3391860 - Candidate Purge based in Last Login Date and Third Party Integrations - Recruiting Management

System consider lastLoginDate to calculate inactivity for the candidates purge.

When candidate profiles are created using API by third-party integrations, at the moment of the creation the lastLoginDate is filled with the current date.

However, since some third-party integrations do not use SuccessFactors Career Site, candidates don't access this portal and the lastLoginDate information is not updated anymore, even if they maintain activity in third-party side.

SAP SuccessFactors Recruiting Management

This has been confirmed by Product Management as known limitation.

System will consider only the login in SuccessFactors career portal to update the lastLoginDate field.

Besides, at the moment, the lastLoginDate is not an upsertable field to be updated using API.

There's an enhancement request about this topic, please click in the link to check it out: Candidate Profile Purge Date - Option to update the last login date via the API, or submit a new one as per KBA 2090228 - How to submit enhancement ideas for SAP SuccessFactors Products.

third-party, integration, upsert, upsertable, lastLoginDate, API, candidate profile, Phenom, eightFold , KBA , LOD-SF-RCM-CAN , General Candidate Issues (not Offers, not Profiles) , Problem