Execution Order in ARM Workflow

[rubens_muller]

Masters,

Type of Request: 23 (Role Assignment/Removal)

1: If in the request, the Role has the Remove action, we set it in the initiator to direct to a path without steps.

2: In the request table, we will have a second role with the action "Add" and for this case, the request will be forwarded to another path with a step for the roleowner to approve or not.

Is it possible for item 1 item to be executed ONLY if item 2 is approved (Approval Level: Request)?

The customer's requirement is that the user has only one Business Role.

Along with Abap, we will do an enhancement where, when submitting a request to a new Business Role, the enhancement will extract the user's Business Role assignments and modify to remove action.

Thank you friends

[rubens_muller · Accepted solution]

I located the fit.

Thanks.

[alessandr0 · Accepted solution]

This does not solve your requirement (based on what I understand). That only means that provisioning happens at the end of the request and not at the end of a path. If your "remove" role is auto approved (path with no stages), and the "add" role gets rejected -> the user will end up with no role.

Cheers, A

[rubens_muller · Accepted solution]

Alessandro,

I ran a test and it worked.

I also had to change the Approval and Rejection level for request

If the request is Approved, both paths are executed.

If the request is Rejected, both paths are aborted.

Thank you, Alessando

[alessandr0]

Hi Rubens,

if #1 is dependent on #2, why not including #1 (remove role) in the same approval path?

Cheers, Alessandro

[rubens_muller]

Very grateful for the return, Alessandro

Because I don't want the removal of the Business Role to go through approval.

The "Z_REMOVEROLE" rule has no steps in the path.

Thanks.