Symptom
Candidate Profile related information can still be found for Candidates that were anonymized in Ad hoc reports
Environment
SAP SuccessFactors Recruiting Management
Reproducing the Issue
- Build a report to pull information from the Candidate Profile
- Select a candidate that was already anonymized
- See that some information are still available
Cause
- Anonymize flag in the Candidate Profile for these fields is set as "false".
- Applications associated to the relevant Candidate Profiles were updated via an API call, after the candidate profiles had been anonymized in the system. When an application is updated using SFAPI after the candidate profile has been anonymized, then it's expected that the same data will sync back to the Candidate Profile as per system design/behaviour. As a result, this sensitive data will become available to report on after the Candidate Profile anonymization date has passed.
Resolution
Set up the anonymize flag for each field based on your data protection need. You can change the flag either through Provisioning or Manage Templates. For more information on Candidate anonymization, please refer to the article 2103423 - DRM 2.0 to Purge Inactive Candidates and Inactive Applications - RCM.
For candidates that have already been anonymized, you can update them via API after the anonymization date to mask the data completely. Please see the following KBA for further details: 2833895 - Update Anonymized Candidate Profile via SFAPI.
See Also
Keywords
Anonymized Fields, Deleted Candidate, Purged, Anonymized Information, Report, SFAPI, DRTM, candidate snapshot , KBA , LOD-SF-RCM-CAN , General Candidate Issues (not Offers, not Profiles) , Problem