on Jul 27, 2017I would like to know, how can we use the variable of sAMAccountname that has been configured in AD Fulfillment workflow to be used in Application fulfillment workflow to have an instant update in AD followed by another application provisioning.
Currently, I’m relying on Rule to initiate Application fulfillment workflow which will trigger based on the reconciled data from Active Directory, post successful Account Creation.
I’m sure this approach will not help the end users to have respective application access immediately as IGL would wait for Active Directory identity collection to get complete.
Any better approach to minimize the delay for the action on follow up system.
If you are using an account template to calculate the value for samaccountname and not changing it in the workflow runtime, then you can use the same account template for the other application account creation.
If you are calculating the value (for samaccountname) in runtime, then you can store your calculated value in a custom user managed attribute and then retrieve it in fulfillment workflow of the other application