February 2020 Release Minor Enhancements

2020.02 GA Release (Package Version 5.6)

ATS v1: Closing Report Edit Page - Support for Lookup Filters

It is now possible to have filters for the lookup fields on the Closing Report Fifth Stage of Job placement flow, a Candidate that reaches the Closing Report Placement stage has been assigned to a job. In BH4SF, a 'Closing Report' is a record that captures all the information related to the newly filled position (name of Candidate, position, salary, start date, which recruiter gets credit for the hire etc.) edit page for ATS v1.

A Custom Metadata Type called Closing Report Lookup Filter Mapping has been added. It includes two fields that can be used to configure filters for any lookup field displayed on the Closing Report edit page.

• Field Name: stores the 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. field name of the Closing Report lookup field that requires filtering
• Filter Logic: stores the lookup filter logic

Configuration Steps

Go to Setup > Custom Metadata Types > Closing Report Lookup Filter Mapping

Create a .mdt record for each lookup field that needs filters

In Field Name, enter the API name of the lookup field you want to filter.

In Filter Logic, specify the filter criteria a record must meet to be included in the lookup.

Example

In the Timesheet Approver The person that approves/rejects Consultant's Timesheets/Expenses (usually a Client Contact, or Hiring Manager) lookup field, to show only 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). that have "Is Timehseet Approver?= True" and that have Email populated:

1. Create a new record against the Closing Report Lookup Filter Mapping Custom Metadata Type.
2. In Field Name, enter: TR1_Timesheet_Approver_c
3. In Filter Logic, enter: Is_Timesheet_Approver__c = true AND Email != ''

ATS v1: Add an Option to Disable Triggers that update Application/Submittal/Send Out Owners When the Contact Owner is Changed

The following three managed fields get updated automatically whenever the Contact Owner field (OwnerId) on the related Contact record is changed:

• TR1_Applicant A person looking for a job. A candidate can also be referred to as a Job Seeker, Applicant, or Provider._Owner_c (Application First stage of Job placement flow (Application> Submittal>Interview>Offer> Placement) object)
• TR1_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._Contact_Owner_c (Submittal object)
• TR1_Interviewee_Owner_c (Send Out The third Stage of Job application flow. This is when the recruiter sets up a job interview between Candidate and Client. object)

This release introduces the option to disable these triggers to stop the Contact Owner field from being updated.

Configuration Steps

To disable one or multiple triggers:

1. Go to Setup > Custom Settings > Disable ATSv1 Record Owner Updates
2. Select the checkboxes as required
   

Job Lead: Custom Field Mapping when Converting a Job Lead to a Job

The field set ConvertJobLeadToJob is deprecated as the field mapping process now uses a new Custom Metadata Type called JobLead Conversion Mapping. Most commonly used fields types are supported when you are mapping data from a Job Lead Name of BH4SF custom object. It stores details about a Job position not yet advertised or confirmed by a potential Client. Once the Client agrees to use the recruiter's services to fill the open position, then a Job Lead can be converted into Job record. field to a Job A job (vacancy, position, role) is an opening for which a customer's client needs a placement. field.

• Text
• Picklist
• Checkbox
• Number
• Email
• Date
• Datetime
• Time
• Currency

Configuration Steps

1. Go to Setup > Custom Metadata Types > JobLead Conversion Mapping (TR1__JobLead_Conversion_Mapping__mdt)
2. Create a .mtd record for every Job Lead field that you want to map to a Job field
   

Example

The screenshot above shows how the .mtd record is configured to map the value from the Account field on a Job Lead record to the Account field on the Job record during Conversion.

Textkernel: Parsing Debug Log to Auto-delete After "X" Days

This enhancement to the Textkernel Integration gives the option of setting up an auto-delete action for the Debug Logs created during the resume parsing process (v.3.418 onwards).

Users can choose how long the logs are stored by setting the duration using a new Custom Setting.

Configuration Steps

To enable the auto-delete action:

1. Go to Setup > Apex Classes and click on the Schedule Apex button.
2. Enter a name in Job Name (for example "TextKernel A BH4SF partner. One of the Search and Match / Resume Parsin services providers integrated with BH4SF Delete Debug Logs").
3. In the Apex Class lookup field, select DeleteDebugLogsScheduler.
4. Complete the section Schedule Apex Execution by entering the preferred date/time for the execution.
   • Schedule this to run daily.
5. Click Save.

By default, the Debug Logs will be deleted after 30 days. If you want to change this, follow these steps:

1. Go to Setup > Custom Settings > Talent Rover Properties.
2. Scroll down to the Delete Logs After field and enter a number.

Disable the Paste Resume Option in Document Parser

System Administrators can now hide the Paste button from the Document Parser pop-up to require resumes to be uploaded only.

Configuration Steps

1. Go to Setup > Custom Settings > Talent Rover Properties and click on Manage Records.
2. De-select Enable Paste Functionality