and more in a single search tool across platforms. Read the announcement here. |
04/04/2023 12:24 PM
Hi Team,
We have a requirement where we need to provide the entitlements(Add access) through rules and if the condition fails then we have to remove the entitlements(Remove access) through rules only.
And if the user already has that entitlement it should not create one more add access task for the same entitlement. But it is creating one more task and that task is going to completed state with "No action required"
Anyone faced this?
Regards,
Varshitha
04/04/2023 01:39 PM
That is the expected product behavior. The task will get created with status as 'No Action Required' and it will be part of the Completed Task List.
04/05/2023 11:32 AM
Hi ,
Have you tried below option in the technical rule?
If the condition doesn't match then remove the birthright access.
Regarding your 2nd question, if the user's account already has the access then in such cases system will created the task with status "No Action Required" and move it to Completed task list.
Thanks
Devang