Recruit update - February 2022

In additional to a few fixes recent operational issues, this release includes some minor enhancements to the new user portal, based on feedback from migrated customers and a couple of key new features.

Recruit and Recruit admin

Assigning users to vacancy roles not involved in the approval process before a vacancy is approved
Previously, assigning users to vacancy roles such as panel members or interested parties was only possible once a vacancy had been approved. This meant that the user creating or publishing a vacancy was not able to allocate relevant users at those stages.

User role fields may now be added to any stage, provided the role in question does not have any responsibilities in the actual approval process. This means, for example, that the Hiring Manager can select their screening or interview panel when they are creating a vacancy for approval; or a Recruiter can assign users to these kinds of roles prior to publishing a vacancy.

Vacancy reference numbers now included in more places as standard in the new User portal
This will help users identify specific vacancies where there may be more than one with the same title. Reference numbers are now included on the vacancy details page whilst a vacancy is being approved as well as afterwards. They are also now included in the lists of archived vacancies and previous approvals.

Filter by status option now available as standard in "Other recruitment" candidate lists
This change benefits customers who have lists of candidates for users other than the Hiring Manager covering multiple candidate statuses. It is now possible to filter the lists to show candidates only at a specific status, as well as a specific vacancy.

Vacancy status displayed as standard on Vacancy details pages
The current status of a vacancy is now displayed as standard at the top of the Vacancy details page in the new User portal, in the same style as it is displayed on the main vacancy list.

Vacancy edits/status change timeline entries not showing the user who made the change 
The new version of the vacancy edit form introduced with the new User portal was not capturing the details of the user who saved for use in Vacancy timelines. This issue has been resolved and the data will be displayed in timelines for changes made after the release was deployed.

Multi-lingual fields now no longer need to be all visible at relevant vacancy approval stages
Previously, data in vacancy fields for non-English language data entry for vacancies posted in multiple languages could get lost if not displayed at a vacancy approval stage with editable data. This will now no longer be the case and alternative language data will persist, regardless of whether editable on a form or not.

Clearing previously entered data out from single and multi-line text fields
An issue in the new User portal has been resolved, which was preventing previously entered text from being cleared out from non-mandatory single or multi-line text fields.

Removal of unnecessary Close/Cancel buttons from bottom of Vacancy details page
These buttons are no longer displayed on this page, as they are no longer required.

Ensure index.html page is not cached
Some customers who had been migrated to the new User portal were experiencing unexpected issues which were caused by cached older versions of this page. This update will help to ensure this no longer happens. Note that using Ctrl+F5 to refresh the User portal may still be required initially to remove the old cached version, but once that has happened, this issue will no longer reoccur.

Update to self-service classifier management
In certain circumstances, data related to old items continued to be shown after committing a classifier change via self-service. e.g. The map displayed associated with a specific location. This issue has been resolved.

Persistence of data in forms used for panel feedback
Resolved an issue where data entered in these types of forms was not always persisting as expected.

Candidate portal

Further improvements to candidate portal Location search

Following on from the improvements made in the previous update, the system will now check a candidate's IP address to try to ascertain which country the person doing the search is currently in. If there are two locations with the same name and one of them is in the same country as where their IP address places them, we will then prioritise that one.

This won't be perfect, but we expect it to do what people expect in the vast majority of cases.

i.e. For someone on a computer or device in the UK doing a search for "Christchurch", the search term would update to "Christchurch, England, United Kingdom", whereas for someone in New Zealand, it would update to "Christchurch, Canterbury, New Zealand" after they click "Search".

Recruit configuration tools (System Builder)

VacancyGuid field no longer causes an error if selected as a field on a form page
This can be used to display the full Vacancy Guid (which is what appears in vacancy-related URLs) on form pages where required. It is also now possible to use the recently introduced HTML literal control to form links to a relevant vacancy-related page if required.

Resolved an issue where some process icons were not displaying
A few of the icon options for a single candidate process were not correctly displaying in Recruit Admin. All available icons may now be used.

Use of placeholders checking for blank/empty strings in fields on the same page
This configuration is now supported. Previously, the show/hide logic was not working on pages displayed in the new User portal in this scenario.

Vacancy title displayed in the list of fixed columns for "Other recruitment" lists
Although this column was already appearing in the published website, it was not included in the configuration views of these lists and now is.

Enable user role fields at the vacancy approval stage
User role fields are now available to be ticked at any vacancy approval stage simply by ticking the box to enable the field and the box to indicate whether data entry is required in the same way as other form fields.

Note that only roles not involved in approval may be configured in this way. A new pre-flight check has been implemented to display a warning should anyone select an invalid role to be displayed on a form other than the vacancy edit form. i.e. If the role in question is selected against any vacancy approval (requisition) stage.