Symptom
Once candidates have applied to posted jobs, the candidate summary page provides a quick view into applicant information and statuses on the talent pipeline, along with the ability to move candidates from one status to another. In this context, some customers contact the Cloud Product Support to request information how to define a field as required only for a specific status on the talent pipeline.
This article explains why this configuration isn't feasible and what's possible to be configured regarding this request considering a multi-stage application environment.
Environment
SAP SuccessFactors Recruiting Management
Reproducing the Issue
Drag a candidate into specific status or select the candidate and then click on Action" > specific status. After complete this action a field should be required only for in this status.
Resolution
There is no configuration available in the system to define a field as required for a specific status and not required for other statuses on the talent pipeline. What can be achieved is define a field as required and hide the field for other statuses.
As an alternative, the following table presents two proposed solutions for this context:
Approach |
Configuration proposed |
1 |
Define this field as required and viewable for all statuses. |
2 |
Define this field as required and viewable only for a specific status. |
In case you want to implement one of the proposed solutions you should perform that through Manage Template or contact an Implementation Partner.
Keywords
Field Required, Status, Statuses, Multi-Stage, Recruiter, Permission, application-field-id, Talent Pipeline , KBA , LOD-SF-RCM , Recruiting Management , LOD-SF-RCM-APP , Applicants and Job Applications , Problem