# Version 9.1.194 (4 November 2025)

#### **Organisational Structure**

##### When viewing the linked positions, and you click on “ALL”, it only seems to show filled positions (#137435)

**Problem**

- Org was not clickable to view positions linked to org after the styling changes

**Solution**

- Ensure that the org level is still clickable so that the positions for that org level can be viewed

---

#### **Translations**

##### Translation not mapped to the message indicating password requirements (#139039)

**Problem**

- Some of the translations for IdentityErrors are displaying the code/key instead of the actual message.

**Solution**

- Set the localizer to use the description/message instead of the code. Also fixed an issue where the wrong error was being shown.

---

#### **Job Management**

##### Incorrect Line Manager on Employee Profiles (#139500)

**Problem**

- An incorrect join was made from the reporting line ID instead of the user ID, as well as a missing Reporting line type

**Solution**

- Add change to include reporting line type as well as correct join

##### When viewing the linked positions, and you click on “ALL”, it only seems to show filled positions (#137435)

**Problem**

- When selecting Vacant positions, the position details are displayed, but once under ALL, the position is displayed with the user in that position reason being that the appointment has ended, and hence why it is vacant, but under all, it shows the user details still

**Solution**

- Update the logic check to include check to also not show user details when the end date has been reached

---

#### Performance Management

##### Unable to import templates when VB and LB sections are enabled (#137921)

**Problem**

- Front-end logic check was made to allow VB and LB section items on import

**Solution**

- Remove and correct section items

---

#### **People Management**

##### V9 We're sorry, screen when updating Reporting Lines (#139393)

**Problem**

- After appointing a person and editing the reporting lines, the user receives an unauthenticated error due to the people group check on the edit page. The default language error occurs repeatedly and fails silently. Error when executing service method \\u0027GetRulesetDefaultLanguageAnonymous\\u0027.","Exception":"System.InvalidOperationException: Sequence contains no elements\\n

**Solution**

- Introduces TempData\["ByPassUserActiveInPeopleGroupValidationCheck"\] = true before redirects in PeopleController to bypass user active group validation checks. Also updates RulesetQueries to return a default language if none is found, improving robustness.

---