Greetings, I'm a little green on FIM and looking for some advice.
We have an HR system where we store the information on Contractors, Interns, and Employees.
The business process for converting Contractors and Interns to Employees is to terminate the Contractor and re-hire as an Employee. This gives us a different employee number for the "live" entry in the HR system.
Also, there is a "Supervisor No" attribute that is a Reference attribute for their manager. This is their employee number.
What do I do in FIM? If the Employee number is the anchor, won't the system consider the employee a new object? Is there a way to connect the new employee record to the metaverse object that was a contractor or intern, and update the anchor attribute (the new employee number)?
I was thinking of using a different custom field in the HR system as the FIM_Sync. But just realized that if this became the anchor, then no managers would connect since the Supervisor No is an Employee number.
Thanks in advance for helping.
-Doug
*** Update ***
I read some of the articles on Correlation ID that are in the 2003 version of MIIS the TechNet library. So a follow up question would be what happens between the CS and MV when the HR object changes.. Assuming I have this FIM_Sync attribute to be my Correlation ID.
- Contractor is created. Employee ID is anchor and FIM_Sync field is populated.
- New object in CS
- Projected into MV
- Provisioned out to AD and other systems, but they don't have the FIM_Sync attribute in their schema.
- Business Event.. Contactor converted to Employee:
- Contractor in HR system terminated (employment_state) and FIM_Sync entry removed.
- Employee record created in HR system and FIM_Sync value populated with what it was in the contractor record
- New Employee object in CS
- Does Contractor get disconnected?
- Does the Employee CS object get joined to existing MV object?