2408762 - Recruiting users are unable to move candidates in any status of the talent pipeline - Recruiting Management

Any recruiting operator is not able to move candidates to any status of the talent pipeline. When a user tries to move an applicant in the Candidate Pipeline, the system displays a pop-up error box with the following error message "You do not have permission to change the candidate status" every time.

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."

SAP SuccessFactors Recruiting Management

This issue could have a few causes. Here are the ones we've identified so far:

• The field statusId is not configured in the Job Application Template
• The field statusId is not permissioned to any operator role in the Job Application Template
• Multistage environment is enabled, and the field statusId is given permission in the Job Requisition Template and not on the Job Application Template
• The statuses don't have any Recruiting Operators selected in the "Selectable by" area in Edit Applicant Status Configuration

• It is very important to define the 'statusId' field in the Job Application template.
• If permission to 'statusId' is not maintained and permissioned in the Application template, then users will not be able to move candidates across the talent pipeline.
• It is also important to make sure the status permissions are properly set in Edit Application Status Configuration > [Select the Status Set] > [Select the Status you are not able to move candidates to] > "Selectable by" AND "Visible to".
• If you are using Single Stage Application, the permissions in the Job Application template will be in charge of having the ability to move candidates on the pipeline.
• If you are using Multi Stage Application, all field-permissions in the Job Application XML should move into the Job Requisition Template, except the permissions for the Recruiting Operators to the 'statusId', 'resume', and 'application comments permissions' fields. If the Recruiting Operators do not have write permission on the Job Application Template for the field statusID, then they will not be able to move candidates across the talent pipeline. All other field permissions should be defined in the Requisition template.
• If write permission is given to the Recruiting Operators on the Job Requisition Template for the field statusId as well as in the Job Application Template, there is a high chance that it's still not going to work. The permission to the statusId field must be exclusively given on the Job Application Template.
• Check the status set 'Required' if enabled, sometimes you will see the status set in Pipeline do not have asterisk, so it's important to check in Admin Center>Edit Application Status Configuration > [Select the Status Set].

If contradicting field permissions are specified in both the Application and Requisition templates, the permissions may not be rendered correctly for recruiting users.

2080952 - Applicant Status Configuration in SuccessFactors - Recruiting Management

move, moving, candidate, applicant, non-applicant, status, statusid, resume, coverletter, multi, stage, multistage, single, drag, drop, forward, RCM , KBA , LOD-SF-RCM-APP , Applicants and Job Applications , Problem