# Version 9.1.210.2 (Support Release - 19 February 2026)

#### **Learning Management**

##### Adjust dropdown sizes and exclude start and end date from year dropdown (#144958)

**Problem**

- The Year dropdown has regressed into the Date Range of the Master dataitem rather than the associated label, and the size has been adjusted and is no longer legible.

**Solution**

- Adjust dropdown sizes and exclude start and end dates from the year dropdown.

---

#### **Performance Management**

##### Resolve issue with the additional agreement button displaying when the user does not have a primary agreement (#140461)

**Problem**

- Add an additional agreement button that shows when impersonating a user and the user does not yet have a primary contact, and the user is only on a single review setup.

**Solution**

- Ensure the additional agreement button is correctly hidden when the user does not yet have a primary contract.

---

#### **People Management**

##### Add handling to not do PG update with rowlock when no data to update (#144529)

**Problem**

- Situation where if current activity on materialised PeopleGroupUsers, but there is no data in the table for the PG, then the rowlock causes performance issues.

**Solution**

- Wrapped the table update with the row lock in an if to only run if there is data to update.

##### Refactor People Management tab queries to increase performance (#144529)

**Problem**

- In some instances, the queries to fetch MyTeam / MyDepartment / MyCompany / PeopleGroupUsers time out or take an excessive amount of time to complete.
- Investigated and found a couple of areas that could be done better, one of which relates to the appointments
- 2 calls are made as subqueries to determine 1) the number of subordinates for the user, 2) whether the user is my manager.
- These are extremely inefficient, however, as for every row in the resultset the count is done from reporting lines / checked against my Line Manager.

**Solution**

- Changed the 'My Manager' check by fetching the user's manager beforehand into a variable and then comparing the result userid against that variable.
- Moved the subordinate count outside of the main cte query by first selecting everything into a temp table and then calculating and updating the subordinate count after the fact as a batch update.
- Some minor changes to React for mapped key uniqueness.

---