Saviynt unveils its cutting-edge Intelligence Suite products to revolutionize Identity Security!
Click HERE to see how Saviynt Intelligence is transforming the industry.
Saviynt Copilot Icon

Rehire logic not working

NDY
New Contributor III
New Contributor III

We have set up a rule to trigger a rehire action within 30 days based on the user’s end date stored in Customproperty17. However, even when users are rehired within 30 days, the rule for rehire after 30 days is being triggered instead.

For example, in a recent case, the Customproperty17 (end date) was 8/18/2024, and the user was rehired on 9/11/2024. Despite being rehired within 30 days, the rule for rehire after 30 days was triggered.

While checking this logic, everything appears correct, as we are comparing the value in Customproperty17 where the user’s end date is stored.

NPY_0-1726261279291.png

NPY_2-1726262229711.png

 

The logic we have in user update rule is as follows:

Users    Customproperty17     Greater Than     date_sub(curdate(), INTERVAL 31 DAY)

NPY_1-1726261719401.png

Could you please check where the gap could be?

 

 

8 REPLIES 8

rushikeshvartak
All-Star
All-Star

You need to modify the rule to check two conditions:

1. For rehire within 30 days: The user should be rehired when the current date is within 30 days of the end date.
2. For rehire after 30 days: The user should be rehired if the current date is more than 30 days after the end date.

Suggested Logic:

1. Rehire within 30 days:

Users Customproperty17 Greater Than date_sub(curdate(), INTERVAL 30 DAY)


2. Rehire after 30 days:

Users Customproperty17 Less Than or Equal To date_sub(curdate(), INTERVAL 30 DAY)

 


Regards,
Rushikesh Vartak
If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'.

NM
Honored Contributor II
Honored Contributor II

Hi @NDY ,

I will suggest instead of having basic config use advance config as whenever you are doing custom function better to use that .

2) Users Customproperty17 greater than or Equal To date_sub(curdate(), INTERVAL 30 DAY)

NDY
New Contributor III
New Contributor III

If you check my original post, we configured the rehire logic for within 30 days and after 30 days as you suggested. This logic was implemented quite a while ago. The issue we’re encountering is that, even though based on CP17 the user qualifies for rehire within 30 days, the “rehire after 30 days” rule is being triggered instead. For example, as shown in my original post: CustomProperty17 (end date) was 8/18/2024, and the user was rehired on 9/11/2024. Despite this, the “rehire after 30 days” rule was triggered, even though the user was rehired within 30 days. Here is our current rehire logic:

NPY_0-1726445840138.png

 

Did you tried suggestion as mentioned in previous reply


Regards,
Rushikesh Vartak
If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'.

NDY
New Contributor III
New Contributor III

Hi @rushikeshvartak , I don't see any difference in what you suggested versus what we have. Can you pinpoint to what changes I would need to make to existing logic?

NPY_0-1726493544174.png

Thanks

Instead of 2 rules you can have 1 rule with between condition


Regards,
Rushikesh Vartak
If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'.

NDY
New Contributor III
New Contributor III

Is this an issue with having two rules? And would having one rule solve the issue? What could be the reason behind the existing rules not working? Do you think it could be a product defect?

Its condition and implementation issue not an product defect


Regards,
Rushikesh Vartak
If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'.