2913606 - Job application required field not working when an application status is skipped - Recruiting Management

When you change the candidate application status, the system doesn't show a required field validation error if you skipped an application status where there are blank required fields. Why does the system allow users to skip a status where required fields are not filled?

Configuration 1

Multi Stage Application is enabled.

In the Job Application XML template, you have defined the job application field as required="false".

In the Job Requisition XML template, you added the required="true" attribute to field application-field-id in the field-permission section so that the job application field becomes required in certain application status only. (The related configuration is documented in the KBA 2596149)

Configuration 2

Multi Stage Application is enabled.

In the Job Application XML template, you have defined the job application field as required="true".

In the Job Requisition XML template, you have granted the write permission to edit this job application field in certain application status only.

• SAP SuccessFactors Recruiting Management
• Multi Stage Application is enabled

1. Candidate applies for the job requisition
2. Recruiting user opens the candidate application
3. Move the candidate to an in-progress status by any methods below, skipping the status where there is a required field
   • Drag & Drop
   • Action menu > Move Candidates
   • Change the status and save
4. The candidate is moved into the target status successfully

The system checks the required attribute and the read/write permission only in the current status.

It doesn't show the required field validation error when the field is read-only (or is invisible) to the current operator and no one has write permission to the field in the current status.

• In the case of Configuration 1
  • If the field is NOT required in the current status, it won't show the validation error.
  • If the field is required in the current status but no one has write permission to edit it, it won't show the validation error.
  • It should show the validation error when at least one operator role has write permission to edit the field in the current status.
• In the case of Configuration 2
  • If no one has write permission to edit the field in the current status, it won't show the validation error.
  • It should show the validation error when at least one operator role has write permission to edit the field in the current status.

This is an expected behavior when you skip the status. Regarding the required field validation in the current status, please refer to KBA 2613826 - Application status pipeline validation - Recruiting Management.

If a status should not be skipped, you can set the application status/status group to Required via Admin Center > Edit Applicant Status Configurations. Please refer to 2080952 - Applicant Status Configuration in SuccessFactors Recruiting.

2596149 - Update a Job Application via ODATA when multistage application is used - the system requires to fill any mandatory field, even those one hidden in that specific status - Recruiting Management

2613826 - Application status pipeline validation - Recruiting Management

2080952 - Applicant Status Configuration in SuccessFactors Recruiting

2226690 - Not able to set an application status as "Required" - Recruiting Management

required field validation, job application, candidate status, application status, applicant status, Edit Applicant Status Configuration, field-permission, application-field-id , KBA , LOD-SF-RCM-APP , Applicants and Job Applications , Problem