Bugs
Acendre Recruitment
1. GSD-1535: A customer report indicated that when a candidates session expired, there was an issue delivering activity booking confirmation emails. The root cause has been resolved with a small software fix.
2. GSD-1603: The Acendre team found an issue with the Advanced Candidate Portal, where the job step and status were displayed for old jobs that were marked not to be displayed. The root cause of the problem has been identified and resolved.
3. GSD-1695: We received feedback from a customer that in unique cases, the online reference module would have a mismatched status around the reference received status field. The issue was identified and fixed.
4. GSD-1698: We had a report of an issue with job highlights and new audience types in jobs, whereby the highlights were not shown in the Candidate Portal. The root cause was identified and resolved with a small software fix.
5. GSD-1722: The team at Acendre found an issue when two dynamic prompt questions were placed on the same form, the second question stopped working. The issue was identified and fixed.
6. GSD-1734: We had a report of an issue with the “ApplicationEdited” field displaying incorrect values, The issue was identified and fixed
7. GSD-1783: We received feedback from a customer that when actioning a task email via an SSO environment, the system forced existing sessions to log out and cause problems if the URL encryption feature was enabled. The root cause was identified and resolved with a small software fix.
8. GSD-1937: We received feedback from a customer that one of the captions in the requisition module wasn't working as expected. The cause of the problem was located and fixed.
Acendre API Platform
1. GSD-1606: A client informed us that our API suite was not always transmitting the Transactionid field or details. The issue was investigated and resolved.
2. GSD-1762: We were informed by a client that our Position API subscription had issues when trying to disable a position. The root cause was identified and resolved with a small software fix.
3. GSD-1821: We had a report of the UserPosition subscription not making the Start Date mandatory, resulting in incorrect position reporting. The issue was located and fixed.
4. GSD-1822: We have been informed by a client that our Org Unit API had an issue with updating the isActive field. We located the root caise of the problem and resolved it in this release.
5. GSD-1823: We have updated our documentation to include the isDeleted field as being “readonly.” This applies to the Position, Organisation Structure and Position User API endpoints.