| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
Table of Contents
Acendre Release Notes - Release 5.6
New Feature Summary
Recruitment Enhancements
Feature 1: Controlling Global Question Answer Updates
Feature 2: Controlling Global Question Answer Display at Form Level
Feature 3: Expandable Global Question Answer Boxes
Fixes
Acendre Recruitment
| Anchor | ||||
|---|---|---|---|---|
|
Product | Feature | Description |
Recruitment | Controlling Global Question Answer Updates | This change introduces the ability to control if new answer options added in the global question library will update everywhere (existing functionality) or only on new instances (templates). |
| Controlling Global Question Answer Display at Form Level | This feature introduces the ability to control which answer options are available against global questions at a form level. |
| Expandable Global Question Answer Boxes | This change allows the candidate or back end user the ability to expand answer option boxes when entering or reviewing text. |
| Anchor | ||||
|---|---|---|---|---|
|
Below are the listed enhancements included in the 5.6 release. These items focus on expanding the features of Global Questions and introducing greater controls.
If you require any further information regarding these new features, please reach out to your Client Success Manager who will be able to take you through these further.
| Anchor | ||||
|---|---|---|---|---|
|
Description: When new global question answer options are added in the global question library, they update on every instance that the global question has been used. These updates occur on templates, previous records and current records. For example, if there was a multiple-choice global question in the library entitled "Location" with the answer options of "Sydney", "Melbourne" and "Perth", these answer options are available for selection anywhere this global question is used. It could be used on an application form, job form and an assessment form. If there is a requirement to add an additional answer option of "Brisbane" it too would become available anywhere the global question has been used, including historical and current records.
This change introduces the ability to control if new answer options will update everywhere (existing functionality) or only on new instances (templates).
How this helps: Let's take the above example of a new location answer option of "Brisbane". The new option doesn't need to be available on current jobs or historical jobs only on new jobs. The new answer option can now be added in the global question library, but can be controlled so that it will only be available on new instances. This means that when a new job is created from the template this new answer option will be available but will not display on any historical or current records.
How to use the new option
Step Number | Description |
1 | Navigate to the global question in the global question library that requires an update. |
2 | Navigate to the Answer Options tab. |
3 | Enter the new answer option and decide if the new answer option should be available on all instances or just new instances. This decision is controlled by the Yes/No options on the question Update on new instances only? |
4 | A new parameter "Update on new instances only?" has been added to the Global Question API to allow the feature to be controlled via the existing Global Question API. |
| Anchor | ||||
|---|---|---|---|---|
|
Description: This feature introduces the ability to control which answer options are available for selection at an individual record level. In the previous example of a global question "Location" with the answer options of "Sydney", "Melbourne", "Perth" and now "Brisbane", this feature will allow control over which locations are available at an individual job level.
How this helps: In an example of two current jobs that will be available at different locations, one is at Perth or Melbourne and the other in Brisbane or Sydney. The same global question of "Location" can be used on both jobs, but the answer options that appear to candidates during application submission can be controlled i.e. one job will display Perth and Melbourne and the other will display Brisbane and Sydney, but the same global question will be used on both.
How to use the new option
Step Number | Description |
1 | Navigate to the form you would like to control the global question answer options against. |
2 | Locate the global question on the application form that needs to be updated. |
3 | Navigate to the Answer Options tab. |
4 | There is a new column Display Answer? This column indicates whether the specific answer option will display on the form. |
5 | Untick any answer options that do not need to be displayed on that specific form. |
6 | Some points to note:
|
| Anchor | ||||
|---|---|---|---|---|
|
Description: This change allows the candidate or back end user the ability to expand answer option boxes when entering or reviewing text. The user simply clicks and drags in the bottom right corner of the answer box.
How this helps: This allows for a better user experience by minimising the user's reliance on the scroll bar.
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
GSD-4908: An issue was found where users were unable to update reportable areas of global question for analytics. This was occurring even when the question was made reportable in a context previously. A code fix has been applied to allow multiple updates.
GSD-4854: Users were experiencing an issue where candidate reference documents were missing all instances of the letter 'o' causing grammatical errors. A code fix has been applied to correct this issue.
GSD-4689: The 'My Settings' menu for individual user was not editable, unless the user had permission to edit settings for all users. A fix has been applied to allow users to update their details through the 'My Settings' menu without the universal permission.
GSD-4631: In some situations, the system will direct users to 'Home' screen when they attempt to edit a newly created template. The root cause was template corruption while creation or editing. This has been resolved, and users can now create job templates and edit them without any problems.
GSD-4519: When a selection criteria question was edited as a part of job creating wizard, the edited text was changing back to the default text when a question was added to pre-application form. A fix has been applied and the edited selection criteria question will be displayed in the pre-application form without any issues.
GSD-4471: Some users were receiving Json error message when running the 'spell check' function in WYSIWYG text box, if the text contained the letters 'nz'. This has been rectified and the 'spell check' function is working as expected.
GSD-4666: While updating question answer options via global question API, intermittent slowness was reported. An update has been applied to the API configuration to resolve this issue.
GSD-4587: When a custom tertiary question is added as a display question, the system throws an error exception to the users and will causes the form to be inaccessible. A fix has been applied and the custom tertiary question in the form is now displaying correctly.
GSD-4504: The candidate portal registration function was mapped to an incorrect event, which was causing routing issues where the incorrect job was displayed on candidate's job alert profile page upon registration. The issue has been resolved and candidates are able to see correct jobs in the candidate portal.
GSD-3671: It was found that the width of input text-field was not always enough to display the whole text answers when users were previewing the forms in 'print friendly mode'. The input text-field has been increased to display the full value in the preview page when using the print friendly mode.
GSD-2630: The '&' symbol used in multi-choice global question answer was causing an issue in the talent warehouse and the search did not return relevant applicant data. The issue has been resolved and special character '&' is now supported in the talent warehouse search index.
GSD-1508: In some situations, users reported that the answer data from the group question field was not pre-populated from the correct source. This has been rectified and the data is being pre-populated from the latest requisition step as expected.
GSD-4797: When users made questions reportable, if the question was enabled with a duplicate name as another existing question, it would cause the analytics module to crash. To resolve the issue, a new feature is implemented to ensure that a non-duplicate name is used.