When pulling prehire worker records from Workday into SailPoint, I’ve noticed that the FILENUMBER (which is the default unique identifier) is coming in as a system-generated GUID.
Once the employee transitions from prehire to active worker and the FILENUMBER updates to the actual employee number:
-
Should we expect this to be a seamless update to the existing identity?
-
Will the identity retain the same cube, or will SailPoint generate a new cube because the unique identifier changed?
Has anyone encountered this behavior, and if so, what’s the best practice for handling it?
I’ve been wondering about this as well and would like to bump this. I set this up in sandbox and noticed that prehires have a much different filenumber but havent been able to get with HR to have them update them to an actual employee record to find out what happens next.
Does anyone at SailPoint/here know how this is supposed to work?
I discovered that pre-hire records identity cubes DO persist when they move to a fully fledged worker. The Transition is seamless. I also discovered they have a file number, but it is a 32 character workday systemID. This means Pre-hires come in with a FILENUMBER and USERNAME that is different than existing hires.
For instance, if all existing hires have a FILENUMBER of 9 numerical characters, then all pre-hire identities would immediately be recognizable with a longer FILENUMBER and USERNAME. Furthermore, a USERNAME will not update after the record has transitioned from pre-hire to regular hire.