ATS v2: Lookup Filtering

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.

This article applies to ATS v2s using the ATS v2 data model only.

Overview

This article provides a way of defining the Contact type that should excluded from a lookup field. This method uses a Workflow Rule and Field Update combination.

This article is intended for System Administrators.

How it Works

The Bullhorn for Salesforce package includes a corresponding checkbox field (shown in the third column below) for each of the look up fields listed.

Location	Lookup Field	Checkbox Field (Contact Object)
Application V2 A BH4SF custom object introduced when new data model ATSv2 was added to the core product	Applicant A person looking for a job. A candidate can also be referred to as a Job Seeker, Applicant, or Provider. TR1__Applicant__c	Is_Select_Candidate A person looking for a job. A candidate can also be referred to as a Job Seeker, Applicant, or Provider.__c
ATS v2 - Submittal The Second Stage of Job application flow. This is when the recruiter sends the Candidate CV to the client, a sort of first introduction.	To	Is_To__c
ATS v2 - Submittal	Cc	Is_Cc__c
ATS v2 - Submittal	Bcc	Is_Bcc__c
ATS v2 – Quick Add	Candidate	Is_Select_Candidate__c
ATS v2 – Send Out The third Stage of Job application flow. This is when the recruiter sets up a job interview between Candidate and Client.	Interviewers	Is_Interviewers__c

By default, all checkboxes are set to True which means that all Contacts 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). in the Org are seen as Contacts that need to be shown in the corresponding look up.

For example, if you do not add any configuration and you go to the Interviewer Usually the client/hiring manager taking part in a Job interview. A recruiter can also be an Interviewer(s) field in the Send Out Schedule pop-up, you'll be able to search and retrieve all Contacts in your Bullhorn for Salesforce database.

To control which Contacts are shown in a Contact look up, update the corresponding checkbox field to False. If the checkbox is set to False for a Contact, then that Contact will not be included in the look up field.

For example, once you set up a rule that identifies all Contacts that are Candidates A person looking for a job. A candidate can also be referred to as a Job Seeker, Applicant, or Provider. (not Clients A Company is the organization where the contact works. This can also be called the Client.) and update the Is_Interviewers__c checkbox to False, then the Interviewer(s) look up will only show the Client Contacts 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). in your Bullhorn for Salesforce database.

Configuration Steps

For any of the above look up fields, decide what type of Contact you want to exclude from the selection.
Create a Workflow Rule that defines that type of Contact.
Create an associated Field Update action that will update the corresponding checkbox from True to False.
Activate the Workflow Rule.