Click HERE to see how Saviynt Intelligence is transforming the industry. |
08/29/2024 01:58 AM
Hi,
Use case: I am trying to create a use case where through user update rule, remove access of one entitlement it should automatically remove other entitlements specified.
Implementation Details:
For this I tried using the "Remove Ent Task" from Entitlement Map.
Issue: It is generating a pending task only for Ent 1 but not Ent 2.
Ask: I am expecting pending task generation for Ent 2 as well. Should I make any configuration changes to achieve this?
Best Regards
Charitha.
08/29/2024 02:43 AM
Hi @Charitha , is the entitlement from different endpoint still assigned to the account?
Can you try this via ars request.
We saw the same behaviour most likely a bug but as our use case was changed couldn't test all edge cases
08/30/2024 05:09 AM
Hi @NM ,
Yes. Ent 2 from Endpoint 2 is still assigned to the account when the user update rule got invoked and generated remove access task only for Ent 1 from Endpoint 1.
Our use cases are as follows:
Best Regards,
Charitha.
08/29/2024 08:26 AM
08/30/2024 04:55 AM - edited 08/30/2024 04:55 AM
Hi @rushikeshvartak ,
So are you saying, 'Remove Ent Task' work only if entitlements are from same endpoint?
Best Regards,
Charitha
08/30/2024 08:03 AM
Tasks will not be created from entitlement mapped under entitlement map