Handling ONB2.0 rehires in SailPoint

[Richie_Halpagoda]

Dear All,

My customer has SailPoint as the Identity Provisioning agent for the Company Idp (Azure AD). After activating ONB2.0, customer had to update a lot of logics and build was somewhat a rebuilt in SailPoint. Rehire scenario was one of the pain points. If the rehire date was in the past and the ONB activity was not completed, Employee Status from EC picks up as active. This means Old employee record gets activated before the actual hire in EC. According to the KBA https://userapps.support.sap.com/sap/support/knowledge/en/3414839 -this is standard behavior. 

One more thing: SailPoint uses CompoundEmployee API and Odata API. They are unable to put a filter using both APIs.

Has anyone experienced this issue and how did you overcome it?

SAP SuccessFactors Platform , SAP SuccessFactors Onboarding , SAP SuccessFactors Employee Central , API 

[Adam_S]

Hi @Richie_Halpagoda - If I'm understanding your post correctly, we had the same issue with our integration to SailPoint (SP). We created a field on EmploymentInfo that is Yes/No field and this field drives when an employee (new hire or rehire) is ready to be sent to SP. For new hires and rehires, we do not set the field to 'Yes' until Manage Pending Hires is completed. For rehires, this ensures that active record that gets inserted during the ONB process doesn't get picked up by SP until all the data is finalized post the MPH process. We have business rules within ONB and EC to set this flag to No and Yes at the right times.

I am unsure of way to accomplish this more natively without the creation of a new field that SP would 'look' at to determine when a new hire/rehire is ready to be picked up.

[Richie_Halpagoda]

Thanks Adam. This is a good idea. I can potentially add the a flag to say hired or not.