Table of Contents
| Table of Contents |
|---|
...
5.14 Release Show and Tell
| Widget Connector | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Table of Contents
| Table of Contents |
|---|
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
| Feature | Description | ||||||
Recruitment | Task reminders | Configuration has been introduced to trigger a reminder email for incomplete tasks | ||||||
Bulk job archive | Multi-select jobs and archive them in one action | |||||||
Additional custom columns in jobs and requisition list | Global questions can be added as additional sortable columns in the jobs list and the requisition list | |||||||
Updates to apply to job functionality | When using the apply to job functionality a decision can be made to use application answers from the latest answered instance of the question or the answers specific to the application the candidate is being applied from | |||||||
Multi-select question and drag/drop functionality in form configuration | Questions can now be multi-selected and dragged/dropped to a new location when configuring forms | |||||||
Auto completion option on assessment form steps | Assessment form steps can now be configured to auto complete and automatically trigger step rules | |||||||
Communicate candidate step and status in the candidate portal | Clients can configure specific assessment steps and statuses to display to candidates in the candidate portal | |||||||
Pressing the enter key will log candidates into the portal | A restriction that prevented the enter key from submitting candidate login credentials in the candidate portal has been removed | |||||||
SEEK integration updates | Updates to the SEEK integration including: Allowing audience updates to open audiences only Posting job ads with a future opening date Completion of the SEEK job board configuration during job creation Expiry date logic in the manage job ads screen Refinement of SEEK job ad status during job creation | |||||||
API Send rule action update | Preventing changes to API send rule actions when the rule action has been triggered | |||||||
Performance | Prevent inactive and deleted users from showing | The Manage Review Associated Users view has been updated to remove inactive and deleted users from the default display | ||||||
Analytics | Horizontal Dashboard Filters | Add filters to your dashboard in horizontal format |
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
Description: Task emails are configured to send to either client users or candidate users to let them know that there is a form or action they need to complete. This enhancement introduces the concept of task reminder emails that can be triggered to task owners when a task remains outstanding.
How this helps: This configuration is available on requisition and assessment steps that have be configured to send task emails. It allows for automatic reminders to help prevent bottlenecks in the process.
...
Update - May 2022: Task Reminder Configuration is not currently available on tasks that use the configuration options Multiple Assessors Per Candidate or Uses Pre-Allocation.
Step Number | Description |
1 | Locate the step in either the assessment process or requisition process the task reminder needs to be configured against and open step configuration. |
2 | Click on the Permissions tab and scroll to the bottom of the screen |
3 | Ensure that the step is configured to send a task notification email and the new option Send Task Reminder Notification Email will be available   Note that reminder task email configuration will not be available if Multiple Assessors Per Candidate or Uses Pre-Allocation configuration is selected. |
4 | Click the option Send Task Reminder Notification Email and choose the reminder email to trigger. Note that the reminder email will need to be configured in the email template library first. Please use the email template type Task Notification for client user tasks or Candidate Task Notificationfor candidate tasks. |
5 | Enter the number of days you require between the original task notification email being sent and a reminder email triggering. If you would like the reminder to be triggered 5 days after the original task notification, then enter 5.   The system will accept whole numbers between 1 to 99. Note that task reminder emails are triggered at 4am on the morning of the configured day. If the process is rolled back, then the task reminder period resets and will start counting from the time date that the task is reopened. |
| Anchor | ||||
|---|---|---|---|---|
|
Description: Archiving jobs is an action that currently must be completed on an individual job by job basis. It is completed from within the job card and can be a time-consuming activity if there are multiple jobs that are ready to be archived at the same time. With this change multiple jobs can be selected and archived in the one action.
...
Step Number | Description |
1 | Select the jobs that need to be archived in the jobs list using the new tick boxes   |
2 | Select Archive Jobs from the new actions drop down menu and click Go   |
3 | The Update Job Status screen will be displayed, and any configured job archive status will be available for selection. Choose the applicable status option and select Save  Note that any jobs with open audiences will automatically be closed, which will remove the advert from the candidate portal. |
4 | The update will process and direct the user back to the Job List displaying a confirmation message at the top of the screen  Note that jobs with the status of Incomplete cannot be updated using this feature. If there is an incomplete job that needs to be updated, the creation process must first be finalised. |
| Anchor | ||||
|---|---|---|---|---|
|
Description: An additional two columns can be added to the jobs list and requisition list to enhance the information displayed. This is customised on a per user basis and is the same functionality that is already possible in the candidate list.
...
Step Number | Description |
1 | In order to add the additional columns in the jobs or requisition lists, the required global question must first be configured as an advanced search criteria. Select Show advanced search and use the Add Filter button to add the global questions required in the view. Selections from the Job details screen are available in the job list and from the first requisition step in the requisition list.  |
2 | After the questions have been selected click on the cog icon in the list and scroll to the bottom. Two custom column options will appear and can be selected  |
3 | When the tick boxes are selected, choose the applicable global question required in the list view and click Apply  |
4 | The list will refresh, and the additional columns will display with populated data, if it exists   Any additional columns added are user specific and will be retained between sessions. Note that only free text, multiple choice, Yes/No or date question types can be added as additional columns. |
| Anchor | ||||
|---|---|---|---|---|
|
Description: When using the existing apply to another job functionality from the candidate list, talent search or candidate card, the information that pre-fills into the new application is the most recent answer option across all of the candidates’ applications. There has been feedback that there is a need to be able to choose if the information prefills based on the most recent answer options or if the pre-fill is limited to the application that the apply to another job functionality was initiated from.
...
Step Number | Description |
1 | Select the candidate(s) that you would like to apply to another job and select Apply to another job |
2 | Search and locate the job you would like to apply the candidate(s) to and choose Select |
3 | The apply to job confirmation screen will display with two options Populate application form questions with the latest answers across applications (existing functionality) Populate application form questions from answers only in the apply from job Select the applicable option and click on Apply |
4 | The application form for the job the candidate is being applied to will be pre-filled based on the selection made. |
| Anchor | ||||
|---|---|---|---|---|
|
Description: Currently when reordering questions in form configuration each question must be individually selected and moved. Functionality has been introduced that will now allow multiple questions to be selected across form steps and dragged to a new location within the form.
...
Step Number | Description |
1 | Use the tick boxes to select the questions that need to be moved. They can be across multiple form steps   |
2 | Click and hold on one of the selected questions and when the mouse is moved all selected questions will be grouped together for the move. The number of questions will be represented by a red circle icon.   |
3 | Drop the questions into the new location on the form and all questions selected will insert based on their original order and deselect.   Questions that have been moved will have a yellow circle icon displayed indicating that their new location has not yet been saved. The form will need to be saved for the new location to be retained. If the screen is refreshed or navigated away, then the questions will revert to their original location. |
4 | When saved the yellow icon is removed and the question numbering is reset   |
| Anchor | ||||
|---|---|---|---|---|
|
Description: Configuration to allow for assessment form steps to be auto completed has been introduced. This will allow for configured pre-population to occur, automatic step submission and trigger any exit rules on the step without a user having to manually submit the information.
...
Step Number | Description |
1 | Open step configuration for the assessment form step candidates need to move through automatically. The new option Move candidate through this step automatically will be available.   |
2 | Select this option if you would like the candidates to move through the assessment form step automatically and not require a user to manually submit the step.  The info bubble reads:   |
3 | Select Save to confirm the configuration and a confirmation screen will display   Select Proceed to continue with the configuration or Cancel to return to the step configuration. |
4 | It is important to note that if this configuration is selected then the assessment form will be pre-populated based on global question pre-pop configuration and automatically submitted. If there are any global questions with mandatory configuration selected and they are not pre-populated, then the form will still submit, and the mandatory configuration is ignored. If the mandatory information is required for step rule actions to trigger, then the candidate may get stuck at the step and manual intervention will be required. Only use this step configuration in conjunction with global question pre-population. |
| Anchor | ||||
|---|---|---|---|---|
|
Description: The advanced candidate portal functionality introduces two enhanced features. Enhancements to the candidate landing page in the candidate portal and the ability to display step and step status to the candidate. The step and step status can be customised on an assessment template basis or at a system level.
...
Please reach out to your Client Success Manager if you would like to enable this feature and learn more about how your candidates can benefit from the enhancement.
...
to enable this feature and learn more about how your candidates can benefit from the enhancement. As part of the setup, system default statuses will be configured, but once enabled super users will have access to configure statuses at an APM step level
| Anchor | ||||
|---|---|---|---|---|
|
Step Number | Description |
1 | Locate the step in the assessment process template that the client would like to display the status to the candidate in the CP. Open the step configuration and the tab Candidate Portal Options will be available  |
2 | Tick the option Display in Candidate Task Summary List  |
3 | When selected the option to rename the step label and set custom status labels will appear.  Information configured here will override any system default configurations completed in the Advanced Candidate Portal Job Applications View for any jobs that use this assessment template.
 |
| Anchor | ||||
|---|---|---|---|---|
|
Description: The candidate will be presented with the My Applications landing page in the candidate portal that will display all their outstanding tasks, current applications, and previous applications in a consolidated view.
| Anchor | ||
|---|---|---|
|
...
|
...
|
Description: When the candidate clicks on the Job Title for their application from the My Applications view, they are directed to the Task Summary List for that application. In this view they can see any assessment steps that have been configured to display to the candidate providing they have passed through or are currently sitting on the step. Skipped steps and future steps will not display.
| Anchor | ||
|---|---|---|
|
...
|
...
|
Description: A historical restriction in the candidate portal that was preventing candidate login credentials from being submitted when the enter key was pressed has now been removed.
...
How this helps: This aligns the candidate portal with the expected functionality of the enter key triggering login credentials to be submitted and thus streamlining the process.
| Anchor | ||
|---|---|---|
|
...
|
...
|
Description: In the previous release we deployed a new SEEK integration that aligns the Recruitment product with new job posting functions provided by SEEK. In this release we re-introduce some functionality that was possible prior to the new SEEK integration and aligns this new integration with previously expected behaviour.
| Anchor | ||
|---|---|---|
|
...
|
...
|
Description: Once a job ad has been successfully posted to SEEK the job audience field on the SEEK job ad form can only be updated to an audience that is currently open. This ensures that the candidate will always be able to submit an application if the job is advertised on SEEK.
| Anchor | ||
|---|---|---|
|
...
|
...
|
Description: When posting a job ad to SEEK an audience with a future open date can now be selected. The SEEK job ad will have the status of Awaiting upload on audience open date until the audience open date is reached. Once the audience open date is reached, the SEEK job status will change to Sent to Job Board and then Job Open when it has been successfully received by SEEK.
| Anchor | ||
|---|---|---|
|
...
|
...
|
Description: The Sourcing step in the job creation wizard has been updated to display the previously removed Job Ad Configuration option. If this option is selected, then the SEEK job ad can be completed as part of the job creation process and will have the status of Awaiting upload on job completion. The job ad status will automatically update to the relevant status when job creation process is completed.
| Anchor | ||
|---|---|---|
|
...
|
...
|
Description: The manage job ads screen will now display the correct closing date for SEEK job ads. The logic is as follows:
If the close date on the linked audience is greater than 30 days from job posting date, then the closing date will display the 30 day date
If the close date on the linked audience is less than 30 days from job posting date, then the closing date will display the job audience close date
If the linked audience is set to never close then the closing date will display the 30 day date from job posting date
If the close date of the audience is updated, the original SEEK posting date will be used to determine the close date
| Anchor | ||
|---|---|---|
|
...
|
...
|
Description: When an API send rule action that has been configured on a step has triggered, the configuration on the rule action will lock. This will ensure that configuration cannot be updated after information has sent that would prevent any returned data from being successfully inserted. If the configuration needs to be amended, then the rule action needs to be deleted and reconfigured. It is recommended that this change in configuration is completed after any existing API Send data has been transmitted and returned.
...
If additional global questions need to be included on a mapping set that is configured on a form instance, then the process is to make the changes in the mapping set library, remove the mapping set from the form instance and add it back onto the form. This act of removing it and re-adding it will bring any new additions to the mapping set onto the form and the API Send rule action will remain intact.
| Anchor | ||
|---|---|---|
|
...
|
...
|
| Anchor | ||
|---|---|---|
|
...
|
...
|
Description: The Associated Users view in the Manage Review screen has now been updated so that inactive and deleted users will not display as default. Active, locked or expired users will continue to display.
How this helps: This will ensure that the user list is easy to navigate, and irrelevant information is removed from the screen.
| Anchor | ||
|---|---|---|
|
...
|
...
|
| Anchor | ||
|---|---|---|
|
...
|
...
|
...
Description: Filters can now be added to your dashboard in a new horizontal format, allowing you to place filters along the top of a dashboard above your charts and reports.
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||
|---|---|---|
|
...
|
...
|
ADR-1184: An issue was found where using the Talent Search with certain characters would cause server performance issues. This has been resolved through a code fix.
...
ADR-45: The formatting for approval form snapshot PDF files was found to be out of alignment. A code fix was applied to resolve the issue.
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||
|---|---|---|
|
...
|
...
|
ADR-666: It was identified that emails from the Perform system were not being sent to users correctly and remained stuck in the queue. A code fix has been applied to address this issue.
...
ADR-58: A formatting issue was discovered where the review information would be misaligned due to the review data conflicting with the code. A code fix has been applied to resolve the issue.
| Anchor | ||
|---|---|---|
|
...
|
...
|
Resolved an issue where using mandatory filters in reports would disable the feature of advanced broadcast recipients.
...