Symptom
Read permission not working for "C" role for candidates in Application template.
Environment
SAP SuccessFactors Recruiting Management
Reproducing the Issue
- Configure the below code in Application template.
<field-permission type="read">
<description><![CDATA[Grant candidate read access to the following fields]]></description>
<role-name><![CDATA[C]]></role-name>
<field refid="homePhone"/>
<field refid="source"/>
</field-permission> - As per the above code while applying for a job, candidate should have only read permission for the above fields.
- But when candidates are filling their application they are able to edit/fill these fields.
Cause
The "C" role is not supported in a single stage application and there is no way to stop candidate from filling these fields with attribute defined as public="true".
Resolution
The "C" role is only supported in a Multistage application environment and with the help of multistage feature candidates can have read permission in any of the applicant status. In a single stage application environment, if the customer does not want the candidate to fill/edit some fields then the only way is to hide these fields by making use of public="false" attribute.
Keywords
Read Permissions not working for candidates, Single stage, Application, public="false" , KBA , LOD-SF-RCM , Recruiting Management , Problem