Quick Access to My Projects

In the existing lookup, when showing jobsClosed A job (vacancy, position, role) is an opening for which a customer's client needs a placement., there was previously no way of creating a list view to see My ProjectsClosed Object. Its records store details about a Job position to be filled or My Jobs, as this requires a relationship to another object (TR1__Team_Member__c).

The newly introduced lookup custom filter, enables administrators to better determine what My Projects or My Jobs actually means, by defining a SOQL query to be more precise on the filtering logic and related object.

Example: For example My Projects in one context could mean (as a Team Member who is Active) show me all the jobs (projects) linked to my user.

Prerequisites & Configuration

  • The change is available from version 2025.03 and above.
  • Ensure Generic Lookup is configured for the Org
  • Custom Filters should be enabled for Generic Lookup

Terminology

For the purpose of this document, Projects will here on in, be referred to as Jobs in line with our standard terminology.

Introduction

It is now easier to quickly locate the jobs you are looking for when running actions for candidatesClosed A person looking for a job. A candidate can also be referred to as a Job Seeker, Applicant, or Provider., such as adding them to a jobClosed A job (vacancy, position, role) is an opening for which a customer's client needs a placement.. Instead of having to change the view of the lookup with each action, jobs can now be filtered to only show the jobs that you own and are actively working with.

Example

A custom filter can also be used for filtering 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). in the Generic Lookup.

When the Generic Lookup custom filter is configured on an org, it will be available in the lookup at the top of the list views list by default for all users. Users are still able to use Recently Viewed, Global Search, or select from existing previously created list views as needed.

Data Model

Entity Details

sObject APIClosed 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

The API name of the sObject (with namespace prefix if applicable) used for the search.

Custom Label Name

The custom label used as the filter name, for example ‘My jobs’.

Filter WHERE Clause

A WHERE clause for the Generic Lookup custom filter that follows SOQL syntax and uses {currentUserId} as a reference for the ID of the user performing the search. It may include an ORDER BY clause to control the order of the query results. For example: WHERE OwnerId = {currentUserId} ORDER BY Name DESC NULLS LAST.

Active

When checked, the custom filter will be available in Generic Lookup for selected sObject for all places it can be used e.g. Send Outs, Market Intelligence Lookup etc.

Pin Functionality

We now have the ability to remember list view preferences for the Generic Lookup component by pinning or unpinning the list view, when list view filters are enabled.

Example: For example, if you want to mainly search on a filter of My Jobs, this view can be pinned to be reused for when you are next looking for a job, without having to select this view from the dropdown.

Individual users can change the selection from one favorite view to another, by clicking on Change List ViewClosed One of the three user Interfaces in ATS v2 (the others being Kanban View and Table View) and selecting the new favorite view as needed.

Post Deployment Steps

To enable a My Jobs custom list view, a Custom metadata type record should be created and activated.

By default there is already a My Jobs filter and it is not activated.

  1. Got to Setup > Search "Custom Metadata Types".
  2. Find Generic Lookup Custom Filter and click Manage Records.
  3. Click New (or Edit for existing record(s)).
  4. Populate the following fields:
    • sObject API Name
    • Filter WHERE Clause
    • Custom Label Name
  5. Check Active checkbox
  6. Click Save.