Skip to main content

Version 9.1.190 (13 October 2025)

Dashboards

Ripple effect when selecting an image for a banner (#137261)

Problem

  • There is a ripple effect when selecting an image for the banner.

 

Solution

  • Removed ripple effect when selecting an image for the banner.

 

People Management

Disability dropdown not showing (#137946)

Problem

  • There are 2 different disability toggles and lists in which are shown under the tab content of Summary as well as Profile, in which it does not toggle the visibility correctly accordingly to the view selected

 

Solution

  • Add a change to find the parent row container and the correct list ID to toggle the visibility

 

Data Warehouse

Adjustments that need to be made within LearningManagementReport (#137761)

Problem

  • Adjustments are required within lmTermResults and lmStudentSubjects for Student Reports 

 

Solution

  • Resolved calculation issue for Scores within StudentSubjects due to rounding that already occurs within the first calculation 
  • Added Step to update Score fields to blank for cases when Students only have 0 marks for a whole term within StudentSubjects
  • Reduced the manual updates within StudentSubjects
  • Updated the Promotion Status Calculation for Grade 7 - 12 to resolve issues where it had not been calculated correctly within TermResults
  • Reduced the manual updates within TermResults

 

Training Matrix - Refresh (#137719)

Problem

  • The @ReferenceDate has been commented out for lmEmployeeTrainingRequirementsMatrix which can cause performance issues

 

Solution

  • Added @ReferenceDate within the source script for EmployeeTrainingRequirementsMatrix to improve DWH performance

 

Imports

Improvements to the user imports performance and implementation of batch processing (#131379; #135967; #136136)

Problem

  • The performance when importing more than 6K users is abysmal
  • When staging user import directly in the DB the pre-import validation is skipped.
  • When importing positions without codes, a new position is created with every import.
  • When an import is busy processing it is impossible to track the progress
  • When updating the user's details on the profile, the payroll id is cleared, causing the username not to update when synced again from Payspace
  • When the username, ID number or employee code's case differs from the existing DB case, the usernames are not updated and a new user is created.
  • When importing user data the update delays the import
  • When importing the org structure with many changes, the import takes an excessive time 

 

Solution

  • When data is staged directly in the DB, validate the data before starting the import
  • Ensure that the payroll ID is not cleared when a user's profile is edited on the front end.
  • Allow updating username using the payroll ID, ensure matching on username, ID number, and employee code is case insensitive when updating usernames.
  • Ensure the payroll ID is always imported for new and existing users
  • Implement bulk processing for the org structure, job profile and positions
  • Improve matching of existing job profiles when importing job profiles and positions
  • Remove the userdates update and replace it with a streamlined update for performance
  • When importing a position without a code and title, ensure the position is mapped to the current position of the user, rather than creating a new position with every import
  • Add import logs in the service to keep track of running processes
  • Implement batch processing per service of 5K users per run
  • Add detail exception logging when importing org nodes
  • Remove concurrency stamp when creating users

 

 

Back to top