Hello,
I'm facing a problem when I try to execute a policyXpress before an event.
Here is my use case :
I have two custom connectors linked to 2 Account Templates (1 each) and 2 Provisioning Roles (1 each):
o Jupiter --> Jupiter_GDA_Role (main role triggered manually)
o GDA --> GDA_Role (secondary role triggered by policyXpress)
I have created a policy which starts before AssignProvisioningRoleEvent. I have configured the action rule to assign GDA_Role to the user when the name of the role I first give (Jupiter_GDA_Role) contains "_GDA_". When I assign Jupiter_GDA_Role to the user, the policy starts and the GDA_Role is also assigned but not always on the order we expect.
I would like to first assign Jupiter_GDA_Role which should start the policyXpress. This policyXpress should assign the GDA_Role first and THEN the Jupiter_GDA_Role (only on the success of the previous action if possible).
I also tested the solution with two PX (1 for each role): I used two PX triggered using EMPTY_JUPITER_GDA_ROLE (not linked to any connector):
o If this role contains "_GDA_", we start PX1 to assign GDA_Role (priority=0 highest priority task)
o If this role contains "JUPITER_", we start PX2 to assign JUPITER_Role (priority=1)
It seems we don't have control over the execution order of the two PX.
Do you know what could be the reason why it doesn’t work or do you have any other way to implement this ?
Regards,
Nassim