Candidate Mapping Custom Metadata Type Fields
For each field to be mapped, create a separate Custom Metatdata Type record against the Candidate
A person looking for a job. A candidate can also be referred to as a Job Seeker, Applicant, or Provider. Mapping Custom Metadata Type. The screenshot above shows what a filled in record looks like. Below is a list of the available fields and their function:
| Field Name | Function |
|---|---|
| Label | Master Label (label can be changed) |
| Candidate Mapping Name | Developer Name (label can be changed) |
| Action When used in ATS or Search and Match UI, one of multiple actions available after user has selected a sub-set of Candidates
|
Picklist Values: Merge, Do nothing, Override |
| Object | API API, or Application Programming Interface, is used by customers to create custom career portals or to take advantage of Data Mirror/DataMart. Bullhorn prefers to use REST API. name of Object: Contact, Education History, Employment History |
| Field API Name | API Name of the object field |
| Default Value | Value to be added automatically if a field Value is returned as NULL from parser |
| XPath | Path to the specific node in the XML Used to create custom markup languages in order to display information on the Internet. We use XML when sending jobs to Indeed for syndication. file |
| XML Node | Node in the XML corresponding to the Contact field |
Was this helpful?