Version 9.1.177.5 (Support Release - 25 August 2025)
People Management
People Group list times out (#135875)
Problem
- The people group user list times out after 60s
Solution
- Removal of the CTE (Common Table Expression) and restructuring the query to use a single SELECT statement, which improves readability and potentially performance. Additionally, the query now includes organisation path information directly and sets a longer command timeout for large queries.
Identity and Authorisation
Learningstore redirect gives an error when logging into V10 (#135006)
Problem
- When signing in via the learning store, the we're sorry screen appears. This is caused by the redirect code, which expires in one month
after creation.
Solution
- Added logic to ensure it only expires after 10 years. Also added migrations to update existing redirect codes
Login Report - Not recording reset password login data (#135574)
Problem
- No new login logs are viewable on the report builder
Solution
- Fixed backend User reference
Imports
Import Error (#135543)
Problem
- When a schedule processes the Payspace or PowerShell scripts, the data cannot be staged due to Cannot insert a staging record without a valid OwnerUserId
Solution
- Eliminated the check for a valid OwnerUserId in the UserImportStaging constructor and updated related unit tests. Also added ProcessPayroll job configuration to appsettings.Development.json.
Payspace changes to correct the appointment dates (#134132)
Issue 1
Problem
- Start Date in the company is not mapped from Payspace
Solution
- Map the employment date from the employee status API as the Start Date In Company for import
Issue 2
Problem
- Start Date in the company is not mapped from Payspace
Solution
- Map the employment date from the employee status API as the Start Date In Company for import
Learning Management
LMS Portal: Subject Setup: No Cycle 'Weight in Period' Validation (#132285)
Problem
- The weights in a cycle can exceed 100
Solution
- Prevent users from assigning more than 100 total weight to interventions in a cycle, improving data integrity and user experience.
Tenant Management
Tenant Creation | Not receiving initial email and user not authenticated (#135653)
Issue 1
Problem
- A check is being done if the tenant setup has been completed before a notification for rulesetup is sent out, but an attempt is made to send the notification of the ruleset out before the last command for tenant is called
Solution
- Correct the order to first finish last tenant setup command and then proceed with the notification with the ruleset
Issue 2
Problem
- When a new tenant is created, it creates a support user and a few others as well. This makes use of the bulk user import functionality, as this now requires an import ID which failed to create users
Solution
- Parse the import ID to create the new users to proceed with the tenant setup