Acendre Release Notes January 2018 -- Version 4.4

Acendre Recruitment

Value Based Assessment : Cognitive

We are extending our current value based assessment capability and including cognitive assessment to the offering. Our current value based assessment offering consists of:

  1. Personality assessment
  2. Attitude assessment
  3. Personality and Attitude assessment

In Jan release a new assessment - 'Cognitive assessment' will be added to the value based assessment set.

Value based assessment can be used during the hiring process in order to undertake behavioral testing and 'place the right people in the right roles and improve quality of hire.'

This feature will not be automatically available. To inquire further about the new feature please contact your customer success manager.

Security : Notification of account changes

Acendre constantly works to improve the security profile of our products.

The Notification of Account Changes feature has been designed to inform users of any changes to their profile. 

The type of changes that are tracked by this feature are:

  • Account status
  • Username or password changes
  • Changes to user details and or user permissions.

Initially this feature will not be turned on, to have this activated please contact your customer success manager.

API : Application snapshot

Acendre is consistently working to enhance our API offering.

In Jan release a new API will be released - GET candidate application data based on application ID. 

The API is a GET call, it uses Acendre Application ID as a URL Fragment (example /application/ {ID} and returns the most recent snapshot of data along with file attachments, if any.

If your organization wants to view application related data in a third-party application like dashboards this is the API which you can leverage to achieve the desired outcome.

To leverage the API please contact your customer success manager.

API : GET file API

In Jan release we are introducing a new API that sends document for consumption in an external system based upon specific parameters.

The API can be used in a number of ways, for instance

  • On-Boarding Documents : To retrieve on-boarding documents like personal information form, bank details, superannuation forms,education information, certifications etc in external payroll and HRS systems.
  • Get attachment like resumes to be displayed in external systems.

To leverage the API please contact your customer success manager.

API : Search for application identifier

We are introducing a new API for application search. With this API you can use various fields from an application to search and find that application. 

This API can be used to display application related data in external systems.

To leverage the API please contact your customer success manager.

Acendre Performance

Security : Disable inactive accounts

Acendre is introducing new functionality called “Disable Inactive accounts”, that will enable the system to automatically disable user accounts after a predetermined configured time.  This new feature is fully configurable and allows organisations to customise it to meet their security requirements.  The feature has the following configuration parameters:

  • Turn “on/off” of the feature
  • Set the number of days that a user account is inactive to qualify to be made disabled.
  • Reminder emails to employees to update their account information

Initially this feature will not be turned on, to have this activated please contact your customer success manager.

Security : Notification of account changes

The Notification of Account Changes feature has been designed to inform users of any changes to their profile.  The type of changes that are tracked by this feature are:

  • Account status
  • Username or password changes
  • Changes to user details and or user permissions.

Initially this feature will not be turned on, to have this activated please contact your customer success manager.

Performance Benchmark

In Jan release we are introducing a new feature - 'Benchmark'. Benchmarks are performance standards for each rating to be set/updated for each goal within a users' review. These are guidelines for each rating and can be configured to match the guidelines of your organization. For example, for a measure of 1 to 5, benchmark will provide guidelines to managers at review level to rate each employee per goal.

To configure benchmarks,

  • Goto Measure → Edit a Measure.
  • Set the 'Use Benchmarks' field as shown.

    

  • The Benchmark section would appear in the rating sections one use benchmark is set.

  • You can update the benchmark text as per your requirements.
  • The benchmarks once set can be accessed via a link on the goals in reviews.

  • Organisation level benchmarks can also be overwritten at review level by selecting the setting called 'Allow Override Performance Benchmark'.
    • This is useful when you want to have different guidelines for organisation goals and different for team and individual.

For further queries on Benchmarks please contact you customer success manager.


Bugs

Acendre Performance

  1. GSD-613: We have refined our emailing functionality to ensure the formatting of the emails are correct and no additional language characters appear within the email to give a better user experience.
  2. GSD-985: We received feedback from a customer when saving Goals the system would display an error message and not save the input.  Initially a workaround was found and in this release the permanent fix has been applied.

Acendre Recruitment

  1. GSD-129: We were inform the WYSIWYG editor within the recruitment product wasn't always adding up the number of characters correctly, we have modified the counting algorithm to be more accurate.
  2. GSD-195: Within some of our Dynamic Questions the validation rule and saving to the database routine conflicted, thus not delivering the desired outcome.  We have improved the process behind the scene to streamline and fix any issues that may arise in the process.
  3. GSD-290: When packaging up candidates we found an issue where by forms changed order and they would change every-time you did any packaging, the issue was identified and we have included the sorting algorithm to the code to fix this issue.
  4. GSD-582: We have received feedback from a customer, if you have two concurrent step in an assessment process with email notifications the system may send out two email at the same time, we have identified the root cause and have implemented a fix so this wont happen again.
  5. GSD-744: We have received feedback in some cases emails from the online reference module wont be sent if the referees email address has been changed during the recruitment process via the Application form, we have identified the root cause and have fix the problem
  6. GSD-959: We have received feedback from a customer where candidates are moved to a to a complete status within the APM when the rule states that it should move candidates to a not started step, we have identified the issue and implement the fix in this release.
  7. GSD-955: We have enhanced our validation processes around mobile phone numbers, to alert of any unnecessary characters or spaces, this will ensure additional services like sms's are formatted and action as desired.
  8. GSD-1184: We have received feedback from a customer that the was an issue with the GQ import functionality that resulted in an import error, the issue has been resolved to allow Answer Display formatting of characters lengths of 50 characters.
  9. GSD-1281: We have received feedback from a customer that there was an issue in deleting candidate information via the Delete Candidate User Utility whereby it would throw an exception error, the problem was identified and we have implemented a fix to this release.
  10. GSD-1310: We have refined the check box functionality to be more user friendly in the Manage User module
  11. GSD-1339: We had a report from a customer that candidates were receiving multiple emails for a single job applications, after investigate we found the root cause of the problem and have resolved it with a small code fix.
  12. GSD-1346: We have received feedback from a customer that when completing a "Question Use Box" the results weren't been saved and changing to another value, we have investigate the issue and have found the source of the problem.
  13. GSD-1375: We had a report from a customer that reference details become inactive when candidate applies for another job with same referee details, we have identified the root cause and have implemented a fix so this wont happen again.
  14. GSD-1450: We have received feedback from a customer that some jobs posted to the Seek service were not been removed once the job was closed, the issue has been identified and resolved.

Acendre API Platform

  1. GSD-1188: We have identified an issue with the position feed API when deactivating a position and the system returns a successful return message but in the user interface the position is still active.  We have identified the root cause and have fixed the issue.
  2. GSD-1189: We have identified an issue with the core API configuration module with updating keys and getting them resync'ed, we have identified the issue and implement the fix in this release.
  3. GSD-1248: We have found an issue within our User API module where the validation rules needed to be modified to verify the correct user was update when duplicate users existed.  We have identified the root cause with the validation and have fixed the issue.
  4. GSD-1260: When applying employee permission changes via the API and leaving the UserProfile field null, the returning message returned a 400 error message. We have identified the root cause with the validation and have fixed the issue.
  5. GSD-1306: We have found an issue with our Performance Diary API module where it had issues deleting diary entries that had been created by the API itself.  We have identified the root cause and have fixed the issue.
  6. GSD-1396: We have identified an issue with the position feed API where the system was converting a string type field to a numeric number, we have identified the issue and implement the fix in this release.
  7. GSD-1400: We have received feedback from a customer that when updating a employee position via the API module, the system wasn't allowing changes to employees that had been deleted or inactive, We have identified the root cause and have fixed the issue.