and more in a single search tool across platforms. Read the announcement here. |
11/28/2023 04:34 AM
We have a technical rules which looks like this:
Currently, we are assigning entitlements based on a users customproperty7 and an entitlements customproperty38. If these have the same values, assign the entitlement.
We have stumbled upon a problem where if we delete a group from Active Directory and create a new one with the same name, this technical rule will assign both the present entitlement as well as the 'deleted on - TIMESTAMP' entitlement.
Is there a way to finetune this action so we can say:
Assign Groups::ev.customproperty38=substring_index(substring_index('${user.customproperty7}', ',' , 1), ',' , -1) AND ev.entitlement_value NOT LIKE '%Deleted on%'
This does not work as it will assign every entitlement that does not have deleted on, but it won't check the first custom action.
Anyone have any idea how we can implement this?
11/28/2023 04:44 AM
Add status filter
11/28/2023 04:46 AM - edited 11/28/2023 04:46 AM
How would i do this exactly? Could you edit the code so it checks for status 1?
11/28/2023 04:58 AM
Assign Groups::ev.customproperty38=substring_index(substring_index('${user.customproperty7}', ',' , 1), ',' , -1) AND ev.status=1
11/28/2023 05:02 AM - edited 11/28/2023 05:03 AM
This still assigns the "deleted on - " entitlement even though its status is inactive:
11/28/2023 05:30 AM
This looks like defect
11/30/2023 12:47 AM
Can someone give a second opinion on this being a bug? We don't want to create a ticket just to have it closed due to "misconfiguration".