Symptom
A standard field set as required="true" in the Application xml template, but when candidates apply to a job, the field is not required.
Environment
SAP SuccessFactors Recruiting Management
Reproducing the Issue
- Check in the Application template to see the field set as required="true";
- As an applicant, either internal or external, apply to a job requisition an see that the field is not set as required;
Cause
This is because the same standard field in the candidate Profile Template is set as required="false", so the fields are mapped but not configured in the same way.
Resolution
When you have a field that is set as required="false" in the candidate profile template, and set it as required="true" it is likely that this field will not be required when the candidate is applying to a job requisition. This is because the mapping configuration between the candidate profile and the application needs to be aligned, with the fields configured in the exact same way on both sides.
It is not possible to predict what will exactly happen, you can even face behaviors like the field sometimes being required and sometimes being not required, because the mapping between both templates needs to be aligned.
Keywords
application, applicant, required, field, candidate, profile, true, false, template, job, standard, optional, , KBA , LOD-SF-RCM-APP , Applicants and Job Applications , Problem