We are investigating what could be the solution to avoid inconsistency in Last Hire Date for employee being rehired.
Current behavior, before the rehire event is created :
John Doe : 12345
Last Hire Date : 01.01.2021
After the rehire is created with effective date 01.01.2024 :
John Doe : 12345
Last Hire Date : 01.01.2024
Between now & the effective date : 01.01.2024 the value stored in Employment Info > Last Hire Date is causing problem. It's functionaly wrong and these date is often enforced in third party system ( start date < end date)
If we add a custom field in Jobinfo to store the hire date : "CUSTOM Last Hire Date" synchronized by business rule when Hire & Rehire event is effective.
before the rehire event is created :
John Doe : 12345
Last Hire Date : 01.01.2021
CUSTOM Last Hire Date : 01.01.2021
After the rehire event is created :
John Doe : 12345
Last Hire Date : 01.01.2024
CUSTOM Last Hire Date : 01.01.2021
After the rehire event is effective:
John Doe : 12345
Last Hire Date : 01.01.2024
CUSTOM Last Hire Date : 01.01.2024
Does other customer have introduced such custom field to fix Last Hire Date inconsistency before the effective date ?
our second option is to store the information in a MDF object but these will prevent us to use HRIS sync to sync the custom last hire date with standard field hireDate
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.