Account tasks not to be closed before add access tasks are generated

[NID27]

Hi,

We have a setup when user is imported it autogenerates a create account task for AD. Add access tasks are generated on the start date of the user. Now the requirement is that Account creation task should not be closed before Add access tasks are generated. Any ways to do this?

thanks

Nidhi

[naveenss]

Hi @NID27  use advanced query in the WSRETRY job to restrict this. 

[pmahalle]

Hi @NID27 ,

Set Create Task Action to EntitlementsOnly in Security system. It will create new account task with Add access instead of creating it separately. It means, after setting above mentioned configuration, in your case, when user imported it will not create New Account task, on start date when add access task getting created inside the same add access task, new account task created as subtask. 

Let me know if it helps.

[dgandhi]

Enable below option at Security System level to achieve the use case:

https://docs.saviyntcloud.com/bundle/EIC-Admin-v23x/page/Content/Chapter02-Identity-Repository/Creat...

in all other user interface instances, Active Directory name will appear as given in the Display name.

Create Task Action

This field allows the administrator to define creating tasks for both accounts and entitlements or only entitlements. The parameter provides you the following options: Select: This is the default option, this option creates the tasks for both account and entitlements. If the entitlement request is rejected and the account is approved, the account is provisioned along with the task creation of the account. As entitlement is rejected, a task is created for entitlement but entitlement request is denied. EntitlementsOnly: Select this option to prevent creating a separate Create Account task, when creating an account and entitlement are requested together. If EntitlementsOnly is selected and the approver completes approving the account and entitlement, the task for entitlement is created after completing approval of account and entitlement. An account is created only after approval of the entitlement request. No task is created for the account. Use this option to create a task for entitlements only and wait for the entitlement to get approved, and then create an account. Using this option you can also create Add Access tasks for the entitlements that are available in Entitlements with New Account tab.

[rushikeshvartak]

Without Account , How add access task will be closed ?

If you don't want account task then you can enable EntitlementsOnly under Security System --> Create task Action.

But you can't hold any task to be completed after.

You can try task execution hierarchy in Global configuration

[NID27]

Hi Rushikesh,

Add access tasks are getting errrored out because there is no account at the target.

So.. My concern is- Is there any way to hold the create account tasks untill the add access tasks are generated? Can we put some query in the wsretry job so that it process only those create account tasks which have add access task pending already?

[pmahalle]

Hi @NID27 ,

Hi @NID27 ,

Set Create Task Action to EntitlementsOnly in Security system. It will create new account task with Add access instead of creating it separately. It means, after setting above mentioned configuration, in your case, when user imported it will not create New Account task, on start date when add access task getting created inside the same add access task, new account task created as subtask. 

Refer: https://docs.saviyntcloud.com/bundle/EIC-Admin-v23x/page/Content/Chapter02-Identity-Repository/Creat...

Let me know if it helps.

[rushikeshvartak]

Write create Account logic in Add Access with condition

[Manu269]

Ideally the access provisioning should happen only after account creation.

DId you tried exploring SS > Create Task Action > EntitlementsOnly option