Overview
Field Mapping allows users to streamline the creation of requisitions by pre-populating or limiting the selections of fields based on other fields.
Audience
Admin
Prerequisites
This feature must be enabled before you can begin using it. Requests can be submitted through the Help Center. Once the feature is enabled, you will see it listed by navigating to your user menu > Admin > ATS > View Field Mapping.
Identify Driver and Driven Fields
To start with Field Mapping, you need to determine which fields (drivers) will control other fields (driven). For example, suppose your company has multiple locations and each location has a limited number of departments. In that case, you can limit the department election (driven values) based on the location selected (driver value).
After identifying the fields you will be using, you need to ensure they are included in your requisition form. Once all the fields are added to the requisition form, you can upload a CSV file that defines the mapping between driver and driven fields. After you have done your original mapping, you can make subsequent adjustments using the Manage Field Mappings link.
Add Fields to Requisition Form
Now that you have identified the fields you will be using, you need to ensure they are included in your requisition form.
Navigate to your user menu > Admin > ATS > View Requisition Library > View Requisition Templates.
Select the desired requisition form name.
Verify the desired fields are included in the Form. If they aren’t, you can drag and drop them into the Form. See the Create Requisition Custom Fields article if your requisition template requires a custom field.
Click Save.
IMPORTANT: Functionality does not support using Unicode characters in field mapping (as part of the field names or dropdown values). Special keyboard characters DO render correctly, though.
- Characters Allowed - !@#$%& and all others;
- Characters Not Supported - Ā ā Ă ă Ą ą Ć ć Ĉ ĉ Ċ ċ, etc.
Create and Upload CSV File
Now that all the fields are added to the requisition form, you can upload a CSV file defining the mapping between driver and driven fields.
Create the CSV file (Excel provides the most accessible method).
- In the first row of the first column, add the name of the driver field. Add the names of the driven fields in the first row of the following columns.
- Add all the values available for the driver field in the remaining rows of the first column. If any of these values can result in multiple values in the driven field, then you must add them multiple times (it will only appear once when creating a requisition). See the sample below.
Location | Department | Custom Field |
Location 1 | Department 1 | Custom Field 1 |
Location 2 | Department 1 | Custom Field 2 |
Location 2 | Department 2 | Custom Field 2 |
Location 2 | Department 4 | Custom Field 2 |
Location 3 | Department 2 | Custom Field 2 |
Location 3 | Department 3 | Custom Field 2 |
Upload the file: Navigate to your user menu > Admin > ATS > View Field Mapping. Choose the file that you created above, then click Upload.
Once the file is uploaded, you will be prompted to map the column name from the file to the Jobvite field name. Evolve ATS will attempt to map these for you, but you must confirm or modify these values.
Click Save.
If there is an alert icon next to the Matching Jobvite field and your file is mapping to standard fields, then you will be prompted to confirm the mapping to the specific values defined in the corresponding section of the Jobvite value.
Once complete, click Save.
Special Case: Driving Job Description
You can set up your field mapping file to drive the content and formatting of your job Description field. This can be used only where the driver field is Job Title (because this is the logical, direct relationship).
NOTE: If desired, you must create a custom field, such as Internal Title, to map to the job Description field. The standard Job Title field cannot be used for this purpose.
To display bold, italic, bullets, etc., in your job description using this method, you must populate the CSV file with the job description written in HTML format.
Requisition Fields that do not Support Field Mapping
The following requisition fields do not support the ability to be field mapped (these fields cannot be both parent and child of a field mapping):
- Posting Type
- Publishing Option
- LinkedIn Recruiter System Connect
- Company Name
- Created On
- Updated
- Created By
- Recruiter
- Hiring Manager
- Agency Access
- Approver
- Approver Status
- Approval Rejection Message
- Approval Request Submitted
- Approval Request Updated
- Client
- Client Contact
- Interview Evaluation
- EEO Category
- ApproveDate
- Time to Fill
- Filled On
- Candidate Status
- #Candidates
- MyRequisition
- Full Status
- Region
- Contact Information
- Accepts Calls
- Job Link
- Start Date
- End Date
- #Candidates per Source
- #Candidates per Source Detail