Off Limit Icon and Ranking Pop-Over in Omnitable

Overview

To enhance the user experience when viewing Off Limit 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). within the context of a job A job (vacancy, position, role) is an opening for which a customer's client needs a placement., the behavior of the Off Limit icon has been improved.

Previously, users could only see the highest-ranking Off Limit policy, which often duplicated the policy already associated with the current job and provided little additional value.

With this update:

• The Off Limit icon now takes the current job record into account.
• When hovering over the icon, users will see the next most relevant Off Limit line item in a pop-up, offering clearer context and more actionable information.

This change ensures users have better visibility into applicable Off Limit policies without unnecessary duplication.

Where the Feature Is Available

The new Off Limit icon with job context awareness is supported in the following locations:

• Job ATS
• Omnitable Generic/reusable component that can be added to pages to show a fully configurable/customizable list of records and actions. ATS
• Omnitable Job Role A job (vacancy, position, role) is an opening for which a customer's client needs a placement.

How It Works

The Off Limit Info object serves as a summary, storing all policies applied to a contact, specifically the related list of line item records. The Policy field continues to display the highest-ranking line item policy for that contact.

In certain places where the Off Limit icons are displayed, such as on the Job ATS, the context of the job is used to select which line item rank field will be used to render the icon and the pop-over.

The Evaluation Order

• If Line Item Rank 1 is not populated, no O/L icon is displayed.
• If the Line Item Rank 1 is not related to the current job, this line item will be used to display the icon.
• If Line Item Rank 1 is related to the current job (via Line Item Exempt_JobId__c field), then Line Item Rank 2 may be used:
  • If the Line Item Rank 2 is present, it will be used whether it's related to the current job or not.
  • If no Line Item Rank 2 is present, no O/L icon is displayed.

Example

A candidate A person looking for a job. A candidate can also be referred to as a Job Seeker, Applicant, or Provider. has 1 line item record from an ATS stage policy for the submittal stage.

In the job where the candidate is at the submittal stage, no Off Limit icon is displayed in Job ATS (because the line item is related to the current job and there is no Line Item Rank 2).

However, in another job where this candidate is being considered, this line item is used to display the Off Limit icon (because the line item is not related to that job's context).

Technical Details

Two new fields have been added to the Off Limit Info object:

• Line Item Rank 1 - Stores the first winning policy line item
• Line Item Rank 2 - Stores the next applicable winning policy line item, selected using the same rules but excluding the first winning line item

These fields are populated either by the calculation engine going forward or by the OffLimitRankingBatch batch job for legacy data.

Ranking Logic

The 'winning' Off Limit Policy is calculated based on the following criteria:

Option 1: If all line items have the Rank field populated

1. Compare the rank: the lowest number wins
2. Compare the end date: later end date wins. An empty end date wins over a populated end date
3. Compare policy CreatedDate: policy with later CreatedDate wins
4. Compare policy behavior: policies with Block type win over Warning
5. Compare line item CreatedDate: line item with later CreatedDate wins

Option 2: If not all line items have the Rank field populated

1. Compare policy behavior: policies with Block type win over Warning
2. Compare line item CreatedDate: line item with later CreatedDate wins
3. Compare the end date: later end date wins. An empty end date wins over a populated end date
4. Compare policy CreatedDate: policy with later CreatedDate wins

Configuration

Post-Deployment Steps

1. Run the batch job

   The OffLimitRankingBatch job must be executed to support historical Off Limit Info records. Upon completion, a BHLO_Log__c record will be created to log the batch run.

   Execute the following in Anonymous Apex:

   Id batchJobId = Database.executeBatch(new OffLimitRankingBatch(), 200);

   In subscriber orgs, add the namespace prefix: new TR.OffLimitRankingBatch()

2. Permissions

   Ensure that users have the 'Run Flows' permission, as the popover is a screen flow executed on hover of the Off Limits icon.

   Go to User In Salesforce terminology, this is anybody that has login access to an instance. In Bullhorn Recruitment Cloud instances, usually the staff of recruiting companies Profile / Permission Set > App Permissions > Run Flows.

Important Notes

• This feature does not overwrite the ability to associate custom icons to Contact Off Limit policies, or define custom icons on an Off Limit policy basis.
• The Off Limit Icon with a popover is only supported in the locations mentioned above.