Skip to main content

Version 9.1.159 (29 April 2025)

People Management

ESS issues (#130616)

Problem

  • When saving user information on People Management, an intermittent "Error occurred" snack is displayed
  • The problem is that user reporting lines are checked for changes, but all people groups are busted for the ruleset
  • This means that every time user information is updated for any user (or if nothing is changed and the Admin only clicks on Save), all the people groups are cleared from the cache and deleted from JobProfiler.MaterialisedPeopleGroupUsers
  • This creates additional race conditions when the PeopleGroupUpdated event is emitted, causing all services to try and refresh the MaterialisedPeopleGroupUsers table on JP, as well as when the page reloads, it needs to refetch the PeopleGroupUsers since the cache is empty

 

Solution

  • Changed the User reporting line upsert to only bust the reporting line and people group caches if any changes have occurred, and to only bust for the specifically changed reporting line types
  • Only bust the relevant PeopleGroupIds for the reporting line managerIds, not all people groups

 

Performance Management

Performance Management Errors (#131139)

Problem

  1. When doing the initial moderation and directly clicking on approve & recalculate, the moderation scores were not saved first, when you then unapprove the moderations, the moderation state is broken.

  2. On General Comments of a contract, the manager can click and view the person's comment which opens a modal that is editable. Saving then saves the exact comment for the person to the manager's comment. Same happens the other way around.

 

Solution

  1. Fixed the moderation approve & recalculate to always correctly save the moderation scores since their could also be interim changes. And on unapproval to correctly reset the contract moderation status.
  2. Changed the general comment modal to be not editable when it is the person viewing the manager's comments or vice versa

 

Job Profiler

Issue on New Appointment (#130526)

Problem

  • When adding a new (second or next) appointment or doing a transfer, the appointment fails with an invalid appointment start date error.
  • First issue is that the error is misleading as the problem should reflect that the end date overlaps the start date of the next appointment, secondly the check performed was incorrectly comparing the previous appointment's start date to be less than the next appointment's start date, which should normally always be the case so every appointment fails.

 

Solution

  • Changed translation to be more specific to the actual error/check.
  • Corrected the check to compare the current appointment end date against the new appointment start date.

 

Notifications

Notfications - Make sending welcome emails more robust and performant (#130837)

Problem

  • The grpc channel size is too small when the list of users receiving the welcome email is more than 7500
  • The welcome email fails should any user's reset URL fails to generate

 

Solution

  • Add a setting to give the option to increase the size, should it be needed. This is not part of the Helm charts, as it should not be
    Add tries to send the notification with an empty reset URL rather than failing the entire batch

 

People Groups

People Groups: Display incorrect number if people on "Custom" (#130594)
Problem
  • On the People Group list, the Included Users count does not match up with the actual number of users displayed when viewing the PG summary, This is because on the list page, terminated users still included on the PG are taken into account, as well as users that have both been included and excluded. It needs to show the same counts as you would see on the summary view.
 

Solution

  • Modify the included users count selection to only check for active appointments and to not include users that have also been excluded.

SigniChat

When first opening a new chat, the collapse button is missing (#130584)

Problem

  • When opening a new chat, the close button does not show as it formed part of the search section (which should be hidden when opening a new chat).

 

Solution

  • Ensure that the close button still displays when opening a new chat.

 

 

 

Back to top