Provisioning Priority Option Usage in Entitlement Types

[Community_User]

Originally posted on September 29 2021 at 18:24 UTC

Would like to understand Provisioning Priority Option Usage in Entitlement Types. Is there any documentations around it?

Enabling this option will only help execute the entitlement type specific tasks on priority when the user already has an account? What about new account tasks tagged along with add access tasks? 

Has anyone successfully used the option & know the use cases where it can be used efficiently? Any inputs here is much appreciated.

[Community_User]

Originally posted on September 29 2021 at 21:23 UTC

Siva,

Do you mean the instant provisioning that can be configured based on the task type ?

Regards,

Avinash Chhetri

[Community_User]

Originally posted on September 30 2021 at 19:42 UTC

No, Avinash! If you open any endpoint and traverse to entitlement type details -> There is a toggle button for Enable provisioning priority (ON / OFF). Looking to get understanding of what this option can do when switched on. 

[Community_User · Accepted solution]

Originally posted on October 5 2021 at 00:29 UTC

Hi Sivagami,

Based on the documentation link shared below, it seems to work based on the priority of the the individual entitlement set when the "Enable provisioning Priority" is also configured.

https://saviynt.freshdesk.com/a/solutions/articles/43000431776

Regards,

Avinash Chhetri

[Community_User]

Originally posted on October 12 2021 at 18:32 UTC

Hi Avinash, Team,

We noticed the option to not work as described in the documentation. Hence, I wanted to check the usage.

[Community_User]

Originally posted on October 12 2021 at 19:09 UTC

Sivagami,

Could you let me know the use case you tried, how you configured Saviynt for it and what was your observation ?

Regards,

Avinash Chhetri

[Community_User]

Originally posted on October 12 2021 at 19:35 UTC

Let's take Application A and Application B.

Application A with ent type C which is set provisioning priority

Application B with ent type D which is not set provisioning priority

We have New account, add access tasks and remove access tasks for both Application A and Application B

When wsretry is run for Application A and Application B, expectation is add access / remove access tasks for the ent type C should get processed first over ent type D tasks right? But we noticed the system to process both the application tasks randomly and the provisioning priority was not taken into consideration.

[Community_User]

Originally posted on October 15 2021 at 00:32 UTC

Sivagami,

Did you also set the priority for the particular entitlement value (say Admin) under ent type C ?

Also I believe you cannot set the same priority for two different entitlements within an entitlement type.

for e.g. If EntType C is set for Provisioning priority and you have 2 entitlements say Admin and Read/Write, the priority on each of them needs to be set at the entitlement value level and they cannot be both set the same value i.e. 1

Regards,

Avinash Chhetri

[Community_User]

Originally posted on November 2 2021 at 19:26 UTC

Thanks Avinash for the clarity.

Have few more queries.

1) Is there any configs that needs to be set in externalconfig for the wsretry job to check provisioning priority?

2) Does the provisioning priority functionality work irrespective of whether provisioning job is WSBLOCKINGRETRY or WSRETRY ?

2) Let's say you have 5 entitlements in EntType C, are you suggesting setting priority on the entitlement to be set on all entitlements available for the entitlement type with provisioning priority enabled? What will happen to the entitlements not set priority?

[Community_User]

Originally posted on November 2 2021 at 22:48 UTC

Hi Sivagami,

1) I do not think anything extra configs needs to be set. Are you facing any issue ? 

2) I'm not sure on this one, I have not personally tried testing this feature on both WSRETRY jobs. Are you facing any issue ?

3) No, out of the 5 entitlements, you can have two of them set to 1 and 2. You cannot have two ent values both set to 1.

Regards,

Avinash Chhetri