The "Purge inactive candidates" job as part of DRTM is not purging a candidate.
SAP SuccessFactors Recruiting Management.
Reproducing the Issue
- Setup the "Purge inactive candidates" job to purge candidates in a country who have been inactive for x amount of years.
- Identify a candidate from the country who has been inactive for that period of time.
- Execute the "Purge inactive candidates" job.
- Notice that the candidate has not been purged and can still be seen in the Candidate Search feature.
One possible cause is that the candidate has been "Marked for anonymisation by candidate delete". You can check this by running an AdHoc report for the field "Anonymisation flag" for that candidate.
This anonymisation flag means that the candidate has requested their profile to be deleted themselves.
This type of purge relies on the "RCM Entity Anonymization Job" in Provisioning to be executed, not the "purge inactive candidates" job, even if the candidate meets the inactive criteria.
To delete candidates who have been "Marked for anonymisation by candidate delete", you need to setup the "RCM Entity Anonymization Job" in Provisioning.
Please see step 3 of KBA 2166333 - "How to set up anonymization - Recruiting Management" for information on how to set this up. If you do not have access to Provisioning, please contact your Implementation Partners or the Professional Services team to set it up for you.
Once this job is set up and executed, the candidate and all other candidates who have requested their profile to be deleted will be purged. You can check this by running the same AdHoc report for the field "Anonymisation flag", and see that the flag now has the value "Anonymised", meaning that the candidate has been purged.
KBA 2635179 - "New Data Retention Time Management in Recruiting Management"
candidate, purge, purged, anonymised, deleted, purge inactive candidates, DRTM, inactive, candidates , KBA , LOD-SF-RCM-CAN , General Candidate Issues (not Offers, not Profiles) , Problem