When we create a request for an application, request is getting generated and completing all the approval process
moving to fulfillment phase also but strucked in fulfillment phase by giving a message saying that waiting for dependency.
please find the below screenshot for the detail.
Please suggest your inputs to resolve this issue.
Hi Boris,
Thanks for your quick response..!
Already we had an account in target application its status was orphan. After creating a users by using register user form then i have collected IDC so it got mapped with orphan account of target application
that is why create account operation has not triggered.
It is triggered only add entitlement.but still it is showing as waiting for dependency.ideally it should not.
In your change request, when you are clicking on the account (the i icon), what do you see under Account Users section?
Can you send a screenshot similar to what I posted?
Hi Boris,
Please find the screenshot it shows account is mapped with the user.
Hi Boris,
i am also experiencing that the latest Account collector has not collected this account, in the Row data i can see that this account is missing, but still the Application->Account shows that the account is available. it should go missing right ?
please suggest why the user account is still showing.
i tested with query as well in that application , and it does not show that user's account in application.
please suggest !
Regards,
Rajkiran
One more strange behavior , i am not seeing the account when go and see the Application -> Collector -> Account
Not sure if this is expected behavior, ideally it should not be this way.
It shows at the "Application - > Account" level , but not at the "Application -> Collector - > Account" level.
You most likely see the account under the User -> Access because it's a place holder account.
You don't see the account in Accounts tab, because it wasn't collected.
I suggest you find the first change request where the system tried to provision the account and check what went wrong there. Maybe the provisioning attempt has failed and it's assigned to manual activity.
I see the process issue here.
User waas not present on RSA.
User account was present on Application.
User account were collected by Application Account Collector
Now User got created from RSA side. Users Collected.
User got mapped to Application Account.
Now from Application target system, Users Account got deleted. but Application Account Collector was not run.
and so still RSA shows the Account mapped to user.
Now Manager requested 3 Entitlements of that application.
And so it did not create work item for "Create Account for USer"
but only had add Entitlements to users.
Now as there is no account in target system, and so RSA is not able add them, and its "waiting for Dependency".
I dont find even solution to clean the data as well. i tried terminating user from HR source, Termination Rule got triggered, but then that also throws error, because the actual target system does not have account to terminate.
funny case.
Regards,
Manish
Your screenshot shows only 3 change items. Are there any other?
As far as I know, waiting for dependency happens when you are trying to add access rights but the user still has no account. In that case the system will create additional change item to create account first. If the account creation change item has failed, then all the other change items will be in a waiting for dependency state until the account is created.