Welcome to the July update for Recruit. This release will be rolled-out to all clients during the weeks commencing 12 August and 19 August. It includes a number of new features and enhancements that clients have requested recently. A brand new integration with Xref is also now available which may be implemented to save clients time and money with their referencing process.
A new standard integration with leading online reference checking provider, Xref (https://xref.com/en/uk/) is now available. Clients who wish to automate the process of collecting references for candidates may now set up an account with Xref, decide what criteria and referencing forms you require, then once ready, just request via Kallidus Support that the integration be turned on to link your Xref account to Kallidus.
In terms of how it works, it's a button click on an appropriate "Referencing" pop-up page, which registers the candidate with Xref. Xref will then automatically email the candidate to request their references and chase up the candidate and their referees, request replacement references, etc. until the required number and type of references and/or time period is covered.
This means that Recruiters or Hiring Managers can just sit back and relax and wait for the full Reference report to come in and users can view this and the status of the candidate in Xref from within the Kallidus system.
Costs for use of Xref depend on the volume of checks and the number of "Credits" purchased - one credit = one candidate (regardless of how many references required). Please contact Xref to request further information, mentioning that you were referred by Kallidus.
Column filters in full screen data grid mode
The column filter functionality in data grids in Advanced view now also operates as expected when viewing in full screen mode.
New feature to enforce selection of at least one vacancy when adding slots for self-scheduling
Previously, it was possible for users to inadvertently add interview slots intended to be assigned to a particular vacancy without actually allocating the slots to any vacancies. This results in slots being visible to candidates in all vacancies configured to use self-scheduling, rather than only the vacancy(s) for which they were intended.
This new feature, if enabled on an interview series, will set the Vacancies field on the Add slot form to be a required field. This will therefore prevent slots from being inadvertently created which are not assigned to at least one vacancy.
Slots now automatically assigned to the vacancy a candidate is in when scheduling manually
When scheduling candidates manually via the Interview scheduling pop-up page, the interview slot created was not assigned to any vacancies. This could be a problem in systems where candidates may be removed from their original slot for any reason, as the slot would then become available for candidates in all vacancies to select.
This new feature will ensure that any slots created via manual scheduling will only ever be available for the relevant vacancy, even if a candidate is removed.
Performance enhancements to self-service classifier and list editing in multi-lingual systems
A performance issue has been resolved which was resulting in occasional time-outs when editing classifier or application form list items via self-service.
Performance enhancements to time-based reports
The standard time-based candidate reports were causing time-outs on some systems. An enhancement has been introduced to improve performance of these.
Contacts list page update
An issue has been resolved where the Contacts page was causing an error in systems with Global contacts.
Users with an Approver role no longer able to approve their own requisitions when routed to a different user
Previously, users who routed a requisition for approval to a different named user could still approve requisitions at the next stage if they also had been assigned the user role responsible for the next stage of approval. Following this release, only the named user a requisition is sent to will be able to approve it.
Multiple clicks now ignored on Vacancy and Requisition form save and action buttons
Multiple clicks on some buttons could result in multiple vacancies or requisitions being inadvertently created. All buttons will now ignore all clicks other than the first one to avoid this from happening.
Styling of action links in the Styled theme
Previously, in systems configured to use the Styled theme, any User portal tables with more than one action link displayed the last link on the right in a different style to the other links - as a button, rather than a link. This behaviour has been updated, so that all links display in the same way. This means that these links will now all either be displayed as links or buttons, depending on any custom styling added.
Updated source tracking mechanism
Previously, the source tracking mechanism captured and stored a person's original source only, not the source of each individual application. We now capture the Landing and Referrer URL for a person's original application (stored against the Person) as well as the source of each individual application (stored against the Candidate/Application).
As before, the updated mechanism takes account of the fact that a candidate may navigate away from the initial Vacancy Details landing page to browse other pages not hosted by Kallidus, before returning to apply. i.e. We are still able to capture and store the original actual Referrer and Landing URLs, even though the Referrer and Landing URLs may end up being different for the eventual application.
Google Tag Manager
This has now been implemented as standard on the Candidate portal to allow Kallidus to analyse usage data to identify potential issues and areas for further UX improvement. In addition, the tracking code has been moved to the recommended place, so clients using their own Google Tag Manager implementations should find that the Google Tag Manager events now fire more reliably.
Deprecation of Marketplace emails
All emails related to Marketplace integrations may be configured within Kallidus Recruit or, where relevant, a third party system. Previously, Marketplace itself was also set up to send some emails related to events triggered within Marketplace and these could not be disabled. Feedback from users suggested that all the emails from Marketplace itself were not useful, so these have now been disabled.
Old products with a large amount of data may now be edited and saved more quickly.
New setting on Interview series to enforce vacancy selection on slots
A new "Require Vacancy Selection" checkbox is available in interview series configuration (Backoffice > Structures > Interview series) to enforce the selection of at least one vacancy when users add new slots. This feature should be enabled unless a client works in a way such that any slots added need to be available for any vacancy.
New "Leftie" theme
A new standard theme has been added to support client careers site designs which require the main navigation to be on the left side of the screen, rather than the top. Clients with this kind of design no longer require a custom theme.
Removal of full custom themes and old Advorto Basic theme
In preparation for the migration to Microsoft Azure and forthcoming updates to the Candidate portal and User portal UX, the option to configure entirely custom themes is being deprecated, along with the Advorto Basic theme, which was not widely used. All clients have been migrated to a standard themes so all clients will be able to take advantage of the forthcoming and any future UX improvements.
Note that full custom CSS may still be applied to one of the existing themes, which adequately supports the design requirements for nearly all clients. The XML vacancy feed or API options are then available for clients who require the vacancy search, list and details pages to be entirely within their own brand on their own website.
Deprecation of Refer
In preparation for the migration to Azure, Refer has also been deprecated to simplify things, as no clients use this service.
New Source tracking section in System Pages
Related to the forthcoming migration to Azure, Campaign module has also been deprecated and replaced with a new source tracking mechanism that will exist for all clients as standard. The Campaign module configuration section has therefore been deprecated and replaced with a new "Source tracking" section, with an option to turn on cookieless tracking should that be required.
Tracking without the new cookie mechanism will not be as accurate as the new cookie-based mechanism, but will still provide some data.
The Landing URL, Referrer URL and Logged date/time fields have been moved to being standard system fields, so no longer require sub-items to be set up. All Campaign module data for existing clients will be migrated to the new standard fields as part of the upgrade.
New options to configure a process to run when a Marketplace instrument records a ready or updated event
When configuring a Marketplace instrument, a process may be assigned to be automatically run when an assessment is ready, e.g. once a third party assessment provider returns a link to us to allow a candidate to take an online test or video interview.
Similarly, a process may be configured to run whenever an "Updated" event is received, e.g. whenever a third party sends us new or updated data for a candidate.
Assign process to instrument button
A process may now be assigned to an instrument button. This means that as well as registering a candidate with a particular third party via Marketplace, if the registration is successful, a process may also be triggered, e.g. to progress the candidate on to a relevant different status.
No longer compulsory to select folders for a Marketplace instrument
It is now no longer a requirement to select folders for a Marketplace instrument. Previously if no folders were selected, the call to action in the Candidate portal would be visible to all candidates at all statuses. Now, if no folders are selected, the call to action will not be displayed to candidates at any status.
Update to front end literal control
A new configuration option is available in the front end literal control for displaying tabular data, where the table of data is stored in JSON format in a single field. Tick the new "Is JSON Table" checkbox where this is the case and the data will be displayed in a table format with the appropriate headings, rather than has a raw string of JSON.
This feature should be used, for example, in an Xref configuration to show a table of all the candidate's referees and the status of each reference.
Marketplace instrument result documents now available to add to PDF actions and printable views
Where, third party providers who return a document as part of the data returned to Kallidus, the document may now be configured as a standalone PDF action and/or combined with other PDFs. Marketplace-related documents will now just appear in the list of selectable documents as per other documents and may be selected as required.