2603610 - Candidate is landing to "Forwarded" status on a talent pipeline when updating value using ODATA API

When a Recruiting user want to move or add a forwarded candidate to a Job requisition functionality through oData API.

User tries to add a forwarded candidate to the job requisition through oData API, candidate information is not displayed in the candidate summary page UI due to which there exists an inconsistency between the candidate count in Job requisition landing page and Candidate Summary page.

When ever we use the entity "SFOData.JobReqFwdCandidates" - Candidate lands in Forwarded status irerespective of the fact we are passing status as Invited to Apply, Default or Forwarded.

This is a known limitation in Odata API , where candidate who's in Forwarded status cannot moved/upserted to "Default/NewApplication" status using Odata.

Whenever we use UPSERT candidate application using entity – “SFOData.JobReqFwdCandidates” with Default and Forwarded status being passed as one of the parameters in different request payload.

However, every time the application will land into “Forwarded” status.

The workaround is to update the same via UI only.

Enhancement Request has been raised for the same: https://jira.successfactors.com/browse/RCM-35717

Please follow the release notes on the status of the enhancement request.

KBA , LOD-SF-RCM-API , Webservices & APIs , Problem