October 2024 Release: Resolved Issues
2024.10.5 GA Release - Package Version 8.17.4
ATSv2
All ATS Sub Status Stages Incorrectly Displayed in Job Type Stage Dropdown
The Stage drop down will now correctly display only the stages configured for that job A job (vacancy, position, role) is an opening for which a customer's client needs a placement. type.
ATS Actions Not Working for Recruiter Users
Non-admin users are now able to perform ATS actions due to an inclusion of the Job Record Type permission in the ATSv2 In BH4SF, the newest version of the ATS tool (Application Tracking System) Permission Set.
Job Sync Issue: New JBA Creation Failed to Sync with TK
When successfully creating a JBA using the Apply URL link, the Job will now sync with TK An abbreviation for Textkernel thanks to updated logic.
Past Canceled Interviews Don't Show in View Schedule
Logic has been updated to get the Send Out The third Stage of Job application flow. This is when the recruiter sets up a job interview between Candidate and Client. ScheduleV2 Cancel Only Future setting to depend on Job Record type for the Job ATS. The same logic has been applied to the Candidate A person looking for a job. A candidate can also be referred to as a Job Seeker, Applicant, or Provider. ATS.
For configuration details, see Canceled Interviews with Past Date.
Stage Status Chevrons Grayed Out for Open Jobs in Candidate Contact Records
When the Longlist is added to the ATS, the stage status chevrons will no longer be grayed out for open jobs A job (vacancy, position, role) is an opening for which a customer's client needs a placement. when the candidate is in the Longlist stage.
Translations Not Working on ATS Modals
ATS modal windows now appear with the appropriate label.
Executive Search
Off Limits Policies Not Sorted Alphabetically
We are now ignoring case sensitivity, so the Off Limits Lightning Web Component policies will now sort alphabetically.
- Additional user updates have been made to include the following:
- Only Ascending and Descending sorting
- Icon display changed to show the column is inverted.
- This change follows standard Salesforce behavior.
USAM
Breadcrumb Display Incorrect When Boolean String Pasted into Search
Validation check added to look for double quotation marks used incorrectly in the USAM search bar. In the event of an incorrect usage, a toast error message will display.
Default Search Displays No Results Upon Opening
When opening Universal Search and Match (USAM) for the first time in a user’s current session, the page will now load and results will display properly, even when the Default search is used.
Job Match Save Search Freezes Without Saving
Empty fields on job records will no longer cause the Job match save and search function to freeze when inserting a new record, even when sharing is enabled. Also, this will now save successfully.
NOT Search Query Synonym Behavior
Logic has been fixed to allow synonyms to be available with the NOT operator.
Packaged Fields from Job Can’t Be Added to the Job Card Fieldset
All job fields are now added to the available fields for the job card field set.
Results Not Loading Correctly Despite UAHQ Configuration
Correct results are now accurate for USAM thanks to a code fix.
Saved Second Search Overrides First
When saving a search as a new search (save 1), the second search (save 2) will now save as well and not override or delete the first saved search.
Slow Typing Response Multiple Facets & Fields
Backend calls have been minimized, allowing characters to appear more quickly. Users can now complete their searches in USAM without delay in all facets, including the City/Zip field in the Location facet and the Complex Search Query field in the Activity Search facet.
Job Search: Sort by Rank Intermittent Functioning
Sort by rank now displays search results in the appropriate order in the TK Job Search, even if a different sort is applied first.
Unable to Remove TK_Years_of_Experience__c field from Breadcrumb
The X button now removes the TK_Years_of_Experience__c field from the USAM breadcrumb. This fix also applies to any other number fields in the USAM breadcrumb trail.
USAM Can’t Override Applicant Header Name on Add to Application Quick Action
The hard-coded value for the Applicant A person looking for a job. A candidate can also be referred to as a Job Seeker, Applicant, or Provider. header name has been removed, allowing the existing custom label “Applicant” to be used.
USAM Users Can’t Share Resumes
Users can now select a candidate and share the candidate’s resume while searching in USAM, and the Share Resume function is opened in a tab if the resume information isn’t accessible.
Various
Job Parser Not Picking Up Array Member from JSON
Job Parser now supports mapping and processing an array of objects in JSON_Path__c to the field on the Job. If we get an array of objects from TK, the updated logic will populate the field with the first element in the array by default.
Textkernel Management Component "Queued for indexing" Inaccurate Number
When viewing the count for “Queued for Indexing” in Textkernel Management Component, inaccurate numbers are no longer given if the result is above 50000.