Mapping Job Requisition Fields for the Real Time Job Sync

The next large synchronization that needs to be configured is the Real Time Job Sync. Before configuring this integration job, you first need to complete the job requisition data mapping, which identifies which fields in the job requisition should be used for Career Site Builder (if the Unified Data Model is not enabled), Recruiting Advanced Analytics, and XML feeds.

The following should be considered when completing the data mapping:

• System requirements: Career Site Builder accepts a total of 19 standard fields (for example: city, state, zip code) that can be mapped from the job requisition, along with 5 custom fields that can be used as required. This field mapping controls which fields can be used from the job requisition in Career Site Builder features such as job page layouts (job posting pages), search filters, and category page rules.
• Limitations: The customer will most likely have more than 24 fields in their job requisition template; therefore, you may need to be strategic in the field mapping approach.
• Leading practices: To ensure your customer’s configuration is set up successfully, use leading practices for configuring the job requisition data mapping and recommendations.
• Unified Data Model: When the Unified Data Model is enabled, the field mapping for job postings, search filters, and category pages is not required. However, the field mapping is still required for Advanced Analytics and XML feeds.

This example assumes that your customer has enabled the Unified Data Model or is using the Location Foundation Object, so all location fields are mapped to Location.

Mapping is completed from Admin Center→Setup Recruiting Marketing Job Field Mapping.

Leading Practices for Mapping Department and Dept Fields

The department field is most important for primary categorization, such as for category page rules and search results. The use of a secondary department field (field ID="dept") is another leading practice. Many customers may use this field as "Function," which is used for job classification, often on job boards.

• Both fields (department and dept) need to be on the job requisition template, though they do not need to be visible to all users and may be populated by Position Management or recruiting business rules.
• Sometimes both fields are populated with the same values.

For our use case, we will populate the department field with the name of Best Run’s actual departments, though the names may be modified to be easily understood by external candidates. Remember to make it easy for candidates to search for jobs. We will populate the dept field with the job function (function picklist), to be used primarily for job distribution.

Note that Category in CSB needs to be populated with the data from the job requisition Department field, and Department in CSB needs the data from the Function field.

Remember that how you configure the job data is dependent upon your customer’s needs.

• Configure Real Time Job Sync after completing job requisition data mapping, which determines what fields are used for Career Site Builder (CSB) (if Unified Data Model isn’t enabled), Recruiting Advanced Analytics, and XML feeds.
• With Unified Data Model enabled, mapping isn’t needed for core CSB features (postings, search, filters) because CSB can reference all job requisition fields directly.
• If the Unified Data Model is not enabled, mapping key fields correctly is critical to ensure that Career Site Builder references job requisition data correctly.