3280105 - How Job Application field visibility is controlled - Recruiting Management

This article describes what factors control the application field visibility for Candidates and Recruiting users. 

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."

SAP SuccessFactors Recruiting Management

The following controls an application field's visibility:

a. The "public" attribute in the field definition found in the application template. A value "true" means the field is visible and a value "false" means the field is not visible. In this sample, the field custField is defined to be public="false" which means the field is not visible.

<field-definition id="custField" type="picklist" required="true" custom="true" public="false" readOnly="false" anonymize="false" forward-intact="true" sensitive="false">

b. The override definition for the "public" attribute found in the application template. The override settings can overwrite the "public" value in the definition. In this sample, the attribute="public" is set to value="true" for some countries for applicant type "both".

<country><![CDATA[UZ]]></country>
<country><![CDATA[VE]]></country>
<country><![CDATA[VN]]></country>
<country><![CDATA[VI]]></country>
<country><![CDATA[YE]]></country>
<field-attr attribute="public" value="true" applicant="both"/>
</override>
<field refid="custField"/>

Notes:

1. The applicant value here can be set to "both, internal, or external" depending on which applicants need to see the fields. 

2. The country in the override does not pertain to the country of the candidate but the country of the requisition. In case you have several country fields in the job requisition template, the field with the type="derived" is the country that will be acknowledged.

<field-definition id="country" type="derived" required="true" custom="false">
<field-label><![CDATA[Country]]></field-label>
<field-description><![CDATA[]]></field-description>
</field-definition>

3. Each country is represented by a 2-letter country code in the xml, e.g., UZ is Uzbekistan, VE is Venezuela, etc. If the country is missing or unselected in the country list in the override, then, the applicants on that requisition will not see the field. 

c. Read or Write permissions for the field in the template. In single stage applications, the read or write permissions for the application fields are in the application template, while for multi-stage applications, the read or write permissions for the application fields are in the requisition template. These permissions apply to the candidates and the recruiting users. 

Note: Select the fields under the Field Reference ID list and the candidate [C] will have write permissions on them. 

This is the sample permission for single stage applications where the permissions are in the application template. 

<field-permission type="write">
<description><![CDATA[write access candidate]]></description>
<role-name><![CDATA[C]]></role-name>
<country><![CDATA[PR]]></country>
<country><![CDATA[HK]]></country>
<country><![CDATA[PT]]></country>
<country><![CDATA[HN]]></country>
<source><![CDATA[*]]></source>
<field refid="custField"/>

Notes:

1. The source here can be set to "*, internal, or external" depending on which applicants need to see the fields. 

2. * means both internal and external. 

This is the sample permission for multi-stage applications where the permissions are in the application template. 

<field-permission type="write">
<description><![CDATA[]]></description>
<role-name><![CDATA[C]]></role-name>
<status><![CDATA[Forwarded]]></status>
<status><![CDATA[Invited To Apply]]></status>
<status><![CDATA[Default]]></status>
<field application-field-id="custField" />

Note: The write permissions for the fields in this setup is defined per candidate status, i.e., The candidate [C] will have write permissions to the field custField when the candidate is in Forwarded, Invited To Apply, Default status. However, if the candidate is moved to another status in the pipeline, they will no longer have write permissions to the field. 

Modifying a Template in the Manage Templates Tool
https://help.sap.com/docs/SAP_SUCCESSFACTORS_RECRUITING/8477193265ea4172a1dda118505ca631/108f9be0c6624feca6bf0f51a34c06de.html

Application fields not seen, Application fields not visible, Application fields not showing, Job Application fields, Permissions, Public, Public attribute, Override, Recruiting Management, RCM , KBA , LOD-SF-RCM-APP , Applicants and Job Applications , How To