Acendre Release Notes July 2018 -- Version 5.0

Bugs

Acendre Recruitment

1. GSD-1981: We have identified an issue with formatting email templates while using the space character, and identified the root cause. We have fixed the issue.
2. GSD-1941: We have received feedback from a customer that our "Print Friendly" mode sometimes only printed the form without the data. We have located the issue and the problem has been resolved.
3. GSD-2077: We have received feedback from a customer that when deleting a requisition template, the process would fail. We have identified the root cause based on the inherited permissions and have fixed the issue.
4. GSD-2220: We have identified a formatting issue with the Candidate Portal on the formatting of menu lists. This issue has been identified and resolved.
5. GSD-2298: We have received feedback from a customer that our Candidate Portal job search functionality wasn't returning errors when the search criteria didn't find any jobs. The issue has been found and fixed.
6. GSD-2381: We have identified an issue with task notification not firing off emails from the system. We have identified the root cause and have fixed the issue.

Acendre API

1. GSD-2299: We have identified an issue with our user/position API subscription where adding an addition employee to an existing position that has an employee already assigned. The root cause has been identified and fixed.

Acendre Performance

1. GSD-1978: We have received feedback from a customer while trying to delete an employee’s review. After investigation, the team found that under some circumstances, the date data can become null, thus not allowing the application to delete the review. The team identified the issue and added additional criteria to prevent this from happening in the future.
2. GSD-2111: We have enhanced the functionality around loading "Managed Reviews" based on feedback from a client. We have streamlined the process when loading more than 100 employee reviews in a single process.
3. GSD-2214: We received feedback from a customer that when creating a review from a review template, an error message could arise if the original template had a notification with a trigger associated with it. We have identified the root cause and fixed the issue.