Advorto release notes - 4.5.24
Candidate-based Marketplace integrations
This release includes an update to the system to allow Marketplace integrations to work on a Candidate level. Previously, data coming back from integrations was being stored at a "Person" level, i.e. applicable to all applications a person may make, so they were only able to do any particular assessment once.
Although this makes sense for some assessment types, e.g. psychometric tests, where this allows clients to avoid having to send the same candidate to the same test for applications to different roles, in other assessments this is less useful.
For example, in video interviews, it is common to have different video interviews for different roles. Similarly, with regards to Referencing, references are specific to the role the candidate is applying for.
The updates now allow integrations to be configured to be Candidate-based or Person-based as required to support both scenarios.
With regards to video interviews, note that even when configured on the Advorto side, some third party providers may not support the same candidate being sent to the same interview for different roles, particularly where they are using the candidate's email address as the unique identifier. Please consult with your providers and set different interviews on different vacancies if necessary.
Close assessment to new candidates or decommission
In order to support clients changing from person-based to candidate-based assessment configuration, some other new functionality has been introduced in this release.
- Assessments may now be closed to new applicants where required. This function allows candidates who have already been invited to an old assessment to complete the required activity, whilst new candidates may be invited to a new assessment
- Assessments may now be decommissioned when required. This functionality may also be used when switching assessment providers, allowing all data associated with the old provider to continue to be visible.
Allow vacancy user role data to be used in Marketplace integrations
As user role may now be selected on Marketplace integrations to allow the name and email address of the user assigned to that role to be transferred to Marketplace. One key use of this function is to allow, for example, a Hiring Manager to be notified when something happens, e.g. when a Referee submits a reference response.
Allow Test, Staging and Live to connect to different Marketplace instances
This change allows test data and live data to be kept entirely separate where required. This allows changes to third party integrations or to Marketplace to be fully tested without impacting live configuration, as Test and/or Staging may be connected to a Test instance of Marketplace, which may in turn be connected to test versions of third party systems.
New standard user identity report
All systems now include a standard user identity report, listing all users and all identity fields. As identity fields are used in comms from the system, this will support Super Users checking user configuration to ensure that identities for all users who require them are present and consistent in style.
The new report is available in Custom reports (Reports > Custom reports for users who have access to this feature in their security group).