Acendre Release Notes March 2018 -- Version 4.5

Owned by Larrisa Wright (Deactivated)
Last updated: Sept 23, 2019
2 min read

Bugs

Acendre Performance


1. GSD-581: We received feedback from a customer that when creating a review from an already created template, some of the email recipients’ values are not past through. We have identified the root cause and have implemented a fix so this won't happen again.
2. GSD-1472: We had a report from a customer that when trying to save a performance diary entry, the system would throw an error message. The development team tracked down the issue behind the scenes and has implemented a permanent fix so this won’t happen again.
3. GSD-1504: We received feedback from a customer that sometimes in the Position List view, the display would retrieve all records, including commenced, resigned, ceased and pending records. This caused issues in the individual user position record view. The issue has been identified and resolved.

Acendre Recruitment


1. GSD-688: We had a report that in some requisition forms, the formatting from design and in production view did not align bullet points. The formatting issue was identified and resolved.
2. GSD-1623: We received feedback from a customer that when duplicating a job ad with Seek, the template data wasn’t always copied over. The development team tracked down the issue behind the scenes and implemented a permanent fix so this won’t happen again.
3. GSD-1649: We received feedback from a customer that when rolling someone back within the APM process and having the “send email notifications” option unselected, the process would fire off emails. We identified the issue and have created a permanent fix so this won’t happen again.
4. GSD-1679: We found an issue with the Candidate Portal, whereby creating a “Return/Line Break” didn’t always work with all controls. After investigation, we found the root cause of the problem and resolved it with a small code fix.
5. GSD-1685: We received feedback from a customer that in some cases, when a manual decision step within the APM was made unsuccessfully, the system could send out two notifications. The development team investigated this issue, found the underlying issue and implemented a fix for the problem.