Version 9.1.230 (25 May 2026)
Imports
Resolve the incorrect import of org level 9. Correct import of reporting lines and company dates after materialisation migration (#149114)
Problem
Org level 9 name and code imported in the incorrect order. The Reporting line import fails due to a mapping issue with the record in the Dapper query. StartDateInCompany cannot be imported due to missing aliases. The job profile import starts before the user materialisation completes, then appointments, reporting lines, and company dates are only partially imported.
Solution
Reorder OrgLevel9Name/OrgLevel9Code across models, DTOs and gRPC mapping so field positions are consistent (UserDetails, BasicUserDetailsData, PaySpace export, ImportManagementService). Fix a tuple return in UserDetails to return OrgLevel1Name instead of OrgLevel1Code. Correct SQL in UserQueries: reference ud and muser aliases explicitly, use the proper JOIN for UserCompanyDates, and fix KnownAs column alias formatting. Also, remove a stray blank line. These changes ensure correct mapping of org/job fields and correct user date update logic. Add a short delay before starting the job profile import
Data Warehouse
Updated insert step for PAYU tables (#142732)
Problem
New SchemaIDs need to be added for the Insert step for PAYU tables
The step needs to be adjusted to execute the original SP within the DWH staging insert step
Solution
Added new SchemaIDs for the insert step for PAYU tables
Updated the insert staging step to execute the original SP to ensure consistency
People Management
Improved performance on Company tab query (#149132)
Problem
When selecting the Company tab, and there are a lot of employees, it can take a very long time
Solution
Optimised and improved query
Master Data
Disable the Evaluation Master Data scheduled import. Improve handling on Bulk Import handler for evaluation master data (#148480)
Problem
Errors occur on the Bulk Evaluation Master Data Handler. Currently, this runs for ALL rulesets, even those that do not utilise PM or that have invalid or inaccessible api endpoints.
Solution
Since this Master Data is only used during specific periods, we don't need to fetch it daily. Will now only trigger when requested ad hoc from the front end. Disabled the schedule on all rulesets for EvaluationMasterData import (import type 13). Improved handling of the bulk evaluation master data handler. Note that technically this will no longer be called since the schedule is disabled, but still added improvements in case the schedule is re-enabled from the front end.
Adjusted user registration flow email confirmation (#148426)
Problem
Business rule flow is missing. Once a user submits a user request and the ruleset has confirmed registrations, a user request is logged where the manager can go to accept or reject this. The flow missed a part where it first needs to send a confirmation email to the newly created registration to confirm the email address, then only submit for the manager to accept or reject the request. There was a restriction that an email confirmation code could only be generated from an identity profile that was created
Solution
Implemented new properties to indicate which part of creation it needs to do with CreateUser in Identity and within Account. Once a user registers, it sends a new email template with the email confirmation link. Once the user has confirmed the link, only then are the original templates triggered to the manager and user for submission. The manager can only then accept or reject the request; it will see the dependency that awaits email confirmation. Once accepted, the account user is created; if rejected, the identity user is then deleted