October 2020 Release: Minor Enhancements
2020.10 GA Release (Package Version 5.31.2)
: Hide "Send as a single email to all recipients" Checkbox
To prevent users from accidentally enabling this checkbox and sending the same email to multiple recipients a setting has been added to remove this checkbox from the user interface.
Configuration Steps
To hide the checkbox:
- Go to Setup > Custom Settings > Talent Rover Properties.
- Scroll down to the Hide Send as Single Email checkbox and enable it.
: Attach Files from Libraries
Users that store content in Libraries can now attach files from a Library when sending an email.
: Consolidate Emails to Interviewer for
When Candidates
A person looking for a job. A candidate can also be referred to as a Job Seeker, Applicant, or Provider. are moved to the Send Out The third Stage of Job application flow. This is when the recruiter sets up a job interview between Candidate and Client. Stage in there is an option to send an email to the Interviewer Usually the client/hiring manager taking part in a Job interview. A recruiter can also be an Interviewer (Client A Company is the organization where the contact works. This can also be called the Client.), the Interviewee (Candidate A person looking for a job. A candidate can also be referred to as a Job Seeker, Applicant, or Provider.), or both. When multiple Candidates are selected, an email is sent to the Interviewer and Interviewee for each Send Out Schedule. This means if five Candidates are selected the interviewer may receive five separate emails.
This release includes an option to consolidate the emails so the Interviewer only receives a single email. When enabled, on the page the Interviewer(s) are entered in the first section, which is where the Interviewer Email Editor screen is available. In the remaining sections there is a toggle to confirm the email should be sent to the Interviewer but the Email Editor screen is not included. Upon sending the email the Interviewer(s) will receive a single email with multiple invites attached.
Once this functionality is enabled a new option will appear in the Move Forward drop down in . The name of this action can be customized through custom labels.
Configuration Steps
- Go to Setup > Custom Settings > Talent Rover Properties.
- Enable the Allow Single Interviewer Email checkbox.
Email Signature: Option to Always Add Org-level Signature
Currently, when the Org-level signature is configured, users have to check the Add my signature to email checkbox on the email editor page every time they want to have their signature added. With this update, s can set this checkbox to be selected by default, so the Org-level signature is always added.
Configuration Steps
- Go to Setup > Custom Metadata Types > Email Signature.
- Select the Enable Add my signature to the email checkbox.
Timesheets: Setting Added to Customize Chunk Size for Apex Class
Managed Apex Class CreateTimeSheetsByWeekending is used to generate timesheets at the beginning of the week for consulting Closing Reports that meet the specified criteria. CreateTimeSheetsByWeekending has hardcoded batch size of 50.
A new field in the TalentRover Properties Custom Settings has been added to allow configuration of the chunk size for each batch execution. If no value is specified in this number field, the existing value of 50 will be used. This allows users to decrease this number if they are hitting a CPU limit in their Org when the class is executed.
Configuration Steps
- Go to Setup > Custom Settings > Talent Rover Properties > Schedule Timesheet Chunk Size.
- Enter the required chunk size in this field and click Save.
Reference: Filter the Referee Field by Contact Type
For Orgs that use the Reference managed custom object, it is now possible to filter the Referee look up field so that only the chosen type of 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). is shown or searchable, for example Client Contact 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)..
Some configuration is required. See Contact Lookup Filtering for more information.
: Send Email to Rejected/Unrejected Candidate
The option to send emails to a rejected or unrejected Candidate from the Reject/Unreject screen can now be enabled. Once the option is enabled, a Send Email checkbox will be displayed for each Candidate, plus one at the top of the page to Send Email to All.
How it Works
- This is not currently enabled for High Volume (Bulk Mode).
- Candidates are rejected/unrejected when the Reject/Unreject button is clicked. The email editor screen appears after the button is clicked so sending or canceling the email does not update a Candidate's rejected/unrejected status.
- If both rejected and unrejected candidates are selected together, first the rejected candidates will be handled when the email screen is opened. After that email is sent, the email editor will appear again for the unrejected candidates that were selected.
Configuration Steps
- Go to Setup > Custom Settings > ATS Configuration Settings > Enable send email mode.
- Enable this checkbox and click Save.
: Disable sync with Option
s can now opt to bypass the sync with when a Contact is updated, under special circumstances (mass migration, etc.). A new field was added to the Textkernel configuration Custom Metadata Type, called Sync Behaviour.
Field Options
- Do not call sync (only generate the index A collection of files that can be searched by client data entity types. When records can be found in training login, but not the live system, it may require a bootstrap of the index. record): This disables the sync with when a Contact Trigger is fired. If selected, when a contact trigger is fired (for example via the Resume Parser in Global Actions, or any other action that causes a Contact record update) or the Start Index button in the Textkernel Management component is used, the sync process will not start.
- Call a scheduler to sync in another transaction: This uses a scheduler mechanism to call the queueable job A job (vacancy, position, role) is an opening for which a customer's client needs a placement. that syncs the Contact. First, a CronTrigger record is created to run the sync process in another transaction. The scheduler mechanism checks the amount of existing BHTK_IndexerRequest jobs A job (vacancy, position, role) is an opening for which a customer's client needs a placement. and decides to create more jobs if below the maximum threads.
- Call sync in same transaction: (This is the default behavior) When a Contact is updated it calls the sync process (BHTK_IndexerRequest queuable job) from the trigger. It will immediately process BHTK_Indexing_status__c records, in the same transaction of the trigger, not checking the maximum threads.