3374731 - Applications are not getting purged due to the wrong Internal Status

When the Application's Internal Status is "New" or "Open", the system does not consider the application for purge even though the criteria set for the purge rule is met.

SAP SuccessFactors Recruiting Management

1. Run ad hoc report with affected applications and Internal Status
2. Internal Status is "New" or "Open"

"Internal Status" is a flag used by the system to consider Job Applications for purge. It can only be changed by the system hence called "internal".

It behaves in a way that, if a Job Application is active, meaning it's sitting an in-progress status, the flag will be "New" or "Open". When the Job Application is disqualified, the flag changes to "Disqualified" and when meeting the Purge criteria, the system will pick up the Job Application.

Also note that moving Applications using ODATA API does not update the Internal Status but the Application Status itself.

The "Internal Status" flag must be in a "Withdraw" or "Disqualified" status to be considered for purge.

By manually moving the application from a disqualified status to in progress, then back to a disqualified status again, will change the Internal Status to "Withdraw" or "Disqualified".

This manual action will trigger the system to set the correct flag back to the Job Application which will then be considered for purge.

Note:

• If there is any active emil trigger for the status change, an email will be sent to the candidate. These triggers can be temporarily disabled to avoid unwanted emails being sent.
• Any backend job that moves the Job Application to a Hired status, example Onboarding, is not designed to change the "Internal Status" flag.

Internal, Status, Withdraw, Disqualified, Open, Application, Purge. , KBA , LOD-SF-RCM-APP , Applicants and Job Applications , LOD-SF-RCM-CAN , General Candidate Issues (not Offers, not Profiles) , Problem