June 2025 Release: USAM Features & Enhancements

June 2025 (2025.06 GA Release - Package Version 8.84.4)

Option for ‘OR’ functionality for All Single Facet Field

From this release, users will be able to add the “OR” logic to their searches. Please note that the availability of the “AND” or “OR” logic depends on what operator gets selected, as per examples provided in the table below.

This is now the expected behavior. There is no need for any configuration.

Operator	Field-types	Boolean logic	Example
Equals	String/Id	OR	OwnerName = "Antonio" OR OwnerName = "Artem" OR OwnerName = "Dima
	Picklist		Country="France" OR Country = "UK"
	Number		NumberOfApplications = 0 OR NumberOfApplications = 1
	Date/Time/ Datetime)		LastModifiedDate = 2025-03-05 OR LastModifiedDate = 2025-02-28
	Checkbox	IS NOT SUPPORTED	DoNotCall = true OR DoNotCall = false
Not Equals	String/Id	AND	OwnerName != "Antonio" AND OwnerName != "Artem" AND OwnerName != "Dima"
	Picklist		Country!="France" AND Country != "UK"
	Number		NumberOfApplications != 0 AND NumberOfApplications != 1
	Date/Time/ Datetime		LastModifiedDate != 2025-03-05 AND LastModifiedDate != 2025-02-28
	Checkbox	IS NOT SUPPORTED	DoNotCall = true OR DoNotCall = false
Greater Than	Number	AND	MinSalary > 1000 AND MinSalary < 2000 LastModifiedDate > 2025-03-02 AND LastModifiedDate < 2025-03-05
	Date
Less Than	Number
	Date
INCLUDES	Multi-picklist	OR	Language = English OR Language = Italian
EXCLUDES	Multi-picklist	AND	Language != English AND Language != Italian

Searchability for Blank/Null/Empty Field Values

Users asked for a consistent way of searching for candidate A person looking for a job. A candidate can also be referred to as a Job Seeker, Applicant, or Provider. records that have no value (NULL, Empty) in a given field so that they could pick up new, stray, incomplete or out-of-touch candidates A person looking for a job. A candidate can also be referred to as a Job Seeker, Applicant, or Provider. in the system and work them.

With this release we have made this option available through configuration. It is now possible to add a Blank Value checkbox to facets that results in the field being included for that search to be considered, even if blank.

Configuration

To configure Search on Blank Fields for a facet, you need to add two parameters to the facet’s configuration:

• showBlankValueCheckbox: A Boolean value for determining if you want the Blank Value checkbox on the facet UI.
• blankValueCheckboxChecked: A Boolean value for determining the default state of the checkbox.

These gets added by going to the relevant facet section:

1. Go to Setup > Custom Code > Custom Metadata Types.

2. Next to Search & Match UI Configurations, click Manage Records.

3. In the Search & Match UI Configurations screen, click Edit next to your desired configuration (EX: Default).

4. In the Search & Match UI Configuration Edit screen, enter your desired values and blank values into the Search And Match Layout field.

   • Note: Be sure to include “showBlankValueCheckbox” as “true” and “blankValueCheckboxChecked” as “true” or “false”, according to your preference.

   • Below is an example of what that entry might look like:

     {

     "visible": "yes",

     "title": "Desired Salary",

     "stickyFields": [],

     "sticky": null,

     "name": "advancedSeparateSearch",

     "layoutIcon": "fa fa-search fa-fw",

     "label": "Desired Salary",

     "items": null,

     "filters": null,

     "editorIcon": "search",

     "showBlankValueCheckbox": true,

     "blankValueCheckboxChecked": false,

     "advancedSearchField": "TR1__Desired_Salary__c"

     },

5. Click Save.

Optimize Page Reloads When Removing Search Terms

Up to this release, removing single search values (breadcrumbs) caused the whole search to rerun. This behavior made adjusting searches inefficient if you wanted to remove more than one value. We have changed to a manual model to allow for a better user experience.

How To

1. Remove the desired value from the breadcrumb.

   Note: If you delete a main picklist value, all related options will also be removed from the breadcrumbs.

2. Click Search to trigger a new search.

Configuration

There is no specific configuration step to be performed but please make sure that the sticky parameter for Country in Location is set to no.

1. Go to Setup > Custom Code > Custom Metadata Types.

2. Next to Search & Match UI Configurations, click Manage Records.

3. In the Search & Match UI Configurations screen, click Edit next to your desired configuration (EX: Default).

4. In the Search & Match UI Configuration Edit screen under the Search & Match Layouts section, ensure the Search And Match Layout field contains a sticky parameter for Country in Location is set to no.

5. Click Save.

Search Job Lookup Using Specific Field Values from Applications/Job Boards

Users reported that when searching in Data Source > Applications/Job Board A website where open jobs are advertised Applications they could only find the related job A job (vacancy, position, role) is an opening for which a customer's client needs a placement. by entering text in the Job lookup. This behavior made it difficult to find the correct job, especially when others had similar or identical names.

With this release we have added the option to configure a set of fields that can be used to find a Job in the Job lookup when working with USAM Data Sources Applications and Job Board Applications.

Configuration

To configure your set of fields to be used to find a Job in the Job lookup, add or update the extraSearchFields JSON node with a comma-separated list of 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. names from the Job object by which the jobs A job (vacancy, position, role) is an opening for which a customer's client needs a placement. records will be searched.

1. Go to Setup > Custom Code > Custom Metadata Types.

2. Next to Search & Match UI Configurations, click Manage Records.

3. In the Search & Match UI Configurations screen, click Edit next to your desired configuration (EX: Default).

4. In the Search & Match UI Configuration Edit screen under the Search & Match Layouts section. In the Search And Match Layout field, add or update the code as follows:

• extraSearchFields JSON Node:
• Location: This is the first item in the searchFilterSections under Data Sources.
• API Names to Add: To define the job search criteria, enter a comma-separated list of field API names from the Job object.
  • Supported Fields: Only text fields (excluding long text and rich text area).
  • Unsupported Fields: Date, datetime, time, checkbox, encrypted, lookup, number, etc.
    • Workaround for Unsupported Fields:
      • Use a text formula field pointing to the Job lookup via CASESAFEID(id) formula.
      • Add the formula field’s API name of this formula field to the extraSearchFields JSON array.

Add:

"extraSearchFields": [

"TR1__Certification__c",

"Custom_Unmanaged_Field__c"

...into the code like this:

"searchFilterSections": [

{

"title": "Data Sources",

"name": "dataSources",

"label": "DataSourceSection",

"editorIcon": "entity",

"layoutIcon": "fa fa-database fa-fw",

"visible": "yes",

"searchFieldSetName": "TR1__Data_Source_Searchable_Fields",

"extraSearchFields": [

"TR1__Certification__c",

"Custom_Unmanaged_Field__c"

]

},

5. Click Save.