3117417 - FAQs on Job Requisition templates in Manage Templates - Recruiting Management

This article describes the steps on how to view and update the Job Requisition templates in Manage Templates. The information in this document is supplementary to the implementation guide. 

"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

Job Requisition Templates

Job Requisition Fields

• Template Name - specifies the default name of the Job Requisition template.
• Add More+ - shows the template name per language.
• Application Template Name - specifies the application template name linked to the Job Requisition template. If there is no application template name specified here, the Job Requisition template will be linked to the default application template. 
• Minimum Posting Days - specifies the minimum number of posting days.
• Minimum Internal Lead Days - specifies the minimum internal lead days.
• Template Description - specifies the description text of the template. It is usually the template name.  
• Template Last Modified Date - specifies the last modified date of the template. This does not automatically set to Today's date. This must be changed every time a change will be made in the system. 
• Since the change in this field is manual, there is a possibility that the last modified date is not adjusted even though a change is made in the template, the Audit trail in 'View Audit Trail' option will show the actual 'Changed On' date of the template when changes are made.
• Supported Languages - specifies the supported languages to be used in the actual requisition. The list here depends on the list of active languages in the instance. 
• Just because a language is active in the instance does not mean it can be used by the requisition immediately. The language must be selected here first.  
• Default Listing Layout ID - specifies the listing layout ID.
• Assessment Scale - specifies the assessment scale used by interview assessment. The list here depends on the scales defined in Admin Center > Rating Scale.
• Reverse the Assessment Scale - specifies whether the assessment scale is ascending or descending order.

Job Requisition Template Sections

a. Fields defined - specifies the fields definition in the job requisition template and their attributes, i.e., field-id, field-name, required, etc. Note: If an existing field has a blank field-id, this most likely means that a custom field was defined as a standard field or vice-versa, which would cause data issues on your requisition and returns an error when saving the Job Requisition template. 

<field-definition id="id" type="text" required="false" custom="false">
<field-label><![CDATA[Req Id]]></field-label>
<field-label lang="de_DE"><![CDATA[Anford.-Nr.]]></field-label>
<field-label lang="en_GB"><![CDATA[Req Id]]></field-label>
<field-label lang="en_US"><![CDATA[Req Id]]></field-label>
<field-label lang="es_ES"><![CDATA[ID necesario]]></field-label>
<field-label lang="fr_FR"><![CDATA[Identifiant de demande]]></field-label>
<field-label lang="ja_JP"><![CDATA[申請 ID]]></field-label>
</field-definition>

b. Field Permissions - controls the field visibility (read/write permissions) in the job requisition template. Note: Never use the 'Field Permission Type' value, none. Only set the field permissions to either read or write. 

<field-permission type="write">
  <description><![CDATA[]]></description>
  <role-name><![CDATA[R]]></role-name>
  <role-name><![CDATA[O]]></role-name>
  <role-name><![CDATA[G]]></role-name>
  <status><![CDATA[pre-approved]]></status>
  <status><![CDATA[approved]]></status>
  <status><![CDATA[closed]]></status>
  <field refid="status"/>
</field-permission>

Note: The status pre-approved means the requisition is still in the route map for approval, approved means the requisition is already approved from the route map and is already open, and closed means the requisition is already closed or filled.

c. Button Permissions - controls the button permissions for job requisition buttons: close requisition, reopen requisition, and link child requisition. 

<button-permission>
  <description><![CDATA[]]></description>
  <role-name><![CDATA[O]]></role-name>
  <role-name><![CDATA[R]]></role-name>
  <role-name><![CDATA[G]]></role-name>
  <button-id><![CDATA[closeReq]]></button-id>
  <button-id><![CDATA[reopenReq]]></button-id>
</button-permission>

d. Candidate email permission defined - controls the email option for the candidates in the applications. By default, all operators can access the email option on the application record (near Take Action option). However, if you use this feature, only the operators defined here will have permissions to the email option in the application. 

<candidate-email-permission type="candidateEmail">
 <description><![CDATA[Recruiters can email candidate.]]></description>
 <role-name><![CDATA[R]]></role-name>
</candidate-email-permission>

e. Candidate SMS Permission defined - controls the SMS option for the candidates in the applications.

f. Listing Fields defined - controls which fields are added as listing fields. Listing fields are fields in a job requisition that you want to use as tokens in job descriptions, headers, and footers. Note: These are for standard fields. For custom fields, create a support request to add a field as a token in provisioning.

g. Mobile Fields defined - controls which fields are added in the mobile view of the requisition.

More Information on Designators or Operators in a Job Requisition

Application Section in the Job Requisition

Used for Late-Stage and Multi-Stage enabled instances:

General Settings > Application Status Configuration - section to control the application-related permissions.

a. Application Status Configuration Name - specifies the linked status set or pipeline status set in the job requisition.

<application-status-set name="Standard Status Set"/>

b. Field Permissions - controls the field visibility (read/write permissions) of the application fields per pipeline status and to whom it was permissioned.

<field-permission type="write">
  <description><![CDATA[C can read at these stages]]></description>
  <role-name><![CDATA[C]]></role-name>
  <status><![CDATA[Default]]></status>
  <status><![CDATA[Shortlist]]></status>
  <status><![CDATA[Offer]]></status>
  <status><![CDATA[Hireable]]></status>
  <status><![CDATA[Hire]]></status>
  <status><![CDATA[Unsuccessful]]></status>
  <field application-field-id="firstName" />
  <field application-field-id="lastName" />
</field-permission>

Note: You can make the application fields required in this section instead of the application template. For example: <field application-field-id="firstName" required="true" />.
 
c. Feature Permissions - controls the permissions of the different application features, i.e., candQuestions, interviewAssessment, assessmentIntegration, etc.

<feature-permission type="assessmentIntegration">
  <description><![CDATA[The following roles can launch interview assessment during statuses with an Assessment category]]></description>
  <role-name><![CDATA[S]]></role-name>
  <role-name><![CDATA[O]]></role-name>
  <role-name><![CDATA[R]]></role-name>
  <role-name><![CDATA[G]]></role-name>
  <role-name><![CDATA[Q]]></role-name>
  <status><![CDATA[Assessment]]></status>
</feature-permission>

More Information on Feature Permissions

Manage Templates, Recruiting Templates, Job Requisition templates, Recruiting Management, RCM, Late-Stage, Multi-Stage, Feature Permissions, Field Permissions, Button Permissions, Listing Fields, Mobile , KBA , LOD-SF-RCM-JOB , Job Postings & Requisitions , How To