Process Trigger Dependency

Question

We have a scenario where employees leave the company and then return. When the employee leaves, their HR self-service is disabled and their OIM account is disabled. When the employee returns, their OIM account should be re-enabled and their HR self-service should be re-enabled.
We have multiple adapters that fire when a trusted recon. event changes our USR_UDF_EMPL_STATUS field. These are configured on the Xellerate User form and are in Lookup.USR_PROCESS_TRIGGERS. So, we have tasks like OIM Status Change, OIM Reenable Accounts, HR Status Change.
The issue that we are seeing is that sometimes we are getting the HR Status Change occurring before the OIM account has been reenabled. In this case, the target system does not get re-enabled. I am speculating this is because when an OIM user is disabled all of their downstream resources are disabled.
My thought is that we need to use the Task Dependency to set the OIM Reenable Accounts as a Preceding Task to our HR Status change task. Do we set the HR Status Change as a Dependent Task on the OIM Reenable Accounts? Can we have multiple adapters that are dependent tasks as the user might need to be reenabled on other systems besides HR?
Are we on the right path? Is there a better way to do this?
Thanks.

Answer 1

Your hunch is correct. A disabled OIM account basically just sits there and smiles.
Why don't you just add a pre insert entity adapter that checks if there is a HR status change coming from the trusted source. If so simply enable the OIM user account.
Or am I missing something?
Best regards
/Martin