Configuring the Candidate Profile Template (CPT)

Objective

After completing this lesson, you will be able to configure and permission fields for the candidate profile.

Candidate Profile Template

Learn about creating candidate profiles.

In today’s competitive market, most companies want to provide their candidates with a quick, easy and intuitive candidate experience.

As the consultant, you need to carefully find your way through the application process of a company and avoid configuration that would make a candidate want to abandon the application process.

Internal and External Candidate Profiles

  • The candidate profile template (CPT) is also referred to as the candidate profile and serves as an online resumé. There is only one CPT per instance.

  • Candidate profiles exist for all applicants in the system, both internal and external.

    Internal and External Candidate Profiles tab is displayed on Careers page.

Profile Before Application Feature and Its Activation

The Profile Before Application feature allows customers to set the completion of the candidate profile to required (or obligatory) as the first step in the application process.

The candidate stops by the profile each time before completing an application, but they only need to enter the required data once. Each time after that, the candidate can verify that the data is correct and that data then is updated automatically in the application.

Activation of the Profile Before Application Feature

  1. Log in to Provisioning.

  2. In Company Settings, select the Complete Profile before Application check box.

To activate the Profile Before Application Feature, select the Complete Profile before Application check box.

To enable this Profile before Application feature, log in to Provisioning and turn on the following switch: ProvisioningCompany SettingsComplete Profile Before Application.

Benefits of the Profile before Application Feature

It is best practice to enable the Profile Before Application feature. Collect all candidate-specific information in the candidate profile. Collect job-specific information in the application form.

The benefits of using the Profile before Application feature include:

  • Synchronizes data completed first on the application with the profile, if the feature is enabled.

  • Data completed first on the application automatically synchronizes with the profile if the feature is enabled.

Background elements on the candidate profile can be synced with User Background Elements when User Background Elements are imported.

Candidate ID Available on Candidate Profile Pages

The Candidate ID can be displayed on the candidate profile pages.

Candidate ID is displayed on the candidate profile page.

Enablement of Candidate Display Functionality in Admin Center

Functionality has to be enabled in Admin CenterManage Recruiting Settings.

Candidate Profile Settings page is displayed. Select the highlighted checkbox to display candidate ID.

Candidate Profile Template Details

Zone 1, or the Meta Section, contains the template name, description, last modified date, and the spell check tag.

Template details

None of this data is visible in the user interface and no changes are needed here.

Code block is displayed.

Instruction text In the Candidate Profile

Instruction text can be configured in the meta section, which can provide details for the candidate on what information they need to provide. The instruction can be same or different for internal or external candidates.

Code block is displayed.
Instruction text in Candidate Profile is displayed.

Candidate Profile Template Field Definitions

Zone 2 contains the field definitions.

Field definitions

Remember that order matters. Fields display in the candidate profile in the order they are configured.

Note

Certain fields always display in specific areas of the profile.
  • The id element identifies the supported system data field.

  • For standard fields you must use the exact id as detailed in the DTD or standard fields guide. The CPT uses the candidate-profile-data-model DTD.

  • For custom fields and all fields with field type of instruction, you may create your own id value. A good practice is to ensure that the ids correlate to the field label. This also makes it easier for you when you establish the custom fields that are to be reportable.

    Code block is displayed.

Valid field types

The type element defines the field type.

Valid field types

Field TypeData
textA single line of "free text"
textareaMultiple lines of "free text"
picklistMapped to picklist ID (shown as a dropdown menu)
dateA typed date that prompts the use of a calendar widget
instructionRead only text (for example, instructions on how to  fill out a field)
boolTrue or false (shown as a checkbox)
numberA number value. The system only allows entry of numbers in these fields that automatically display with two decimals. For example, entry of 2 will display as 2.00
percentA percent value. The system only allows entry of numbers in these fields that display with a percentage sign. For example, entry of "50" will display as 50%
multiattachmentselectionAllows ability to add documents (other than resumé and cover letter which have a specific field and location on the candidate profile)

The required element specifies whether the field requires a value. The user cannot save the profile until required fields have been completed.

The custom element specifies whether the field is a standard field as identified in the DTD or a custom field.

Candidate Profile and Candidate Application Mapping

Candidate data captured in the CPT automatically feeds the candidate application, or Candidate Data Model (CDM), when the candidate applies for a position, as long as the data elements have been configured in both the CPT and the CDM.

CPT and CDM mapping

Note the correlation between the data in the CPT and the CDM:

The correlation between the data in the CPT and the CDM is displayed.

CPT XML and Application XML

To ensure that data synchronizes between the application and the profile, you need to configure the field definitions exactly the same (same ID, same field type, and so on).

Code block is displayed.

Changes to the candidate profile do not affect existing applications. For example, if a candidate moves and changes their street address, the original street address on the application stays the same because an application is a 'point-in-time' reference.

The documents uploaded in the candidate profile can be made available and synchronized in the application. Documents added or deleted in the application can be synchronized with the candidate profile if the field ID and type are the same in both the profile and application XML.

If custom field id between Candidate Template and Application Template are mapped same column name should be used. If not done, a warning message will be displayed to the user and changes be allowed to be saved.

Mapping of CPT and CDM custom fields is shown with arrows on the screenshots.

After creating the CPT, it is necessary to build the database index. Please follow the instructions in this handbook to build the index.

CPT Permissions

Field permissions in the Candidate Profile template control the permission to view and edit each field in the candidate profile.

You can set permissions so that field can be hidden, set to read or write for candidates, and set to read or write for recruiting users. Customers can specify whether only a candidate can write to specific fields or whether defined recruiting users who are part of a dynamic group can also write to the field. Permissions can be defined based on the type of candidate (internal or external) and on the country/region of the candidate. If field-permission tags don't exist in the Candidate Profile XML, the default behavior is write permission for all the fields to the candidate and read permission for recruiting users.

Considerations include:

  • Multiple role-name elements aren’t supported within a single field-permission element, but doesn't cause an error during Provisioning validation.
  • To create a permission element for the candidate role, configure the role-name element with a CDATA value of "Candidate".
  • To create a permission element for a dynamic group, configuring the role-name element with a CDATA value of "Dynamic Group".
  • When setting up a Dynamic Group, the role-name element must also contain a group-name attribute defining the group the role is tied to.
  • The field-permission element must contain at least one country element. Multiple country elements are supported.
  • The country element must contain a two-digit ISO code for the applicable country/region or an asterisk to denote all countries/regions, such as US, DE, UK or *. Refer to the Online Browsing Platform (OBP) at the ISO website for the complete list of the two-digit country/region codes.
  • For the country-specific permission feature to function properly, the Candidate Profile must contain a field-definition with the id="country" type="picklist" where the picklist-id="country". The country picklist loaded into the instance must be the ISO standard country values. The system does the conversion into the two-character ISO country code, such as US, DE, or UK. Don’t tie the country field to the ISOCountry picklist; this picklist is reserved for Employee Central.

Types of Permissions

The types of permissions include:

  • Read (View) permission allows the appropriate user to read the fields.

  • Write (Edit) permission allows the appropriate user to edit the fields; users who have write permission inherently also have read permission.

    Code block is displayed.

Process for Enabling Dynamic Groups

Dynamic groups can be associated to permissions. This feature does not consider groups from Manage Recruiting Groups under administrator.

To enable dynamic groups, proceed as follows:

  1. Log in to Provisioning and navigate to Company Settings.

  2. Select the checkbox for Dynamic Groups V2 (My Groups) and click Save.

  3. Log in to the internal application as an administrator user and navigate to OptionsGroups.

  4. Create a dynamic group and save it.

  5. Associate that dynamic group in the candidate profile.

Code block is displayed.

Note

Refer to the Dynamic Groups section of the Recruiting handbook, materials in THR80, SAP SuccessFactors Platform academy, or other available materials for more information.

Summary

  • Enable the candidate profile and configure essential profile fields to capture relevant candidate information.
  • Instruction text can be configured in the meta section and can be same or different for internal or external candidates.
  • Types of permissions include: Read (View) and Write (Edit).