November 2022 Release: Resolved Issues
2022.11 GA Release - Package Version 6.49
: Interview Scheduling on Same Day Results in Amendment of Existing Schedule
Previously, attempting to schedule a second interview for the same date updated the time on the first interview Send Out
The third Stage of Job application flow. This is when the recruiter sets up a job interview between Candidate and Client. Schedule instead of creating a new, additional interview. Now users are able to schedule multiple interviews for a specific day as expected for both Internal Interview The third Stage of Job application flow. This is when the recruiter sets up a job interview between Candidate and Client. and Send Out Schedule.
: Candidates Table View Displays Job ID Instead of Job Name
The Table View One of the three user Interfaces in ATS v2 (the others being Kanban View and List View) for Candidates A person looking for a job. A candidate can also be referred to as a Job Seeker, Applicant, or Provider. has been corrected so that on the User In Salesforce terminology, this is anybody that has login access to an instance. In BH4SF instances, usually the staff of recruiting companies Interface, the Job A job (vacancy, position, role) is an opening for which a customer's client needs a placement. Name/Hyperlink displays instead of the Job ID.
: View Schedule Not Working for Some Users
The View Schedules function in is now working as expected.
Email Editor: Call List Emails Stuck on Sending Emails Status
This issue impacted the original Email Editor but does not apply to the . The following logic changes were implemented to prevent Call List emails from getting stuck on the Sending Email status:
- Once the middleware is done sending the emails it will set the email record to successful and the EmailTriggerHandler will be activated and used to run into a CPU limit.
- Task creation was moved to a new future Method.
- This future method will be called for a chunk of contactIds of the total 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). in the email. The default is set to 25 contactIds per process with an option to lower that amount when there are many candidateIds.
Current Limitations:
- 50 future methods can be initiated per request. With 25 contacts per future that equals 1250 contactIds. Once the transaction runs out of futures it no longer adds a new task record and an error will be written to the BHLO log.
- If the amount of candidateIds in the email is very high there is a risk of hitting a CPU limit. If both contactids and candidateIds are high, Futures may also run out quickly.
- Large amounts of attachments can still slow things so that 25 contactsIds can't be handled in a single transaction.
- There will be a short delay between the email being set to Success and the actual creation of the tasks.
: Registration Interview Merge Fields Related to Events are Not Merged in the Received Email
Blank merge fields will no longer appear when sending emails from the Registration Interview page using templates with merge fields related to Events.
Consent v2: Send Consent Button Grayed Out on Consent Page
The Send Consent In BH4SF , Consent is used in the context of GDPR or similar data privacy processes. Candidates or Clients are usually asked to consent to the storage or sharing of their personal data. button in the Consent v2 Tool on the main Consent page is now working as expected.
Records with Incorrect Filetype
Records with a PDF file type imported through data migration displayed the incorrect filetype. The missing data is restored when upgrading to the version containing this fix.
Contact Merge Results Multiple Default Resumes
Previously, two default resumes appeared when using the standard Contact Merge function. Now, only the most recently created Contact Document is set as the default resume, based on the CreatedDate field.