2913606 - Job application required field validation not working when the application status was skipped - Recruiting Management

When changing the candidate application status, the system does not display a required field validation error, even if a previous status with blank required fields was skipped. 

SAP SuccessFactors Recruiting Management

1. Open a candidate's job application.
2. Move the candidate to an in-progress status by any methods below, skipping a status with an unfilled required field.
   • Drag & Drop
   • Action menu > Move Candidates
   • Change the status and save
3. The candidate is successfully moved to the target status.

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.

Configuration 1

• Multi Stage Application is enabled.
• In the Job Application Template, the job application field is defined as required="false".
• In the Job Requisition Template, the job application field is set as required="true" in a read permission section.

Result:

• 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.

Configuration 2

• Multi Stage Application is enabled.
• In the Job Application Template, the job application field is defined as required="true".
• In the Job Requisition Template, the write permission to edit this job application field is only granted in certain application status, not in the current status.

Result:

• 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 the status with required field is skipped.

To prevent users from skipping a status with required fields, can set the application status/status group as 'Required' in 'Edit Applicant Status Configurations'. For more information, refer to the KBA 2080952 - Applicant Status Configuration in SuccessFactors Recruiting.

KBA 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

KBA 2613826 - Application status pipeline validation - Recruiting Management

KBA 2080952 - Applicant Status Configuration in SuccessFactors Recruiting

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

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