Daxtra Search and Match: Job Record Match Button

Note: To take advantage of the features mentioned in this documentation, your Org needs to be using Package Version 7.16 or newer. See Release Notes for more details about which features were introduced in each release. If you would like to upgrade to the current release, contact Bullhorn for Salesforce Support.

Overview

The Match button can be added to JobClosed A job (vacancy, position, role) is an opening for which a customer's client needs a placement. page layouts and used to find CandidatesClosed A person looking for a job. A candidate can also be referred to as a Job Seeker, Applicant, or Provider. matching the job requirements.

Match allows you to automatically build a search from your Job record to help you find qualified Candidates quickly. The Match feature is a pre-populated Search. This article shows you how to use the Job Record Match Button.

Using the Match Button

Prerequisites

How it Works

  1. The job is synced with Daxtra and relevant keywords are extracted from the Client Job DescriptionClosed The text that contains all the information related to an open job position (responsabilities, requirements, skills, years of experience etc) field. For example if the skills "developer" and "manager" are extracted, Daxtra then finds Candidates with those keywords in their Resumes.
  2. The results displayed after clicking the Match button can be refined by using the filtering options on the main Daxtra Search page.
  3. The following filters can be auto-populated based on the values in the corresponding Job fields:
    • State Area
    • Regional Area
    • City
    • Function
    • Primary Background

If these are populated on the Search page, ContactsClosed A contact (or client contact) is the person who the recruiter is working with at a Company. In Talent Rover a Contact can be either a Client Contact or a Candidate Contact. Both types of Contacts are stored in the same object (Contact). that don't have an exact match will be excluded from the results. To avoid that, the user can delete the value before searching.

Admin Note:

Values can be removed by adjusting the corresponding Field Set located at Setup > Build > Create > Objects > Job > Field Sets > PrefillDataFieldSet