Recruit update - September 2021

Whilst the roll-out of all the work we've been doing over the last year on the new User portal continues and customers are gradually being migrated over, we've found time for a few other updates to address various minor product suggestions as well as completion of our new Indeed integration roadmap item.

Recruiter portal

New integration with Indeed / Glassdoor
A number of improvements have been made to our Indeed/Glassdoor integration. This will replace the current integrations which work via the Recruit Marketplace and will be available to existing customers once they have been migrated to the new User portal. The changes include:

• New simplified Indeed configuration page (for Kallidus consultant use), including new settings and mappings for company key contact email, Education, Experience and Remote type
• Support for either all vacancies or specific vacancies being sent to Indeed, using "Indeed" as an option in the existing "Publish to" field on the vacancy form, rather than requiring a separate step via Marketplace after publishing a vacancy
• Ability to use multiple company names/brands in Indeed within a single Recruit instance
• All location field metadata now mapped to all the relevant Indeed location-related fields (previously, only country and city were mapped, which could result in some incorrect locations displayed in Indeed). N.B. This depends on relevant full addresses/geocodes being added and generated for any relevant locations a customer selects on their vacancies.
• New feed aggregator - one feed to Indeed from Kallidus for all vacancies for all customers - this means that new customers will no longer need to deal with Indeed directly or to request that Indeed accept a new XML feed
• For more information on the Indeed's XML specification, requirements and how it works, click the link below:
  https://developer.indeed.com/docs/indeed-apply/enterprise-ats/

Improvement to vacancy transfer audit to help identify specific vacancies
Previously, when a candidate was transferred from one vacancy to another, the candidate's timeline would only display the vacancy title of the vacancy the candidate was transferred to the new vacancy from.

For customers who have multiple vacancies with the same job title, this didn't give enough information about the original vacancy.

The vacancy title in candidate timelines has therefore now been changed to a link, so users can click through to the vacancy timeline page of the relevant original specific vacancy.

Current vacancy status now displayed on vacancy timeline pages
The current status of a vacancy is now visible in the top left of the vacancy timeline, above the opening and closing dates.

Improvement to validation when reassigning requisitions
The reassign requisition (to a different approver) feature now validates that a user is selected.

Restricted candidate actions no longer shown on candidate timeline pages when folder security is enabled
Addressed an issue for customers with folder security enabled This feature allows customers to restrict access to some actions (e.g. Next steps, Screening, etc.) for candidates who are at specific statuses in the candidate workflow.

Although the restricted actions were not visible in candidate lists, they were visible and available if a user was able to navigate to the timeline page for a particular candidate. Restricted actions are now also hidden on the timeline, based on the candidate's current status.

Improve messaging for users who are trying to add a new user who already exists
Previously a generic "Something's gone wrong" message was being displayed to users if they tried to add a new user who already existed. Users will now be informed that a user already exists with the same email or login. N.B. The existing user may be deleted, so it may be necessary to check the Deleted user list and use the "Reactivate user" feature to re-enable them.

Slot gap text box on Add interview slot(s) page now wider
The data entered in the boxes indicating the gap between interview slots was being slightly cut off for two-digit numbers. This issue has been resolved.

New User portal

Resolved an issue with the display of data in vacancy fields with conditional display logic
Some vacancy data was not visible for approvers during the approval process where a field had conditional display logic configured. This has been resolved.

Resolved an issue with the display of additional language vacancy text fields
Under certain circumstances, additional language vacancy text fields for certain languages were being displayed by default, before any additional languages were selected on the vacancy form. These fields are now only displayed once the relevant language is selected.

Addressed an issue with type ahead fields saving item IDs, rather than the text value
The text value of a user's selection is now correctly saved and will be used as the data displayed in data views, reports and comms mergefields, etc.

User identity fields no longer mandatory
Following user feedback, the new user portal add/edit page has been aligned with the existing user portal, where identity fields such as email signature and user telephone number were not mandatory.

Use of file upload fields in Views
Fields related to file uploads may now be used as a column in candidate views - this will display the file name of the file uploaded, which will also be a download link which users may use to download the relevant file directly. Previously, if such a field was added to a View, the view would error until the file upload field was removed again.

Recruit admin (System Builder)

Conversion of former Vacancy Heading, Sub-heading and Text controls to HTML controls with markdown
The new "HTML" control should now be used for any text content on vacancies. This replaces the former controls for Headings, Sub-headings, Text and any HTML such as info text panels. The HTML option should also no longer be used and will be removed in future. Any HTML-type content should now be entered using markdown. See the link below for supported markdown syntax:

https://www.markdownguide.org/basic-syntax/

Vacancy form help text
HTML should also no longer be used in any control help text on the Vacancy form. Instead, use markdown syntax, as per the link above.

Vacancy form HTML control now supports conditional show/hide logic, as per other vacancy form fields
This may now be used when headings or text are only required to be displayed based on data selected for other fields on the vacancy form.

New merge field for the User portal URL
{!System.UserPortalUrl} may now be used in configuration wherever a link to the user portal is required on any pages or in user comms templates. This field is now also displayed on the list of all system merge fields available from the Publish page in System Builder.

Candidate status folder labels now included on workflow configuration page (as well as names)
This makes it easier to spot issues and to compare the workflow configuration with what users actually see.

Systems no longer lock just when visiting the new user portal config section
Previously, a system would lock and block user config self-service even when just viewing configuration. This issue has been resolved.

Candidate status folders with workflow actions configured may now be safely deleted
Deleting a candidate status folder from configuration would previously cause problems on the workflow configuration page in System Builder. This is now no longer the case.

"Default value" configuration removed from Single line text controls
This was populated with "Not applicable" for all single line text controls and wasn't a feature that was ever implemented for this control type, so has now been removed to simplify things.

Improvements to scoring calculations related to panel feedback
Scoring controls which are required to sum, average or calculate a percentage across all panel members who have scored a candidate now only require a single field to be selected. Previously, a field needed to be entered for each individual panel member "row".

In addition, scoring calculations now work in the new user portal as hidden fields on the actual panel feedback form. This means that a calculated score may be immediately displayed anywhere on the system as soon as a panel member submits. Previously, the calculation would have taken place when loading a different page, e.g. at the point where a Hiring Manager is required to make the final decision.