June 2020 Release: Minor Enhancements

2020.06 GA Release (Package Version 5.19)

Global: Core Package Triggers can be Deactivated at an Org, User, and Profile Level

The 2020.06 GA Release contains a new Custom Setting that can be used to deactivate package triggers not only at Org level, but also at a UserClosed In Salesforce terminology, this is anybody that has login access to an instance. In BH4SF instances, usually the staff of recruiting companies or Profile level. This is particularly useful during data migration, when turning off triggers for all users in a live Org is not a viable option.

When multiple settings are in place, the hierarchy logic checks the Org, profile, and user settings for the current user and returns the most specific, or lowest, value. In the hierarchy, settings for an Org are overridden by profile settings, which are overridden by user settings.

These are the triggers that can be deactivated:

Configuration Steps

  1. Go to Setup > Custom Settings > Triggers Configuration (TR1__Triggers_Configuration__c) and click the Manage Records link.
  2. To deactivate triggers at Org level, click the New button in the top section of the page and enable the required checkboxes there.
  3. To deactivate triggers at User or Profile level, click on the New button in the bottom section of the page and enable the required checkboxes there. You will need to select either User or Profile.

The settings to disable triggers at an Org level in Custom Settings > Talent Rover Properties have been deprecated and should no longer be used.

ATS v2: Align Behavior Between Job and Candidate Views When a Job Status Equals Closed

Previously, if candidatesClosed A person looking for a job. A candidate can also be referred to as a Job Seeker, Applicant, or Provider. were moved to a different stage on a job that had a Job Status of Closed, ATS v2 for JobsClosed A job (vacancy, position, role) is an opening for which a customer's client needs a placement. and ATS v2 for Candidates behaved differently.

With this release, both Job and Candidate views of ATS v2 allow actions when the Job Status equals Closed. System Administrators can change this through a Custom Setting and disable actions for closed jobs.

Configuration Steps (Optional)

To prevent users from performing any action or candidate moves on closed Jobs, follow these steps:

  1. Go to Setup > Custom Settings > ATS Configuration Settings.
  2. Select the Disable ATSv2Closed In BH4SF, the newest version of the ATS tool (Application Tracking System) actions for Closed Jobs checkbox (This controls the behavior of both ATS for Jobs and ATS for Candidates).

ATS v2: Offer Data Entry Page Enhancements

When multiple candidates are selected and moved to the OfferClosed The fourth Stage of Job application flow. This is when the candidate is offered the position (details about salary, locations etc are shared and candidate decides if he wants to take the job) stage, there is now the option of replacing the current data entry page with a new data entry page that uses a more efficient grid-like layout, similar to what is used for the Mass PlacementClosed The stage that occurs after a candidate accepts a job offer and facilitates their information being copied to the back office. page.

Current data entry page:

New data entry page:

Configuration Steps

  1. Go to Setup > Custom Settings > ATS Configuration Settings.
  2. Select Enable grid format for Offer page.
  3. You will also need to configure what Job details are displayed in the top section and what Application V2Closed A BH4SF custom object introduced when new data model ATSv2 was added to the core product fields are displayed in the bottom section. These two field sets control what is displayed:

ATS v2: Send Out Schedule and Internal Interview

Copy to All button Can Customize What is Copied

When multiple candidates are selected in ATS v2 and Send OutClosed The third Stage of Job application flow. This is when the recruiter sets up a job interview between Candidate and Client. Schedule is then selected, the Send Out Schedule page displayed has one section for each selected Candidate. The Internal InterviewClosed The third Stage of Job application flow. This is when the recruiter sets up a job interview between Candidate and Client. page behaves the same way. Instead of manually copying data from the first schedule to the others, users can click the Copy To All button (right top corner). Currently a set number of fields get copied, which cannot be changed.

This release introduces the option to configure which fields get copied when the Copy To All button is clicked for both the Send Out Schedule and Internal Interview pages.

Configuration Steps (Optional)

Out of the box, all the available fields are included in the Copy To All action. To customize the fields that are copied use the new Custom Metadata Type Copy To All Customization.

  1. Go to Setup > Custom Metadata Types > Copy To All Customization (TR1__Copy_To_All_Customization__mdt).
  2. Click on Manage Records.
  3. Select or deselect the fields desired. Field names preceded by "II" are specific to the Internal Interview page, while those preceded by "SoSClosed In BH4SF, this is an abbreviation of 'Send out schedule'." are specific to Send Out Schedule.

Global: TR1 Package Code Base supports API v48

The TR1 package has been updated to fully support 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. v48 which allows Bullhorn for Salesforce to use the latest features of Salesforce.

No configuration needed

Daxtra: Fix for Error 411 when Parsing Resumes

Error 411 was reported by several customers and this upgrade provides a solution. If your Org was affected please contact Bullhorn for Salesforce Support and request to be switched to a new DaxtraClosed A BH4SF partner. One of the Search and Match / Resume Parsing services providers integrated with BH4SF extractor (CVX-EU-2).