February 2025 Release: ATSv2 Resolved Issues
February 2025 (2025.02 GA Release - Package Version 8.44)
Candidate ATS Default View Configuration Ignored
The setting you select in
will now be applied, allowing you to see your chosen view.Candidate ATS: New Offer Data Entry Checkbox Field Always Marked as TRUE
In the Candidate ATS, the checkbox for the New Offer 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) will now reflect how the fieldset is configured on the data entry page.
If No Sub Status is Set, Table Row is Blank
In ATS Table View One of the three user Interfaces in ATS v2 (the others being Kanban View and List View), if no sub-status is set or if it's set for a different stage (not the current stage), the Sub Status column will now display None instead of being blank.
If custom values are added to the Value__c picklist field of the Sub_Status__c object and those values are translated, the translated values will not be shown in the ATS Table View. This will be addressed in a future release.
Inconsistent Sorting ATS and Table Views
Users reported inconsistent behavior when sorting /ordering columns in ATS. This has now been fixed to reflect the following expected behavior:
- Default Sorting Criteria:
- Chevron View: Records are sorted by CreatedDate in descending order (most recent first).
- Table View: Records are sorted by TR1_Stage_c in ascending order (earliest stage first).
- Custom Sorting by Column:
- Users can re-order records by clicking on column headers (one column at a time).
- The chosen sorting order is now persistent meaning it remains saved for each logged-in user, per Job
A job (vacancy, position, role) is an opening for which a customer's client needs a placement. record type, and per ATS View.
- This view is saved until it is changed again.
- Stage-Specific Ordering:
- Records can be sorted by stage using the Stage column header, toggling between:
- Least to Most Advanced
- Most to Least Advanced
- This ordering relies on:
- The correct configuration of packaged and custom stages
- The labels of the stages
- The position
A job (vacancy, position, role) is an opening for which a customer's client needs a placement. of the stages within the overall sequence
- Records can be sorted by stage using the Stage column header, toggling between:
Interviewer Names Field Not Populating Correctly
The Interviewer Usually the client/hiring manager taking part in a Job interview. A recruiter can also be an Interviewer Names and JSON fields on the Send Out
The third Stage of Job application flow. This is when the recruiter sets up a job interview between Candidate and Client. Schedule object will now correctly populate with data from both 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). and Users types of interviewers.
Quick Add Allows Saving Without Required Fields on New Application Modal
On the New Application First stage of Job placement flow (Application> Submittal>Interview>Offer> Placement) page, you can no longer save without entering information into the required fields as designated by the KanbanNewApplication Fieldset.
Save Button Unresponsive on ATS Configure Columns Modal
Clicking the Save button will now apply the appropriate changes and close out the ATS Configure Columns Modal.
TR1__Lightning_List_tab Field: Unable to Select Applicant Name
When customizing the fieldset TR1__Lightning_List_tab (Applicationv2 object), users are now able to select the Applicant A person looking for a job. A candidate can also be referred to as a Job Seeker, Applicant, or Provider. name field.
As part of changes in the 2024.10 release, the fieldset TR1__Lightning_List_tab (Applicationv2 object) was previously hardcoded and is now customizable.
Unresponsive ATS Chevron
Clicking an ATS chevron a second time now triggers the corresponding action, such as editing a SendOut A Client Submission (Sendouts, CV Sent) occurs when a recruiter sends a candidate to the hiring manager for approval to have an interview. Schedule or calling a custom action.