Version 9.1.154 (7 April 2025)

Learning Management

When Marking Learners as Absent, if Send Notifications is clicked but cancelled Endless Load Logo Loops over Interface (#129847)

Problem

• The loading screen is shown indefinitely on the attendance register. 

 

Solution

• Removed loading variables from the attendance list and attendance modal 

 

Confirmation on Send Notification for Absent Learners Modal Status is referencing the incorrect Email Locations (#129608)

Problem

• Custom to email recipient data was not applied because the parameter name was incorrect

 

Solution

• Fix parameter name and also handle cases where the custom email field is whitespace

 

On Save Button, Click Deselect Current Cell to Ensure Field Save (#129363)

Problem

• Edits on the mark sheet do not commit when clicking the save button without leaving cell edit mode first

 

Solution

• Commit values to the mark sheet on the save button even when the mark sheet is still in edit mode

 

---

Imports

Import from PaySpace (#128700)

Problem

• When the end date received from Payspace is equal the the start date which is the case with enrolments the record is rejected.
• When the termination reason is not available in the case of the above case the record is rejected.
• When an appointment is updated in Payspace the user receives a new position ID which causes a new position to be created in Signify for each update of the appointment.

 

Solution

• Remove the end date >= start date pre-import validation
• Remove the termination required when the end date is provided pre-import validation
• Change the position code to a concatenation of the organisation title and the employee id. This creates a position with a name per employee rather than per appointment change. This means that positions will not be reused should the employee transfer to a new position in Payspace

 

Cleanup duplicate records (#128477)

Problem

• When an appointment is updated in Payspace the user receives a new position ID which causes a new position to be created in Signify for each update of the appointment.

 

Solution

• Change the position code to a concatenation of the organisation title and the employee id. This creates a position with a name per employee rather than per appointment change. This means that positions will not be reused should the employee transfer to a new position in Payspace

 

---

People Groups

Grouped condition for reporting lines not working (#129613)

Problem

• When selecting a reporting line for custom grouping an error is given and no reporting lines are displayed.

 

Solution

• Included missing variable in SQL that loads the PeopleGroupReportingLine objects

 

The summary page is blank after creating a new Custom group and adding an org condition (#129079)

 

 

---

Organisational Structure

When the Org name is too long the (people, Vacancy, Inactive) does not appear (#129186)

---

People Management

Informational displaying incorrectly calculated year/month count (#128994)

Problem

• An employee's termination date is not taken into account when calculating how long they've been in a position

 

Solution

• Used employee's termination date to calculate duration in position if employee has been terminated

---

Notifications

Emails are still being sent after the Tenant has reached expiry and close dates (#129519)

 

---

Performance Management

Final Review - Autocopy error (#129765)

---