SAP Knowledge Base Article - Public

2952333 - Behavior of Required Fields in the Job Application - Recruiting Management

Symptom

This article explains the behavior of required fields in a job application.

Environment

SAP SuccessFactors Recruiting Management

Resolution

Normal Application:
Open Candidate record -> change status drop down -> Save Flow --> Changing an applicant status in this way requires all required fields on the application visible to this operator in this status to be filled in. (Please refer handbook for more information)

Move candidate from action drop down or drag & drop action flow --> Changing an applicant status in this way required fields not validated and candidate successfully moved as per design

Normal Application with Multistage:
Multistage environment in any flow, all required fields for all operators must be filled out before a recruiting user can successfully change the applicant’s status to any In Progress status. An applicant can be moved to a disqualification status at any point, regardless of whether or not required fields are completed.

Late Stage applicant:
Open Candidate record -> change status drop down -> Save Flow --> Public field is visible/editable by both the candidate and operator, for a late stage application, this field should not be validated while moving the candidate to another status. Non-public field is visible/editable only by the operator, for late stage application, this should be validated.

Move candidate from action drop down --> Changing an applicant status in this way required fields not validated and candidate successfully moved as per design

After candidate applied, it will work based on provisioning setting multistage or single stage application.

Keywords

application, required fields, muti stage, late stage , KBA , LOD-SF-RCM , Recruiting Management , LOD-SF-RCM-APP , Applicants and Job Applications , Problem

Product

SAP SuccessFactors Recruiting all versions