Recruit update - January 2021 - 2

We're slipping in another quick minor release this month (w/c 18 January) to pick off a few operational issues from the top of our backlog.

API

New classifier search API calls
Classifiers are used to drive the selection options for any vacancy and requisition fields which use fixed lists of values. They are also used for user categorisation as well as for tagging people in talent pools.

The following API calls are now available to allow classifier lists to be searched to obtain relevant IDs for classifier list items containing a relevant search term. The IDs returned may then be used in other API calls where classifier data needs to be populated.

Unlike the existing List classifiers API call which returns all classifiers and all list items, which can mean quite a lot of data is returned for some clients, these new calls will return a much smaller data set or just a single matching item if only one match is found:

• Configuration > Search classifiers - Search classifier names (as opposed to list items). Pass a search term to obtain a list of all values for any classifiers containing the search term entered and the corresponding IDs.
• Configuration > Search classifier items - Search classifier items (i.e. the values in the actual lists). Pass a search term to obtain a list of any classifier list items containing the search term entered and the corresponding IDs.

Updates to existing API calls

A minor update has been made to the way search terms are passed in the existing User and Requisition template search API calls. The search term is now passed on the query string of the API call URL. This avoids issues with certain characters, such as &, / or \ causing unexpected behaviour or errors due to their presence in the URL path.

In addition, an update has been made to the existing vacancy and requisition template API calls to correctly handle encoding and display of characters such as & in vacancy titles. As an example, the & character was previously being encoded and subsequently displayed as "&", rather than just an "&" when updated via the API.

Recruiter portal

Dashboard counts of candidates for users with read-only access to some candidate statuses
For users without full access to candidates at some statuses, the counts displayed on the various dashboards will now reflect the numbers of candidates that the user can actually see, including those in read-only access statuses. Previously these counts only included candidates at statuses which users had full access to.

Redirects added for all candidate application and top-up form pages
Following the last release which introduced a change in URL format for all form pages, our monitoring has indicated that some people do seem to bookmark specific application form or top-up form pages.

This was unexpected as candidates all need to login first to be able to access these pages, so we have now introduced redirects for all these pages as well to help ensure candidates who do have existing saved bookmarks are able to still use them as expected.

User portal

User registration email domain restriction rules no longer case-sensitive
Previously, the email domain restriction rules were case-sensitive, requiring multiple rules to be configured to cater for a single email domain, where some users may have been inclined to use a mix of upper and lower case letters. e.g. @ClientName.com, @clientname.com, @Clientname.com, etc.

The domain check is no longer case-sensitive, so this means both simpler configuration and that it is less likely users will be faced with issues when adding users or registering themselves.

Candidate portal

Improvements to copy application function when copying previous applications where a CV was not initially submitted
When copying a previous application where a candidate had indicated that they didn't have their CV to hand at the point of initial submission and where the CV was submitted later via at top-up form, the "Submit CV later" option was also being copies and therefore would be pre-checked again on the form for the new application, even though a CV existed.

The "Submit CV later" checkbox option will now never be automatically ticked when copying a previous application.

"Show until complete" top-up forms in copied applications
This is similar to the above in so far as top-up forms with "Show until complete" configuration which were completed on an original application would automatically get marked as complete in subsequent applications made by copying the original application.

This will no longer be the case, so all candidates will see and be able to amend any top-up form responses for subsequent application to different vacancies if required.

Copy previous application function on the Internal candidate portal
This function is now available on all pages of a multi-page application form in the Internal candidate portal. This now aligns with the External candidate portal. Previously for internal candidates, the option was only available on the first and last application form pages.

Agency portal

Page complete icons in the application form menu for agency applications
The "green tick" icons introduced in the form navigation menu with the new Candidate portal UX last year to indicate a successfully validated page of the application form have now been ported to the Agency portal as well.

This allows agents to more easily see which candidate application form pages are valid and ready to submit and which require more information.

Eligibility failure for agency applications on a short one-shot form
A loophole has been closed which could allow agencies to successfully submit candidates who should have failed at the Eligibility stage.

System configuration tools

Configuration overview of User portal non-Hiring Manager candidate lists
The feature summary report now includes a summary of candidate lists for each client which are used to display lists of candidates to users who are assigned roles other than the Hiring Manager. e.g. Panel members for screening and interview or Offer approvers, etc.

Improvements to initial publish of systems
An improvement has been made to ensure that newly published systems operate as expected the first time they are published. Previously, some things required a second publish to appear as expected.