I have created two termination rules which are triggered after identity unification.
One rule disables and removes entitlements from an AD account.
The other deletes an Oracle account.
Only the first ran rule creates a request, the other does not recognise the termination.
I have tested both rules individually and they work so it seems that the termination rule can only be triggered once?
Hi,
never tried that. Have you tried defining the 2nd rule in a way that it applies to terminated users where the termination/deletion date is > sysdate -1 ? So the rule triggers a day after the termination. might not what you want, though...
Frank
I had initially tried creating a rule that would trigger by evaluating the leave date but only the "Provisioning -Termination" has the AD delete and disable account functionality. The "Provisioning -Termination" rule type also does not have the functionality to specify the exact conditions to kick of a termination rule as it appears this is hardcoded application logic.
Do you know if I'm correct with my assumptions above?
Unfortunately we cannot carry out all the actions under the one rule as for AD we disable the account and remove all entitlements where as with oracle we delete the account. You can only specify one action over all target systems so I had to split the actions out.
I have this setup with 4 separate termination rules, all requests are created correctly on version 6.9.1. P18.
I have this setup with 4 separate termination rules, all requests are created correctly on version 6.9.1. P18.