Coming Soon!!
New Feature Summary
Product | Feature | Description |
Recruitment | Addition of Candidate ID number in default Assessment API package | The default package sent with an Assessment API has been updated to include the candidate ID |
| Clean up of unused configuration options | The following unused configuration options have been removed:
|
Seek job ad posting fixes and enhancements | The following fixes and enhancements have been introduced with this release:
|
Recruitment Enhancements
Feature 1: Addition of Candidate ID number in default Assessment API package
Description: The default package that is automatically send when an Assessment API export is triggered has been updated to include the unique candidate ID number. The package now includes the following data:
FormDataExportId
SubscriptionName
MappingSetName
ObjectKey
ObjectId
CandidateID
MappedData
How this helps: This will now automatically include a unique reference that can be consumed by the third party integrating with the assessment process.
Feature 2: Clean up of unused configuration options
Description: In an effort to ensure the system displays relevant and useful configuration options to users, a number of unused configuration options have been removed:
IP Range Filters
Candidate password complexity options mandating how many complex options are required. Note this does not impact the ability to mandate that complex options are required, but removes the unused functionality mandating exactly how many characters need to be input
Option to display closed jobs on the candidate portal
Feature 3: Seek job ad posting fixes and enhancements
Description: We have introduced some fixes and minor enhancements to the Seek job ad posting process and new Seek job ad form:
The delete/expire button logic has been updated so that the correct message displays depending on the status of the job ad. Jobs that have not yet been posted to Seek will only display the delete button. When a job has been posted to Seek, the user will see the expire button
Any job card that is deleted and has a job ad on Seek will now automatically have the Seek job ad expired
Posting a job ad to Seek with a future opening date has been enhanced and will now display the correct status in the manage job ad screen
If the Seek job ad is configured during the job creation wizard, then the Seek job ad status will display as Awaiting Upload on Job Completion
If the job audience is open when the Seek job ad form is completed, then the Seek job ad status will update to Awaiting Next Upload
If the job audience is set to a future opening date when the Seek job ad form is completed, then the Seek job ad status will update to Awaiting Upload on Open Date
Any merge fields used in the job highlights or job overview field on the job details form will merge through populated to the Seek job ad form.
Fixes
Acendre Recruitment
ADR-1330: If a job card that has a pending or existing Seek job ad posted against it was deleted the linked Seek job ad wasn't expired. This has been fixed and now when a job card is deleted any linked Seek job ads will also expire and pending Seek job ads will not post.
ADR-1345: An issue was identified where candidates were not able to submit onboarding forms due to some data not being created. A code fix was applied to resolve the issue.
ADR-1334: It was discovered that a missing configuration in the database was preventing candidates from receiving task email notification reminders. This has been resolved through a code fix.
ADR-1288: The assessment process matrix was found to have an issue where the current number of candidates displayed incorrectly for concurrent steps. A code fix has been applied to ensure the number of candidates will display correctly
ADR-1201: A branding issue was discovered where various elements of the candidate portal displayed incorrectly. This has been resolved through a code fix.
ADR-1146: When using advance filters on the candidate list, including multi-select type, question filters would cause the system to return duplicate listings of candidates. A code fix has been applied to ensure no duplicates will appear.
ADR-1093: It was found that job alerts were being automatically deactivated through external systems. A new page has been developed to request for manual confirmation before deactivating job alerts.
ADR-763: An issue was identified where job owners would not be able to see candidate notes unless they had a direct permission for the job. A code fix has been applied to ensure that job owners are able to view candidate notes without the direct permission.
ADR-414: It was discovered that the 'Edit Job Template' function permission was not working correctly. A code fix has been applied to resolve the issue.
ADR-1351: Candidate task emails were not firing when they followed an auto submitted step. This has been fixed and task emails will trigger as expected.
Acendre Performance
ADR-1205: An issue was found where the close dates of review phases were not displaying correctly. A code fix has been applied to rectify the issue.
ADR-1177: It was found that editing a caption on both Recruitment and then the Performance system would cause the system to be inaccessible. A code fix has been applied to address this issue.
Acendre Analytics
ADR-895: Global questions that were deleted from Recruitment were found to not be completely removed from the reporting database. This issue has been resolved through a code fix.
ADR-527: It was discovered that SMS messages sent to candidates were not being recorded by the Analytics database. A code fix has been applied to rectify the issue.
