3728822 - Address Fields(For Example: 'City') in Candidate Profile appear as Mandatory despite being configured as Non-Mandatory in SuccessFactors Recruiting

• Address Fields(For Example: 'City') in the Candidate Profile are appearing as Mandatory despite being configured as Non-Mandatory.
• Address Fields appears as Mandatory when New Candidate Experience is Enabled.
• Same fields appears as Non-Mandatory when New Candidate Experience is Disabled.

SAP SuccessFactors Recruiting Management

1. Configure fields in the candidate profile as Non-mandatory.
2. Enable New Candidate Experience.
3. Navigate to the 'My Profile' page after creating a candidate profile.
4. Observe that the Address fields(For Example: 'City') appear as Mandatory despite being set as non-mandatory. 
5. Now Disable New Candidate Experience.
6. Again, navigate to the 'My Profile' page after creating a candidate profile.
7. Observe that the Address fields(For Example: 'City') appear as Non-Mandatory as per the configuration.

Expected system behavior.

When the New Candidate Experience is disabled, the system falls back to the Legacy/Mobile Apply experience, resulting in different field behavior, including mandatory settings and validation rules.

Observations and Explanation

1. “City” field appears as Non-Mandatory when New Candidate Experience is Disabled
When the New Candidate Experience (Reimagined Candidate Experience) is disabled in SuccessFactors, the system falls back to the Legacy / Mobile Apply experience.
In this mode, field behavior—including mandatory settings and validation rules—differs from the modern experience, which is why the City field appears as non-mandatory.

2. “City” field appears as Mandatory when New Candidate Experience is Enabled
When the New Candidate Experience is enabled, the City field (along with other address-related fields) becomes mandatory due to Stricter and Modernized validation rules.

This behavior is especially expected if:

• Candidate data is synced with Employee Central, or

• Specific career site mappings are configured.

Conclusion

Based on the above findings, the reported behavior is expected system behavior depending on whether the New Candidate Experience is enabled or disabled.

mandatory fields, non-mandatory, candidate profile, my profile page, SuccessFactors recruiting, new candidate experience, legacy apply, mobile apply, field behavior, validation rules, career site mappings, succession data model , KBA , LOD-SF-RCM-CAN-CX , Candidate eXperience redesigned , Product Enhancement