Leveraging the Unified Job Requisition Data Model for Recruiting

For each country/region you are posting/advertising jobs in, you will need to create a Job Location Long Format. If you do not configure the long format for a country/region, it will default to the following format:

12345

[address1]<br/>
[address2]<br/>
[city],[state_name][postal_code]<br/>
[country_name]<br/>

Ensure that your System Admin has the following Role-Based Permissions:

• Administrator Permissions→Manage MDF Recruiting Objects→Job Location, Job Location Long Format, Job Location Short Format, Job Location Long Format Configuration Fields, Job Location Short Format Configuration Fields (provide all permissions to your System Admin)

Ensure that your Recruiting users have the following Role-Based Permissions:

• Administrator Permissions→Manage MDF Recruiting Objects→Job Location, Job Location Short Format (provide View permission, at minimum)

1. Navigate to Admin Center→Configure Object Definitions page in Admin Center.

2. Create a new Job Location Long Format Generic Object.

3. Update the following attribute values for a specified job location in Admin Center→Manage Data→Job Location Long Format:

   • externalCode
   • name
   • country

4. Add the respective address formatting fields as desired.

   Note

   When working with multiple countries/regions, it is recommended to use the Import/Export Data functionality to create object data in bulk.

When creating Job Location Short Formats, you will want to consider what job location data is needed for job postings. For example, if you wish to improve the candidate’s search experience within Career Site Builder, it is helpful to include fields within the short format, such as "Location Search Synonyms".

You can create as many short formats as desired, for different countries/regions. You can configure the Job Location Short Format Object field on the Job Requisition, allowing recruiting users to select which short format they wish to use. Otherwise, you can use business rules to autopopulate this field if there is a standard that should be followed.

1. Navigate to Admin Center→Manage Data.

2. Create New→Job Location Short Format.

3. Add the desired attribute values to be displayed when the job is posted.

4. Use separators (commas, spaces, hyphens, new lines, semicolons, pipes, underscores, slashes, and colons) to distinguish the field attributes when the location data is displayed in the job posting.

Before enabling the Unified Data Model, you must first create Job Location data, ensure that all job requisition templates have the standard Job Location GO field defined, and populate the Job Location data in your existing job requisitions.

To support this process, various tools have been created to help the migration of location data to the Job Location GO field. Customers can use one of the following methods to migrate their data:

• Migrating Data with a Scheduled Job
• Migrating Data Manually (using Business Rules)

Regardless of which method is chosen, initial mapping of Job Location data must be completed. This will help the system to identify which Job Location object should be selected for each job requisition template when running the migration job or using business rules.

To ensure the location mapping works successfully, ensure that you have the location data you need in each job requisition to be able to correctly map which job location should be selected. For example, the following location data is required for the field mapping:

• City
• State/Province
• Country/Region
• Zip/Postal Code

If you are using the Location Foundation Object, you can simply map all fields to the existing Location object. You will want to ensure that your Location Foundation Object values have complete and accurate data. However, if you are using individual fields, ensure that all fields are completed with accurate data to ensure the migration job runs successfully. If data is missing in an open job requisition, such as a zip code, the migration job may not populate the Job Location value as expected.

1. Provide the following permission for the System Admin (or necessary) roles in Manage Permission Roles: Administrator Permissions→Manage Recruiting→Set Up Job Location Mapping And Initiate Migration.

2. Navigate to Set Up Job Location Mapping And Initiate Migration.

3. Select the job requisition template you wish to map.

4. Map the required fields as required.

   • If using the Location Foundation Object, you can map all fields to the Location object.
   • If using individual fields, map the fields as necessary.

5. Select Save.

Now that the field mapping is complete, you are ready to migrate your location data using the migration scheduled job, or manually using business rules.

Once you set up the field mapping for the Job Location data migration, you can use the Initiate Migration option to trigger a scheduled job that makes the following changes:

• Adds the standard Job Location field and field permissions to each mapped template, if not present already.
• Creates Job Location object values based on the existing location data in each requisition created from a mapped template (for example, if you only mapped one job requisition template, the system would only create Job Location data from the job requisitions created from that template. Any other job requisitions created from an unmapped template will be ignored.)
• Sets the Job Location value on each requisition created from a mapped template, if the Job Location field is empty.

1. Navigate to Set Up Job Location Mapping And Initiate Migration.

2. Ensure location field mapping is completed and saved.

3. If you wish to include closed job requisitions in the migration job, select the date you wish to include requisitions that were created on or after. If you do not want to migrate closed job requisitions, do not provide a date.

4. Select Initiate Migration.

5. Navigate to Manage Scheduled Jobs to monitor your scheduled job and its status.

6. Select the details to view more information about how many job requisitions were migrated.

7. Open a job requisition to view the Job Location field and the value selected.

   Note

   • If you can see the Job Location field label in the job requisition, but cannot see the value, ensure that the appropriate Role-Based Permissions were provided for the Job Location object.
   • If you do not see the Job Location field in the job requisition, check the job requisition template at the top of the form (select the i icon to view the template name). If this template was not included in the Set Up Job Location Mapping And Initiate Migration page, the migration job was not completed.
   • Ensure that you review your job requisition template field permissions to ensure that all recruiting operators receive the Job Location field permission, as necessary.
   Review the Created Job Location GO Data

   Once the migration scheduled job has completed successfully, you will see the Job Location values created within Manage Data→Search for Job Locations, and view the values. When the system creates these values, you will see the following data migrated to the new object:

   • External code
   • Location name (combination of Country, State, and Zip Code)
   • City
   • State/Province
   • Country
   • Postal Zip Code
   • Effective Start Date

   Note

   Other fields stored within the Job Location object (for example, Neighborhood, Sales Region, and so on) will be left blank. These fields must be completed manually through an export or can be updated individually using Manage Data.

Instead of using a scheduled job to update your existing job requisitions, you can use a business rule to ensure that you have more control over which job requisitions are affected, and when to populate the Job Location field with data. This option is great for customers who want to control exactly which job requisitions should be updated with Job Location data.

Using the Get Job Location () rule function within business rules, you can create business rules that set the value of the Job Location field whenever a specified trigger event occurs. The function retrieves the appropriate job location in the Job Location object, based on the field mapping and on existing data in the job requisition. You can use it to set the value of the Job Location field.

• You've configured a field mapping for each job requisition template on the Set Up Job Location Mapping And Initiate Migration page.
• Job Location object values have been created as necessary for each location in your organization, and the Job Location field (sfstd_jobLocation_obj) is added to each template that you want to create a rule for.

1. Go to Admin Center→Configure Business Rules.

2. Create a rule for the Configure Business Rules on Job Requisition scenario.

   Note

   Choose a template for which you've completed the field mapping. Don't select Job Requisition (All). You need to choose a specific template.

3. Choose Field Change or Save as the purpose or trigger event that executes the rule. An initialize rule doesn't work for this purpose.

4. If needed, configure an If statement. If you don't, the rule always executes when a trigger event occurs.

5. Configure the Then statement to set the value of the Job Location field using the Get Job Location () function.

   • In the left expression, be sure to select the standard field Job Location (sfstd_jobLocation_obj) and not another location-related field (such as Location).
   • In the right expression, select the function, select the Get Job Location () as the Value. Then select Job Requisition Template as the argument of the function. (No other selection is allowed.)

6. Repeat these steps for each job requisition template.

7. To activate the rules, go to Admin Center→Manage Rules in Recruiting and assign each rule you created to its corresponding template.

   Note

   • For Field Change rules, you can choose which fields trigger the rule.
   • If the Job Location field is set as a multi-select field, then you will look for the Primary Job Location field within your business rule.
   • If the Job Location field is not set to multi-select, then you will see the Job Location field within your business rule.

   

The brand migration job will help the system convert any of the following fields and its data to the standard Marketing Brand GO:

• Picklists
• Text
• Object

1. Navigate to Admin Center→Scheduled Job Manager.

2. Select the Job Scheduler tab, then + Create Job Request.

3. Select the job type: Migrate Brand to Marketing Brand on Job Requisition.

4. Once the job has been completed, review the details in Monitor Job to ensure nothing has failed.

The following object fields should be added into the Job Requisition templates:

• sfstd_jobLocation_obj - Field Type=Object
• sfstd_jobLocationShortFormat_obj - Field Type=Object

Based on the requirements, these fields can be manually populated or business rules can be leveraged to autopopulate the values as needed. Remember to permission the fields as necessary within the Job Requisition templates.

1. Add object field: sfstd_jobLocation_obj - Field Type=Object

   1. Configure the sfstd_jobLocation_obj as the standard Field-ID

   2. Configure the Field Label (as desired)

   3. Use Object Type: JobLocation in the job requisition XML template. This field can be configured as a multi-select field, if necessary.

   Note

   When using the Set Up Job Location Mapping And Initiate Migration tool, the job will automatically add the standard field to all templates missing the field definition (by default). While permissions are also added, it is important to review the permissions granted within each Job Requisition template and make the changes as necessary.

2. Add object field: sfstd_jobLocationShortFormat_obj - Field Type=Object using the field definition below:

   Field Definition
   Code Snippet

   Copy codeSwitch to dark mode

   12345678
   
   <field-definition id="sfsf_jobLocationShortFormat_obj" type="object"
   required="false" custom="false" object-type="JobLocationShortFormat">
   <field-label><![CDATA[Location Formatting]]></field-label>
   <field-label lang="en_US"><![CDATA[Location Formatting]]></field-label>
   <field-description><![CDATA[]]></field-description>
   <field-description lang="en_US"><![CDATA[]]></field-description>
   </field-definition>

3. Make the following changes to the field definition:

   1. Configure the sfstd_jobLocationShortFormat_obj as the standard Field-ID.

   2. Configure the Field Label (as desired).

   3. Use Object Type: JobLocationShortFormat with multi-select field set to False in a job requisition XML template.

Once the data is migrated, you need to reindex your job requisitions with the updated job location information.

1. Run the Rebuild Posted Job Requisition Search Index job in Scheduled Job Manager to index the migrated data in the database before Career Site Builder consumes it.

   Note

   .

   If you make changes to the job requisition, ensure to reindex it again to store the data.

2. Verify the Unify Configuration MDF Object to view the status of all the migration processes required to reindex the job requisitions available on your instance.