# Version 9.1.144.2 (Support Release - 14 February 2025)

#### **Translations**

##### Themes translation not showing on Login (#126618)

**Problem**

- Translation is not pulling through to the login page

**Solution**

- Implement the translations on the login page

---

#### **Ruleset Management**

##### Able to log into a deactivated ruleset (#126304)

**Problem**

- 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

---

#### **Master Data**

##### Seeded data not appearing in drop downs on Employee Profile (#126916)

**Problem**

- Location, country and province master data are not displayed in the "Address" section due to conflicting component names which also appear in the "Summary" section.

**Solution**

- Give unique names to the component elements, ensuring that the master data correctly displays on both "Address" and "Summary" sections

##### Job Profiler: Navigating to the requirements tab displays an error (#127019)

<div id="bkmrk-problem-3">**Problem**</div><div id="bkmrk-barched-queries-fail">- Barched queries failed due to too many of the same foreign keys

</div><div id="bkmrk-%C2%A0-5"> </div><div id="bkmrk-solution-3">**Solution**</div><div id="bkmrk-updated-query-to-use">- Updated query to use DapperExtension to reduce the number of parameters and remove batch query functionality

</div><div id="bkmrk--2"></div><div id="bkmrk--3"></div>##### Load indicator shown indefinitely when clicking on person's profile (#127605)

<div id="bkmrk--4"></div><div id="bkmrk-problem-dapperinbatc"><div>**Problem**</div><div>- DapperInBatched was used incorrectly in the translation query, causing an invalid SQL query to be generated.

</div><div>  
**Solution**</div><div>- Ensure that DapperInBatched is used correctly for the query.

</div></div><div id="bkmrk--5"></div>---

#### **People Management**

<div id="bkmrk--7"></div>##### Error when the 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 resets 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."

---

#### **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:

1. The default appointment record did not get created leading to the user being seen as inactive due to not having an appointment.
2. 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.

##### Email sent when new ruleset is created contains Reset OTP placeholder instead of actual OTP (#128113)

<div id="bkmrk-problem-6">**Problem**</div><div id="bkmrk-user-authentication-">- User authentication and user forgot password used the incorrect placeholder's name for "ResetOTP"

</div><div id="bkmrk--9"></div><div id="bkmrk-solution-6">**Solution**</div><div id="bkmrk-ensure-that-those-ev">- Ensure that those events use the correct placeholder's name.

</div><div id="bkmrk--10"></div><div id="bkmrk--11"></div>---

#### **Performance Management**

<div id="bkmrk--13"></div>##### Unable to Link Scorecards to Users (#127841)

<div id="bkmrk--14"></div><div id="bkmrk-the-following-change"><div>The following changes were made to the bulk create and delete pages to allow it to work for small and large datasets</div>- The dropdown that searches on a user has been replaced with a list textarea where you can paste a list of usernames to search for. The load of all users to filter appropriately here was too much, and there was not enough time to implement proper async loading in the dropdown.
- The load all option will only load the first 1000 records that match your search criteria, the browser cannot handle the load of any more data than that without hanging
- The people groups filter is now applied using the materialised people group data
- When load all is done only the last part of the org path is displayed e.g. ...Parent Node Name | Position Node Name
- The existing performance contract filter was removed as it caused performance issues as how the data is loaded from different contexts

</div>**Problem**

- When loading large people groups the select lists fail to load, the search does not work, the job grade and job profiles do not include all the options

**Solution**

- Add a new list search and replace select 2
- Implement and refactor appointment and performance queries to user-materialised people group users
- Change load all to be limited to 1000 records
- Remove the filter on existing performance contracts

---