...
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
| Feature | Description | ||||||
Recruitment | Enhanced Application History view on Candidate Card | The Application History tab has been updated to display the Job Reference number the application was submitted against and allow the user to navigate to the job card from the history view. | ||||||
| Standardised file naming convention on document uploads | Introducing standard naming conventions for documents uploaded against jobs/requisitions and assessment forms. | ||||||
| Bulk question edit functionality on forms | Providing the ability to bulk edit questions on forms to manage configuration such as:
| ||||||
| Ability to re-order actions in rules | Allowing the user the ability to move the sequential order of actions against rules. | ||||||
| Additional configuration on candidate registration form | Giving clients the ability to choose if they capture state information on the candidate registration form. | ||||||
Analytics | Richer Dashboard s and Dashboard Management |
| ||||||
| Smarter Charts |
| ||||||
| Enhanced formatting options |
|
| Anchor | ||||
|---|---|---|---|---|
|
...
Description: The Application History tab contains a summary of all applications that the candidate has commenced or submitted throughout their history as a candidate. The Application History tab has been updated with an additional column, Job Reference Number.
How this helps: The addition of this new field within the Application History tab helps identify specific applications when Job Names are similar. The new field has also been developed as a hyperlink that will take the user directly to the job card by clicking on the Job Reference Number. This saves time and system clicks when the user needs to access information available on the job.
| Anchor | ||||
|---|---|---|---|---|
|
Description: A new file naming convention has been introduced to standardise the naming of documents uploaded during the requisition/job process, against a candidate or within and assessment form. The convention is as follows:
Jobs/Requisitions:
<original file name>
If the same file name is uploaded on the same day, then the naming convention is as follow:
<original file name><counter>
Assessment Forms either in the back end or on the candidate portal
<original file name_<yyyymmdd>
If the same file name is uploaded on the same day, then the naming convention is as follow:
<original file name><yyyymmdd><counter>
Please note: Referee documents will not be renamed with this convention but will have a counter appended if the file name is a duplicate. This is also not applicable to Resume documents uploaded into the system using the Resume global question.
| Anchor | ||||
|---|---|---|---|---|
|
Description: Editing questions that exist on a form is a time-consuming process. Each question needs to be opened individually, selections updated, and changes saved. With the success of the bulk question delete tool, we are introducing a bulk question edit tool. This tool will allow the user to select multiple questions and perform some question detail updates.
How this helps: This configuration tool will assist super users when configuring processes or updating forms. It removes the need to select individual questions and make individual updates.
How to use the new option
Step Number | Description |
1 | Navigate to the form you need to perform the update against. These can be forms within the form template library, system forms or forms on individual jobs. |
2 | Use the check boxes on the left of the form to select the questions that require an update. |
3 | Select the new option Bulk Edit Questions |
4 | The Bulk Edit Questions Details page will display, and updates can be selected. |
5 | Select Save when applicable selections have been made or Cancel to navigate back to the manage form page. |
6 | A successful message will display confirming how many questions were updated. |
| Anchor | ||||
|---|---|---|---|---|
|
Description: Actions are added to rules and are triggered in a sequential order. The sequential order was unable to be updated once the actions had been created. If the sequence of the actions needed to be amended, the actions needed to be deleted and re-created.
How this helps: Adding the ability to re-order actions against a rule post creation allows the user to update the sequence without having to delete and re-create the actions.
How to use this new option
Arrows will appear on the rules created within assessment or requisition processes when two or more actions exist. Users simply click on the arrow up/down on the action that needs to be re-ordered.
| Anchor | ||||
|---|---|---|---|---|
|
Description: The system form Candidate Registration and My Details Form allows users to customise the registration form that candidates complete via the candidate portal when registering. Information collected on this form is a combination of system questions, which are required to create a candidate card, and custom questions that the client chooses to add. One of the system questions that was unable to be customised was the State with Other question. This question forced the candidate to select their state or choose other if they were located external to Australia.
The form configuration has been updated to allow users to remove this question from the registration form.
How this helps: This will allow clients the ability to remove the question completely or replace the question with an alternative.
Please note: If this question is removed from the registration form it will not be able to be re-added. It will need to be replaced with new global questions configured in the global question library.
| Anchor | ||||
|---|---|---|---|---|
|
Description: The new Acendre Analytics module (using the new Data Warehouse) will have a significant upgrade to its user interface and functionality.
How this helps: This will allow new and better dashboard designs, easier creation of dashboards and charts, cleaner and smarter chart stylings, and an enhanced appearance.
Please note: This update only applies to Acendre Analytics and will not be applied to the Analytics Classic module.
| Anchor | ||||
|---|---|---|---|---|
|
New dashboard layout – dashboard now appear in a re-styled menu bar
...
...
View dashboards in Fullscreen mode – expand a dashboard to view in full screen so that you can see even more chart and report details. (Use the ESC key to return to normal screen.)
Broadcast dashboards in PDF – send an entire dashboard tab to users or external recipients via the existing broadcast functionality. This allows new ways of sharing content and multiple related reports.
Better dashboard management – easily organise and reorder your dashboards.
New dashboard builder and tools – a wide range of new capabilities have been added to dashboard building, outlined below.
Free-form dashboard canvas - you are no longer locked into single, double or triple column layouts |
 |
Chart blueprints – use blueprints to create a new chart on your dashboard by selecting your desired chart type and specifying the view/fields to be used |
  |
Filter display - display specified filters on the dashboard canvas, either globally or on (and applied to) a specific subtab. |
  |
Automatically link filters between reports on a dashboard |
 | |
Configurable action buttons – add action buttons that can reset filters, link to a specific URL, navigate to a dashboard subtab and more. |  |
 | |
Add dashboard filter bookmarks and make them your default filter value(s). |  |
Use a report multiple times on a dashboard, and choose between live results, snapshots, bookmarks and/or a specific chart. |
 |
Undo, Redo, Preview and More – undo or redo changes when on a canvas subtab, and additional preview, refresh, rollback and version delete options before you publish |
 |
| Anchor | ||||
|---|---|---|---|---|
|
Smart chart defaults – charts built using the blueprint functionality on dashboard canvases will have optimal styling automatically applied |
 |
Smart chart logic will show or hide various chart elements based on the available space, like legend details, axis granularity and labels. |
 |
Enhanced colour scheme setup – new default chart colours to enhance readability and understanding |
 |
| Anchor | ||||
|---|---|---|---|---|
|
New default colours and fonts – new defaults to make reports and dashboard presentation even cleaner and easier to understand. |
 |
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
...
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
AU-261: An issue was identified where the system would create multiple job alert profiles against a single candidate. This would cause issues when trying to deactivate the profiles. A code fix has been applied that fixes this for job alert profiles going forward.
AU-260: When using the Candidate CSV Import function, the process would fail if the target step had the setting Uses Pre-Allocation enabled. This has been addressed with a code fix without affecting the Pre-Allocation function.
AU-259: It was found that the candidate quick search function was not considering job owner access. This would affect job owners and prevent them from being able to find candidates within those jobs if no direct permissions were assigned to them. A code fix has been applied to rectify this issue.
AU-258: An issue was found were approval steps would not open when withdrawing candidates from the assessment process. This issue has been resolved through a code fix.
AU-256: The Communication Log within the candidate card was found to be displaying the incorrect user and not the user who sent the email. This has been addressed with a code fix to display the correct user.
| Anchor | ||||
|---|---|---|---|---|
|
AU-257: An issue was found where Acendre Analytics was not updating when assessment data was received into the system from external providers. A code fix has been applied to ensure this updates correctly.
| Anchor | ||||
|---|---|---|---|---|
|
AU-544: The User API has been updated to use the region default time zone when creating user records. Previously this was a hard coded value but will now be reflective of the configured system default value.