Recruit update - March 2020

This release incorporates our latest security updates and addresses a number of support issues and minor product suggestions raised recently by clients. The update will be rolled-out to all clients starting 23 March 2020.

In other news, our Candidate portal UX release is nearing completion. This will bring a whole raft of improvements to the candidate experience for all clients, so look out for announcements soon.

User portal/Backoffice

Enhancements to delegation functionality
Enhancements have been made to the user delegation functionality to prevent circular delegation.

Column sort order settings in global and personal views
When editing a global view via self-service, the default sort order configured for a particular view column was not being correctly committed. This issue has been resolved, so users may now set a default sort order if required. In addition, a separate issue has been resolved related to personal views, allowing any column to be configured with a default sort order for these as well.

Unexpected behaviour with identity property field data
In certain circumstances, the data entered in fields configured for user identities was switching fields on saving users. The cause of this issue has been identified and resolved.

Update references to "Kallidus" in forgotten password emails
Forgotten password emails will now be sent from a Kallidus email address and refer to "Kallidus" or "Kallidus Recruit".

Support added for agency emails about candidate interviews to be sent to the candidate
Previously, emails about interviews were still only being sent to the submitting agent, even when the "Send to agency candidate" option was selected on the email template. Where this option is selected, email templates of this type will now be sent to the actual candidate, CCing the agent (provided a system is configured to capture candidate email addresses for agency candidates and an agent has provided this).

Performance enhancement related to contact details search
This area of the system was identified as not performing as expected and so has been optimised.

New data retention option of 18 months
A new standard data retention setting of 18 months has been added to support clients who require this.

Improvements to validation of merge fields in comms
Some typos in certain merge fields were not being picked up by the validation mechanism. These fields will now be picked up when saving or sending comms templates and so may be corrected.

Only user role identity fields for roles used on vacancies available for views
Previously, all user role identity fields were available for Vacancy or Candidate views, even when a role was not actually enabled as a vacancy field. If selected, such a field would cause the view to error, so now only fields associated with roles used on the vacancy form will be available.

Improvements to validation on Word merge pop-up
Where a user didn't select an existing template and didn't upload a file, the missing Word merge doc file was not being validated as being required. A file upload will now be required and appropriate validation messages will be displayed if not.

Update to counts displayed when filtering for red or amber KPIs
Where KPIs are configured to be status-specific, the counts of red or amber items at each status was only being displayed correctly if that specific status was selected or if "All" was selected. This could make it not obvious where the red or amber items were if you had a different status selected. When a KPI filter is applied, the counts displayed will now continue to display the numbers of red or amber items, regardless of which status is selected.

Completed interview slots no longer display availability in the slot list
Interview slots which previously had a candidate allocated and where that candidate has completed the relevant interview will now correctly show in lists of slots as having no availability and will not allow new candidates to be allocated to them if all spaces have been filled.

Interview slots not appearing in date order if ordered by the Slot start date field
Although the Slot.Start (date+time field) was ordering as expected, the Slot start date and Slot end date (date only fields without times) were ordering numerically, rather than by date. These date fields will now also order as expected if used.

User portal showing interviewers assigned to slots across multiple interview series
Where the Interviewer(s) column is used in the User portal, e.g. in the Interviews candidates list for a Hiring Manager, the data shown in the "Interviewer(s)" column was also including interviewers from previous earlier interview series that a candidate had been allocated to, rather than showing interviewer(s) for the current series only. This issue has been resolved, so users will now only see the interviewer(s) assigned to the candidate's latest/current interview.

Security enhancements to comms sending mechanism
A security update has been made to the comms sending pages to improve the security of access to candidate data displayed on comms sending pop-up pages.

Ordering of data selections for multi-select list fields in read-only mode
Where multiple values are selected for a list field used on a requisition or vacancy form and where that field is displayed in a read-only mode on a form page, the order that the selections appear in will now be the same as the order that they appear in for the editable version of the field.

Marketplace

Improvements to management/logging of Marketplace exceptions
A scenario was identified which could result in Marketplace integrations not logging an error under certain circumstances. This could result in some transactions not sending updated data to Recruit as the failure was not being picked up by our monitoring. Improvements have been made which are expected to resolve this issue, so failures of data transactions with third party systems may be quickly resolved.

System Builder

Adding vacancies after first publish of a system
An issue has been resolved related to a system needing to be published twice before a vacancy could be added. Vacancies may now be added after the first publish.