Skip to main content

Version 9.1.177.4 (Support Release - 21 August 2025)

People Management

People Management: Admin Access to Profile Fields (#135626)

Problem

  • The Assets heading on people management does not update when the user changes the text on the frontend.

Solution

  • There was no translation added, and the text "ASSETS" was hardcoded.
  • Simply added the existing matching translation

Identity and Authorisation

Login Report - Not recording reset password login data (#135574)

Problem

  • The following pages did not record login successes or failures:
    • Confirm Account Creation
    • Continue Registration
    • Disclaimer: When logging in, the disclaimer is required
    • External Login: When logging in with a non-existent user with the 3rd
    • party login
    • Login with Recovery Code
    • Registration
    • Reset Password

Solution

  • Added the missing logging functionality in the backend

Imports

Import Error (#135543)

Problem

  • The import error email is not always send to the administrators when Payspace Pull, Payspace Push, Powershell Pull or the Bulk import to V8 fails.
  • When the acctual import after the payrol connector import fails then not email is sent 
  • When Code and Name of a org is supplied as empty strings the preimport validation rejects the import incorrectly with the error Org node with code - contains no Org Name;
  • When the Bulk import between V8 and V9 fails then no email is send to the people administrators to be aware of

Solution

  • Change the import to send to the people with the people admin role when 'n backend import for the import types UserDetailsImport, CustomPowershellScriptImport, PaySpacePullImport, PaySpacePushImport, BulkAdditionalServiceImport
  • When a user does the import from the front end only, they will receive the error
  • Change prevalidation on org to only require the name when the org code is provided
  • Auto-unlock a failed backend bulk V8 import after a period of 2 hours

People Groups

Employee appointment/termination error (#134571)

Problem

  • When a signed-in user terminates a user or adds a new user, the cache/roles are cleared and re-materialised, thus causing authentication issues, which throws a we're sorry screen

Solution

  • Extend the duration attempt to wait as well as increase the retry count to 2 times,

System Access

Employee appointment/termination error (#134571)

Problem

  • Once a user has been added/terminated, the Redis cache is cleared, and a new call is made to materialise data as well as repopulate the user roles for the signed-in user.
  • Thus, after adding or terminating the user, the call is made to the Respective service to fetch the needed data, which requires the role of the user who is signed in, and because the roles are busy populating again, the error is thrown, which is caused by a 401 - Unauthorised

Solution

  • Implement a check within the /Edit path view, which the signed-in user is redirected to after they have added or terminated the user, to wait for half a second, should the error of unauthenticated state be received and try once more.

Imports

Bulk Additional Service Import Failed (#135542)

Problem

  • When the bulk additional service import is triggered, it included the appointment history, which is currently not finished implemented in the v8 side. This then causes the import to fail, even if all the others succeeded

Solution

  • Remove the appointment history from the additional service import to not execute for now

Back to top