Symptom
- Anonymized candidate is still showing on the New Candidate Workbench. The said behavior is not appearing or present in Legacy workbench as the candidate shows Anonymized.
- An error is also present when you click or select the candidate profile.
internalMessage=Failed to Get Application Header Info
errorMessage=Service /rest/recruiting/application/v1/applicantSummary?jobRequisitionId=XXX&candidateId=XXX gave 401
status=401
timestamp=YYYY-MM-DDTHH:MM:SS.MSSZ
externalMessage=???UNAUTHORIZED???
Environment
SAP SuccessFactors Recruiting Management
Reproducing the Issue
- Access Recruiting page
- Go to affected job requisition
- Select the Candidate tab in the job requisition
- Notice the Anonymized Candidate is present and showing information.
- Click on the affected candidate and the error would appear.
- Go back to Recruiting page and repeat steps 2-4.
- Switch the toggle option for Legacy.
- Notice the affected candidate is anonymized and no error is present when selecting the profile.
Cause
There was an issue where the event triggering the candidate anonymization flow did not occur.
Resolution
For Live Customers and Implementation Partners
- Please create a incident ticket for Product Support team to investigate and further make an assessment.
- Would require clean up the stale indexed data from Solr and run the script to remove the anonymized candidates from the latest workbench.
Click on star to bookmark this article in order to receive updates about this issue. For more information about updates from subscribed KBAs, you can refer to the KBA 2171560 - How to be notified of new or updated SAP Notes or KBAs - SAP for Me.
See Also
Keywords
RCM-149407, PTCH-46209, applicant, workbench, redesigned, anonymization, purge , KBA , LOD-SF-RCM-APP , Applicants and Job Applications , Problem