At the current system design of the application, when a fields is set as Required and has the attribute Public set as True, or has an override changing the Public attribute to true, via API, these fields will always be required, regardless if the fields are visible or editable at the current status on the Job Requisition. On the other hand, if the field has the attribute Public set as False, this field will never be required via API, even though the Required attribute is set as True.
This behavior is specific to the API changes, the UI is working as expected, and as intended.
SAP SuccessFactors Recruiting Management
application, required, public, true, false, attribute, odata, api, update, status, change, ui , KBA , LOD-SF-RCM-API , Webservices & APIs , Product Enhancement
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.