Acendre Release Notes July 2021 -- Version 5.13
- Larrisa Wright (Deactivated)
Table of Contents
- 1 Table of Contents
- 1.1 New Feature Summary
- 1.2 Recruitment Enhancements
- 1.2.1 Feature 1: Assessment API
- 1.2.2 Feature 2: Candidate Resume Parsing
- 1.2.3 Feature 3: Inserting a new requisition or assessment step into a determined location
- 1.2.3.1 Requisition Workflow
- 1.2.3.2 Assessment Workflow
- 1.2.3.3 New Assessment Workflow
- 1.2.4 Feature 4: New task list filter option
- 1.2.4.1 Filter in Tasks Tab
- 1.2.4.2 Set up Default Task List Filter
- 1.2.5 Feature 5: Enhanced packaging functions to include note attachments
- 1.2.5.1 PDF Packaging
- 1.2.5.2 Standard Packaging
- 1.2.6 Feature 7: Security Enhancement
- 1.3 Fixes
- 1.3.1 Acendre Recruitment
- 1.3.2 Acendre Performance
- 1.3.3 Acendre Analytics
New Feature Summary
Feature | Description | |
Recruitment | Assessment API | New method of exporting candidate data to a third party for processing and receiving returned data directly into assessment forms |
Candidate Resume Parsing | Ability for candidate to upload a resume and have the system extract mapped data elements to pre-fill an application form | |
Inserting a new requisition/assessment step into a determined location | Allows a user the ability to choose where in an existing requisition or assessment workflow a new step should be inserted | |
| Updates to available task list views | Introduction of a new task list filter option to include both “In Progress” and “Not Started” tasks |
| Enhanced packaging activities to include note attachments | Packaging functions will now include note attachments when notes are selected |
| Security Enhancements | Restriction of the use of embedded content |
Recruitment Enhancements
Description: The assessment API consists of two main components:
sending candidate assessment data to third party systems for services such as:
External testing
Background checking
Medicals
Security clearance
Credential validation
Video interview providers
External reference checking providers
receiving processed candidate assessment data back from the third party system, if applicable
Processed candidate assessment data received back from the third party system can be:
Inserted into a current in progress candidate assessment step
A concurrent in progress candidate assessment step or,
A future not started candidate assessment step
How this helps: If you are utilizing third party providers during the assessment process and manually entering information into the provider system and then entering outcomes into Acendre Recruit, then the assessment API can assist with automation of these activities.
The assessment API can also trigger APM actions when data is received from a third party system, including:
Moving a candidate through an assessment step
Adding candidate flags and updating application status, and
Triggering email
The below diagram illustrates the flow of information between the two systems, Acendre Recruitment and your third party provider.
If you would like more information about how the Assessment API can assist you and your team through the candidate assessment process, please reach out to your Client Success Manager.
Description: Candidate resume parsing allows a candidate the ability to upload their latest resume during a job application process and the system will extract specific fields from their resume to pre-populate questions within the application form.
Resume parsing will be introduced in multiple phases, with the first phase being parsing of candidate personal data, such as names, address information, education history, work experience and referee information.
How this helps: This will assist candidates submitting applications and ensure that their personal information is updated based on their latest resume.
It will decrease the time taken to complete applications with the prefilling of core personal information.
Available fields: The below fields are available for mapping as part of our first phase candidate resume parsing feature.
Question | Answer Options | |
Given Name | Free Text | |
Middle Name | Free Text | |
Family Name | Free Text | |
Preferred Given Name | Free Text | |
Date of Birth | Free Text | |
Address | Free Text | |
Suburb | Free Text | |
State | Free Text Note that most customers use a defined list global question that candidate select a state option from. Unless the state information matches the answer options of the global question exactly, the information will not parse. For example, if the candidate lists the state “Victoria” in their address on their resume, but the state global question used by the client has the defined list answer option of “VIC” the information will not parse. Note this limitation is only applicable during phase 1 of the resume parsing project. | |
Post Code | Free Text | |
Mobile Phone | Free Text | |
Home Phone | Free Text | |
Education History x 3 | Institution | Free Text |
Year Obtained | Free Text | |
Work History x 5 | Position Title | Free Text |
Employer Name | Free Text | |
Date Commenced | Free Text | |
Date Finished | Free Text | |
Position Duties | Free Text | |
Referee Information x 2 | Referee First Name | Free Text |
Referee Last Name | Free Text | |
Referee Position Title | Free Text | |
Referee Organisation | Free Text | |
Referee Location | Free Text | |
Referee Contact Number | Free Text | |
Referee Mobile Number | Free Text | |
Referee Email Address | Free Text | |
Resume Parsing – Candidate Experience
Below are the steps the candidate will take when parsing their resume.
Step Number | Description |
1 | When a candidate has logged into the candidate portal and has chosen to begin an application, they will be presented with the resume parsing functionality automatically  |
2 | Candidates can choose: Skip – to skip the parsing step and proceed to the application for manual population Select file – to browse and upload a resume document Note that if the candidate chooses to skip this step their application will be pre-filled as per existing functionality populating the application form with the most recent response to the question. |
3 | When the document is uploaded the candidate will see the name of the document and the successfully uploaded message |
4 | The resume parsing tool will accept most document types. If the candidate attempts to upload an unsupported document type, they will be presented with one of the following messages:
|
5 | If the candidate needs to remove and replace the selected document, they can use the trashcan symbol to delete the document and either upload a replacement or select skip to continue without parsing. |
6 | When the candidate has uploaded the correct resume and selects continue, they will be presented with the processing page |
7 | After the document has been processed the candidate will be directed to the pre-application form or a pre-filled application form. The uploaded resume document will pre-fill into the application form as the candidate’s resume. |
If you would like more information on how candidate resume parsing can be added to you candidate portal, please reach out to your Client Success Manager.
Description: Currently when there is a requirement to insert a new workflow step into either a requisition or assessment process the new step will insert at the bottom of the existing process. The result of this was lengthy time spent moving the step to the appropriate position in the workflow and potentially breaking existing rules/actions within the workflow. This enhancement introduces the ability to choose the location of the new step rather than automatically inserting at the bottom.
How this helps: With the ability to choose the location of new workflow steps users no longer have to spend time moving the steps from the bottom of the workflow or recreating delete form data rules that were previously removed. This will reduce the administration/configuration time associated with existing workflow maintenance.
Requisition Workflow
Step Number | Description |
1 | Navigate to the requisition workflow or requisition template workflow that requires new steps added. |
2 | Each existing step will have a new button entitled Add Step. When this is selected, the user will need to choose if the new step is to insert above or below the current step.
|
3 | When the location is selected, the user will be directed to the manage step screen and additional step configuration can be completed. The new step will be inserted into the location previously selected. |
Assessment Workflow
Step Number | Description |
1 | Navigate to the assessment workflow or assessment template workflow that requires new steps added. |
2 | Each step will have a new button entitled Add Step. When this is selected, the user will need to choose the type of step to insert and if the new step is to insert above or below the current step.
|
3 | When the step type and location is selected, the user will be directed to the manage step screen and additional step configuration can be completed. The new step will be inserted into the location previously selected. |
New Assessment Workflow
Step Number | Description |
1 | When a new assessment process workflow is created, steps are now added by using a new option Create Step. When this option is selected, the user will need to choose the type of step to be created and will then be directed to the manage step screen for additional configuration. |
2 | When the first step in a new workflow has been created the Create Step button will be removed and the user will select the Add Step button on the newly created step.
|
Description: A new task list filter option has been added to the list of available filters. The filter is “Current” and will contain all In Progress and Not Started tasks for the user.
The filter can be set as default for individual users or user groups by a system super user/administrator.
How this helps: This enhancement provides a new and relevant filter option that allows a user to view all their current tasks rather than having to switch between multiple filter views.
Filter in Tasks Tab
Set up Default Task List Filter
Description: Current packaging functionality allows for notes to be packaged but does not include note attachments. This enhancement will now automatically package any note attachments when the option to packages notes is selected.
How this helps: This will now allow user the ability to fully package all relevant note information, including attachments.
PDF Packaging
When using the PDF packaging option, all note attachments will be available within the PDF document after the instance of the note.
Standard Packaging
When using the standard packaging option, all notes will be allocated a note ID and this will be represented with the attachments. This allows the user to identify which attachments are relevant to which note.
Note that notes and attachments added to a candidate on a global level will not package with either packaging option. This is existing functionality.
Description: A new security enhancement has been added to Acendre Recruitment to ensure that our high security standards are maintained.
Restriction of embedded content: A change has been implemented that will remove the ability to create new embedded content within form fields or within jobs on the candidate portal. The enhancement will not impact existing content but will strip this content if the question is amended by a backend user on the form or job. If you would like this functionality retained, then do not edit the question within the form configuration.
Users will no longer be able to create new global questions using embedded content. The additional security will strip the content from the question.
The functionality is currently used to embed YouTube URLs. We will be enhancing the Acendre Recruitment product in the future to ensure that YouTube links can be added to job and question content in a safe and secure manner.
Fixes
AU-1407: An issue was found where a ‘File Upload’ type global question could be saved with an incorrect data type forcing an exception error. This has been resolved through a code fix.
AU-1329: It was found that users logging in through Single Sign On were being affected by the password expiry date set in Recruit causing them to be logged out. A code fix has been applied to rectify the issue.
AU-1303: An issue was identified where job alert emails for New Zealand customers were linking to candidate portals with an Australian domain rather than a New Zealand domain. This has been addressed with an update to use the correct links.
AU-1217: When setting up a SEEK ad, there was an issue preventing the ‘Salary Range’ field from being configurable. A code fix has been applied to correct this issue.
AU-1092: It was found that certain emails triggered by APM movements were not being recorded properly in the ‘Candidate Communication Log’. A fix has been applied to address this issue.
AU-1085: An issue was identified where jobs that were set to ‘never close’ would incorrectly display close dates on the Dashboard. This has been rectified to display the closing dates correctly.
AU-954: An access issue was identified where users who created jobs from requisitions with a ‘Talent Search’ type step would not be able to view the newly created job. This has been addressed through a code fix.
AU-824: When deleting a child question from a ‘Group’ question, after a candidate had provided a response, an error would display. A code fix has been applied to no longer generate this error.
AU-526: An issue was identified where archived jobs were still displaying tasks in the candidate portal if the jobs were coming from a legacy onboarding integration. This has been rectified through a code fix.
AU-349: Previously when a new search criteria was created, a server restart was required to add this to the ‘Talent Search Criteria’. A fix has been applied to correct this issue.
AU-1028: An issue was found where accessing the ‘Managed Reviews’ tab could cause the system to error if there were numerous reviews to load. A code fix has been applied to rectify this issue.
AU-796: It was found that the system was displaying a review incorrectly on the User Interface when there was a conflict between the content and the interface designs. A fix has been applied to correct this issue.
AU-790: There was an issue where the system would not send emails, resulting in these remaining in ‘Queued’ status. This has been addressed through an architectural update of the server process.
AU-75: A restriction in the code was found that was cutting off some of the content from the default screen view in Acendre Analytics. This view has been increased and all content is now visible.
