3598930 - Status Trigger Email Not Triggered to Candidates / Referrer/ Operators When Forwarding Candidates via API - Recruiting Management

Use the ODATA API call to forward candidates to job requisitions, the status trigger email will not send to the candidates, referrer and operators when the applicant in "Forwarded" or "Default" status.

SAP SuccessFactors Recruiting Management

1. Refer a candidate to job requisition via ODATA API call, for example:

{
"__metadata":{
"type": "SFOData.JobReqFwdCandidates",
"uri": "JobReqFwdCandidates"
 },
    "jobReqId":"3068",
    "status": "Default",
    "candidateId": "6336"
}

OR

{
"__metadata":{
"type": "SFOData.JobReqFwdCandidates",
"uri": "JobReqFwdCandidates"
 },
    "jobReqId":"3067",
    "status": "Forwarded",
    "candidateId": "6336"
}

2.Status trigger emails configured in Applicant Status Configuration not triggerd to related person.

Product Engineering is investigating a solution.

Click on star to bookmark this article to receive updates about this issue. For more information about updates from subscribed KBAs, you can refer to the KB Article 2171560 - How to be notified of new or updated SAP Notes or KBAs.

KB Article 2171560 - How to be notified of new or updated SAP Notes or KBAs

RCM, Recruiting Management, Candidate, Referrer, Operator, Recruiter, Email Notification, Status, Trigger, Forwarded, Default, Employee Referrals, Job Applications, External Candidate, ODATA, API, Not send , KBA , LOD-SF-RCM-EML , Recruiting Emails and Notifications , LOD-SF-RCM-API , Webservices & APIs , Bug Filed