Delphix Products

Hello everyone,

Does anyone configured the "Approval Workflow" in the Masking Engine in a way that User1 can only do the masking configuration such as Connectors, Rulesets, Inventory and Masking Job but cannot run the Masking Jobs unless User2 is approves the configuration?

BR,

Yes, that is the default configuration / normal use case. 

User1 can configure everything but once he starts job the gets message that it is not approved > cannot start job.

Once User2 approves the ruleset the job can execute by User1.

If anyone edits ruleset it gets un-approved and job cannot execute > another approval required.

Not sure if the connector is part of this verification (maybe) but the ruleset is verified.

Hello everyone,

Does anyone configured the "Approval Workflow" in the Masking Engine in a way that User1 can only do the masking configuration such as Connectors, Rulesets, Inventory and Masking Job but cannot run the Masking Jobs unless User2 is approves the configuration?

BR,

Yes, that is the default configuration / normal use case. 

User1 can configure everything but once he starts job the gets message that it is not approved > cannot start job.

Once User2 approves the ruleset the job can execute by User1.

If anyone edits ruleset it gets un-approved and job cannot execute > another approval required.

Not sure if the connector is part of this verification (maybe) but the ruleset is verified.

Hello everyone,

Does anyone configured the "Approval Workflow" in the Masking Engine in a way that User1 can only do the masking configuration such as Connectors, Rulesets, Inventory and Masking Job but cannot run the Masking Jobs unless User2 is approves the configuration?

BR,

Not aware there is a specific documentation; 

You need to roles, user1 = create/edit/execute ... BUT not approval permission.

For user2 you need only approval.

Change environment to enable approval workflow.

From this moment onwards if user1 makes a change in ruleset it gets "locked" > and jobs can be executed only if user2 gives approval.

Yes, that is the default configuration / normal use case. 

User1 can configure everything but once he starts job the gets message that it is not approved > cannot start job.

Once User2 approves the ruleset the job can execute by User1.

If anyone edits ruleset it gets un-approved and job cannot execute > another approval required.

Not sure if the connector is part of this verification (maybe) but the ruleset is verified.

Hello everyone,

Does anyone configured the "Approval Workflow" in the Masking Engine in a way that User1 can only do the masking configuration such as Connectors, Rulesets, Inventory and Masking Job but cannot run the Masking Jobs unless User2 is approves the configuration?

BR,