Job Profile Builder offers a powerful way to import and export content easily and implement multiple changes at once, with the Manage Job Profile Content Import/Export tool.
Some of the most relevant entities to import/export content are:
- Family
- Role
- Role-Job Codes
- Role-Mapped Competencies
- Role-Mapped Skills
Importing job roles is beneficial as it enables you to create a family and roles, map job codes, and map competencies and skills all from a single tool. To import each of the entities, you have to download the data import file template, with or without existing data.
Export Job Roles
Navigate to Manage Job Profile Content Import/Export using Action Search, and on the Download Data Import File Template, select the entity. A confirmation dialog will ask if you would like the template to be filled with existing data. Select Yes or No as preferred.
If you choose Yes, am MDF Data Export job type will run to export the data. Navigate to Scheduled Job Manager and confirm the results on the Job Monitor tab.
When the job shows Completed status, select the View Details option, which will open the details of the MDF Data Export job. A Download Status link should be available to download a ZIP file with the Job Profile Content data requested.
Open the ZIP file and select the CSV file with the data, which will be named [EntityName.csv]. In this example: Role.csv.
The first two rows should never be modified. As for the columns, see the details in the table below:
| Name | Description |
|---|
| OPERATOR | This option can be used to Delete MDF Data through import. Depending on the entity, the operator might be different (Delete, Clear or Delimit). For the Role, DELETE is the operator supported. |
| name | Title of the Job Role. There will be a defaultValue, US English, and as many columns as languages are enabled in the instance, so translations can be included in the import file. For entries that don't have a translation to a specific language, the default value won't be used. |
| family.externalCode | In this column, the GUID corresponding to the family must be added. The Family GUID can be checked in Manage Job Profile Content or by exporting the families. |
| createdLocale | The language that the role is to be created in (generally en_US). |
| status | A for Active, I for Inactive. |
| externalCode | GUID for the Role, which is a system-generated ID given to any object created in the system. It should be left empty when importing for the first time. |
| subModule | It is very important that for newly created objects, the subModule field is always left blank. When looking at your exported data, you may spot some objects with subModule set to RCM. Note that this is to show that the object in question is a copy of an existing JPB Object, created for the sole purpose of a job requisition based on the Job Profile that contains that object (which can happen to all the JPB objects). Being so, all the objects flagged with subModule RCM won't display under Manage Job Profile Content, as they are only used on that specific Job Requisition. As a best practice, if an object has subModule RCM, leave it as it is, and if it is blank, leave it as blank. Never change the subModule of an existing object, as this may break your JPB Data and cause inconsistencies that are time-consuming to fix, as well as possible data loss. |
To import the CSV file, navigate to Manage Job Profile Content Import/Export, and select the following details:
- Type: Role
- File: Select Choose File and locate the Role.csv to import.
- File Encoding: If you have translations with special characters, you may select Unicode (UTF-8).
- Purge Type: Incremental Load
- Date Format: MM/DD/YYYY
Select Validate and navigate to Scheduled Job Manager→Job Monitor to confirm the import results. If the validation is successful, repeat the steps and choose the file again, but now you need to select Import.
Verify the results in Scheduled Job Manager→Job Monitor.