Version 9.1.271 (9 November 2026)

EventSchedulingEvent Scheduling

Fix event scheduling calendar infinite height scrolling (#157675)

Problem

• When zooming in on the calendar (or on smaller screens), the calendar view would sometimes gogrew intoinfinitely an infinite vertical height growth.tall.

 

Solution

• Decouple the calendar’s container height from its internal content sizing to prevent resize feedback loops while preserving responsive layouts. Co-authored-by: William

---

Onboarding

Corrected identity email urlURL and active people group (#154461)

Problem

• An incorrect appsetting was used to generategenerated the email linklink. When appointing an external candidate, the All People selection was being cleared before the organisation tree loaded. This could hide organisational units or prevent them from appearing.

 

Solution

• Corrected appsetting keykey. The All People selection now stays in place, allowing the appointment page to show all active organisational units while preserving existing permissions.

---

Performance Management

Resolve issue where Overall Contract Final Score is captured when only a single review period is approved (#157720)

Problem

• When you have multiple review periods, starting and rating any single review period incorrectly captures the overall contract final score. This happens because the ContractPeriod entity only gets added to the Contract entity once the user actually starts a contract, so at the time of approval, regardless of how many review periods are required, there are only ever as many Contract Periods available as waswere created. Meaning that when it checks whether "all contract periods are finalised", it is actually just checking whether all the created ones are finalised,finalised; it does not take into account Review Periods / Contract Periods NOT YET created. The front end handles this appropriatelyappropriately, and the user continues as per normal,normal; it does cause issues down the line however in that because the FinalScore is set, the contract is seen as "finalised" and as such certain actions are blocked (for exampleexample, importing 360 surveys don'doesn't happen because the contract is already completed).

 

Solution

• Modify the conditional check that determines whether the contract is seen to be finalizedfinalised by taking into account all expected review periods / periods/items to be completed.

---

Report Builder

Adding additional configurations (#157544)

Problem

• The live environment does not display any DWH refresh jobs because its jobs are running on the UAT database server.

 

Solution

• Added configuration to retrieve DWH refresh jobs from the correct database server for each environment using the existing linked server setup. Also added configuration to filter jobs by their naming convention, ensuring that live only displays live jobsjobs, and UAT only displays UAT jobs. 39 minutes ago

 

---