Version 9.1.174.3 (Support Release - 31 July 2025)

Ruleset Management

Save button on Ruleset 1 not saving after editing (#134847)

Problem

Imports

People Management: Payroll connector is not populating Job grade (#134763)

Issue 1

Problem

• The import is blocked by address validation when the address is available in the payroll but not used in Signify
  
• The current PowerShell connector is outdated
  
• It is difficult to see why the actual user import is not running

Solution

• This pull request introduces several changes aimed at improving validation logic, enhancing logging, updating PowerShell script templates, and refining UI elements. The most significant updates include removing redundant address validation logic, adding a new logging step for incomplete imports, modernising the PowerShell script for Sage Payroll integration, and updating UI icons for clarity.

Issue 2

Problem

• Not all fields are mapped from a PowerShell script.

Solution

• This pull request enhances the ProcessPowerShellPayrollConnectorsCommandHandler class by extending the user data mapping logic to include additional fields. These changes improve the comprehensiveness of the payroll processing functionality by capturing more user attributes.

Learning Management

-1 does not save (#134762)

Problem

• When overriding is enabled on the Mark Interventions, we only save the marks if they are manually entered. If we copy and paste values, the marks for those students are not flagged as overridden.
  Please note that entering '-' also does not set the override flag

Solution

• Replaced the logic that is used to determine if a user's mark has been overridden. Allowing copy and pasting when the Mark Interventions are set to auto with override enabled

Cannot add comment for learner (#134761)

Problem

• Copy and paste text that contains text that starts with a month name.
  
• It automatically switches to date and time format `DD/MM/YYYY`

Solution

• Set the format to be text only for comments and Numbers only for Marks
  

HR Processes

HR Processes emails (#134452)

Problem

• When the Request Workflow levels are set up in such a way that the direct next level approver is the same as the current approver, the next level is auto approved as well. In this case, the notification howeve,r is not sent should there be a subsequent approver, since the request's current approval level does not take into account those levels that have been auto-approved.

• Consider workflow:
  Level 1 - Line Manager is Approver
  Level 2 - Specific Position E.g. Hr Admin
  Level 3 - Specific Position E.g. CEO

• If the originator of the request's line manager is also the Hr Admin, then when the Level 1 approval happens, Level 2 is also approved automatically.
  
• The notification, however, sends through the current approval level (Level 1), and the recipient is retrieved for the next level (Level 2). The Hr Admin then ends up receiving two emails, and the CEO never receives the email (although the request correctly falls into their queue).

Solution:

• Ensure that the current or subsequent next level approval is sent to the notification event to ensure the correct level approver recipient is retrieved.