/support/notes/service/sap_logo.png){kind=logo}
SAP Knowledge Base Article - PublicSymptom
Why is moving a candidate through the status pipeline using drag and drop or action menu not validating the required fields and it is validating when changing the status from the candidates application?
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
Environment
SAP SuccessFactors Recruiting Management
Resolution
The behavior changes if you have Multi Stage Application & Late Stage Applications enabled or just Late stage enabled.
Multi Stage Application & Late Stage Applications enabled
|
|
Open record > change status > click Save |
Select record > drag & drop |
Select record > action menu |
|
Normal application* |
Validation - Multistage environment in any flow, all required editable & visible 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. Pasted screenshot below for your reference.
|
Validation - Multistage environment in any flow, all required editable & visible 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. Pasted screenshot below for your reference
|
Validation - Multistage environment in any flow, all required editable & visible 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 application** |
Validation only for 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.
|
NO validation
|
NO validation
|
|
Normal application* |
Validation - Changing an applicant status in this way requires all required fields on the application visible to logged in operator in this status to be filled in
|
NO validation
|
NO validation
|
|
Late stage application** |
Validation only for 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.
|
NO validation
|
NO validation
|
Late Stage Applications enabled
* Candidate applied
** Candidate is forwarded to a requisition (added by operator) and candidate has not yet applied
See Also
2081317 - Late Stage Application - Recruiting Management
2568710 - No error Message received while dragging and dropping candidate in the statuses of the talent pipeline in spite of keeping mandatory fields blank
2863589 - Late Stage Job Application being Moved with Blank Mandatory Multiattachment Type Field - Recruiting Management
Keywords
candidate, application, change, status, behavior, validation, applicant, forwarded, move, save , KBA , LOD-SF-RCM-APP , Applicants and Job Applications , How To
/support/notes/service/facebook.svg)
/support/notes/service/twitter.svg)
/support/notes/service/youtube.svg)
/support/notes/service/linkedin.svg)
/support/notes/service/instagram2.svg)