Version 9.1.144.1 (Support Release - 13 February 2025)

Translations 
 Themes translation not showing on Login (#126618) 
 Problem 
 
 The translations on the login page are not working 
 
 
 Solution 
 
 Ensure the translations pull through to the login page 
 
 
 
 Ruleset Management 
 Able to log into a deactivated ruleset (#126304) 
 Problem 
 
 The user could not log in immediately after a ruleset was activated / User could log in after a ruleset was de-activated. 
 
 
 Solution 
 
 Bust the cache when activating/deactivating the ruleset 
 
 
 
 People Management 
 Error when a user tries to reset their password (#126175) 
 Problem 
 
 When the user tries to reset their password the attempt fails because the call is checking whether the user has the People Admin role. This should not be done when the user is resetting their password. 
 
 
 Solution 
 
 Changed the ResetPassword call to check whether the user has the People Admin role or is the user whose password is being reset and then allowed the action. 
 Also, change the message displayed when the user reset their password from "A notification has been sent to the Person to reset their password." to "A notification has been sent to you to reset your password." 
 
 
 
 Master Data 
 Navigating to the requirements tab displays an error (#127019) 
 Problem 
 
 
 Barched queries failed due to too many of the same foreign keys 
 
 
   
 
 Solution 
 
 
 Updated query to use DapperExtension to reduce the number of parameters and remove batch query functionality 
 
 
 
 
   
 Load indicator shown indefinitely when clicking on person's profile (#127605) 
 
 Problem 
 
 
 DapperInBatched was misused in the translation query, causing an invalid SQL query to be generated. 
 
 
 
 Solution 
 
 
 Ensure that DapperInBatched is used correctly for the query. 
 
 
 
 
 
 Notifications 
 The user who registers does not receive their email (#126173) 
 Problem 
 When a new user registers on the system using the Identity auto registration functionality: 
 
 The default appointment record did not get created leading to the user being seen as inactive due to not having an appointment. 
 The email confirmation email did not get sent out and the user could never continue with the registration 
 
 
 Solution 
 
 Ensure that when registering the default appointment gets created. 
 Resolve the issue where the confirmation email was not getting sent out after the user registers.