Future dated Worker information and Contract to Employee Conversion; Profile and LCE impact

msmith33
Tera Contributor

01: Current issue: It’s confusing to look at the profile for rehire and contractor conversion due to blend of current and future data.   Contract conversions LCE do not work properly and can’t consume having a current active contractor  record with incoming future hire employee record.

 

02: We currently store a blend of current and future worker data on both the USER PROFILE and the HR PROFILE in order to provide:

  • LifeCycle:  Future dated Hire/Termination (Onboarding and Offboarding) worker information (need future hire/term date; location, manager, employee type- i.e. contractor vs. employee, etc.)
  • Manager’s ability to raise tickets in ServiceNow (ex: request for new software) and tie to future hire/worker.

 

03:Use Case: Future dated hires; rehires (previous worker engagement); Contract to Employee Conversion (i.e. active contractor becomes and employee with gap in service); Future terminations

 

04: Ideal state:

  • User and HR profile with “current” worker information and “future dated” worker information. Easy for end-user to know if data is current or future dated.
  • Future Dated LCE – Onobarding and Offboarding based on future worker data
  • If contractor becomes an employee (contract conversion); keep profile based on current active contractor record but LCE based on their future employee hire worker data.

 

05: What is ServiceNow’s recommendation for storing future dated worker information in ServiceNow?   

How are customers handling future dated worker information in ServiceNow?  

Is there a way to store both current and future dated information on profiles, for example on separate tabs?   

Are customers leveraging the sn_hr_core_job and if so, what is the impact on LCE and profiles?  Any other SN tables to consider (delivered or custom)

 

 

1 REPLY 1

Susan Britt
Mega Sage
Mega Sage

Are you utilizing the Jobs related list on the HR Profile?  This is a common issue to work through in the system, but also with the teams - coaching them on where to look for what.  For lifecycle events, it's best to have the information on the HR Profile regarding the role/employment type needed for the process (i.e., your future data info).  Then if you are using the Jobs history, those records can be added to indicate the contingent worker info that is technically the current info.