Configure JSON Mapping to the Job Record

Navigate to Setup > Custom Metadata Types > Job A job (vacancy, position, role) is an opening for which a customer's client needs a placement. Mapping > Manage Records and customize the mapping from TextkernelJSON to Job fields to suit your business needs.

Baseline configurations are provided and have mapped some of the most commonly used nodes into packaged fields, but it can be entirely customized.

Customization Options

• Change the Job field mapped to a JSON node in the out of the box configuration. The job description contained in the original document is mapped to the Job Description The text that contains all the information related to an open job position (responsabilities, requirements, skills, years of experience etc) field. To instead map it to your external-facing job description field, replace TR1__Client A Company is the organization where the contact works. This can also be called the Client._Description__c with TR1__Client_Job_Description__c in the Field 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 field.
  
• Add new mapping by assigning a job field to one of the JSON node records that is not used in the out of the box configuration. To do this, enter the API name of the Job field in the Field API Name field.
• Create a new Custom Metadata Type record for extra data mapping.
  • In the out of the box configuration the JSON node contactPerson is mapped to Job field TR1_Contact__c. If you always have the same value in both TR1_Contact__c and TR1__Hiring_Manager__c in your Org, you could create a new Custom Metadata Type record to map contactPerson to TR1__Hiring_Manager__c as well.