Configuring the Application Template

The CDM (Candidate Data Model) is essentially the candidate application.

• From time to time, customers may want a requisition to be connected to a different application with changes to fields and questions.

• One example is having an application that is focused towards contractors instead of employees, as shown in the figure, Application for Sales Manager – Contractor.

  

The CDM is tied to the job requisition template in the JRDM XML. One JRDM XML template is always connected with one CDM XML template

There can be multiple CDMs per instance. If a customer requires multiple candidate applications, then they will also require multiple job requisition templates, since each job requisition template is tied to one candidate application.

The CDM can be configured to control which fields display for internal versus external candidates, as well as the fields that display to the candidate based on the country where the job is located.

Each field in the CDM can be permissioned to be viewed by each recruiting role that is permissioned on the JRDM.

The CDM is also used to grant button permissions for use after the job requisition has been opened to each recruiting role. Standard buttons can be relabeled and are as follows: Forward, Save, and Cancel.

To export, change the name of, and import the current application, proceed as follows:

• You may receive the following warning when importing your template: If this Application Template already exists in the system, continuing with the upload will replace the existing template with your changes. This will affect all job requisitions that reference this template. Press OK to continue.

  This is a reminder that if you did not rename your template, you will overwrite the existing one in the system, as shown in the figure, Overwrite Warning.

If you have completed the steps correctly, you can see your updated CDM in Provisioning.

Before making any changes to an XML template, be sure to export the current XML version.

Always export two copies of the XML file. Mark one copy as original for that day and archive it. Then work with the second copy and you can date the file for that day.

Note

This process of exporting two copies and archiving should be followed for every type of template: application, requisition, profile, data model, and offer approval. Following a standard process is especially important when more than one person is working with the files.

CDM fields are either standard or custom.

• Standard CDM Fields

  • If the field is a standard field: custom="false".

• Custom CDM Fields

  • If the field is a custom field: custom="true".

  • For custom fields, the field ID starts with cust.

The attributes that define CDM fields are as follows (details of each field will be provided in later sections):

The CDM field types available are as follows:

• Bool

• Date

• Derived

• Enum

• Multiattachment

• Number

• Picklist

• RichText

• Text

If the field ID is anything other than what is listed in the standard field guide, then this attribute must be set to true.

Note

It is best practice to use as many standard fields as possible since standard fields are automatically reportable.

The Anonymize Attribute identifies whether a given field is considered personally identifying data and should be purged.

SAP SuccessFactors provides a Read Audit function that helps to determine who has accessed the sensitive personal data of candidates at your company. When Read Audit is enabled, sensitive fields are included in read audit reports if the candidate or someone else accesses sensitive personal data of the candidate. To configure a field as sensitive, ensure that both the sensitive and the anonymize attributes for the field are set to true.

Some fields should only be seen for jobs in specific countries or by internal and external candidates.

• To show or hide certain fields for jobs in certain countries or for a particular candidate type, use the Field Override configuration.

• Field Override allows public=false fields to be visible to the different groups of candidates (internal and external or for jobs in different countries).

• The following override configuration makes fields viewable to internal candidates:

• <field=attr attribute="public" value="true" applicant="internal"/>

• The following override configuration makes fields viewable to external candidates:

• <field=attr attribute="public" value="true" applicant="external"/>

• The following override configuration makes fields viewable to external candidates for jobs posted in the US and Canada:

  Code snippet

  Copy code

  <country><![CDATA[US]]></country>
  <country><![CDATA[CA]]</country>
  <field attr attribute="public" value="true" applicant="external"/>

  Expand
  

Note

The country abbreviations are dictated by the standard ISO list. These can be viewed on the International Organization for Standardization (ISO) website: www.iso.org/iso/country_codes

The buttons you can enable permissions for are as follows:

• Forward allows the role to forward the candidate to another requisition or to a user.

• Close allows the role to remove the candidate from consideration.

• Save allows the role to save changes to the application.

• Cancel allows the role to cancel changes to the application.

The figure, Application Button XML, shows two XML samples that enable application button permissions.

• In sample 1, the recruiter is permissioned to forward, close, and reopen the application of the candidate.

• In sample 2, all roles ("*") are permissioned to save and cancel changes to the application.

  

Permissions for the fields on the CDM are assigned the same way permissions are assigned in the requisition.

• If permissions are not set for a CDM field, internals roles (such as recruiters and hiring managers) will not be able to read or write to that field on the candidate summary page.

  

After defining a standard field label in the Candidate Data Model, be sure to add the modification in a special area of Provisioning or Admin Center named Job Application Field Labels. If you do not have this option within Admin Center, be sure to enable Manage Job Application Field Labels permission. Any modifications made to this section will be directly reflected to the end user experience for the application.