Version 9.1.146 (24 February 2025)

Notifications

The user who registers does not receive their email (#126173)

Problem:
When a new user registers on the system using the Identity auto registration functionality:

  1. The default appointment record did not get created leading to the user being seen as inactive due to not having an appointment.
  2. The email confirmation email did not get sent out and the user could never continue with the registration

 

Solution:

 

Add time to Welcome email (#124699)

Problem

 

Solution

 


Data Warehouse

Add 2 new interpolation fields (#127243)
Adjust DWH deployment workflow for V8 DWH packages (#126906)
Problem
  • Workflow can only deploy V9 DWH packages
Solution
  • Adjust workflow (by adding a dropdown for V8 database names) to deploy the V8 DWH package. 
Grades Mismatched in Signify & SFTP (#126629)
Problem
  • Data did not return on ReportBuilder due to PeopleGroups not being refreshed (Performance issues)
Solution
  • Adjusted PeopleGroupUsers task in DWH so that the table is truncated only between 12 and 1 in the morning and not as well in the afternoons
The date field is not recognised as a date in the report filter (#125626)
Problem
  • ApproverDate fields within jpHRProcesses are set as NVARCHAR DataType and not DATETIME2
Solution
  • Set datatype for ApproverDate fields from NVARCHAR to DATETIME2

Import

Error on People Group Import Request under Integrations (#127998)

Problem

 

Solution

 


Learning Management

No error detail if absent notification cannot be sent to Parent/Guardian (#123832)

Problem

 

Solution

 


People Management

Error when a user tries to reset their password (#126175)

Problem

 

Solution

 


Learning Store

Learning Store Description on the deactivated product does not contain any information (#125890)

Problem

 

Solution

 


Master Data

Load indicator shown indefinitely when clicking on person's profile (#127605)

Problem

  • DapperInBatched was misused in the translation query, causing an invalid SQL query to be generated.

Solution
  • Ensure that DapperInBatched is used correctly for the query.
Navigating to the requirements tab displays an error (#127019)
Problem
  • Barched queries failed due to too many of the same foreign keys
 
Solution
  • Updated query to use DapperExtension to reduce the number of parameters and remove batch query functionality
Seeded data not appearing in drop downs on Employee Profile (#126916)
Problem
  • Location, country and provided master data did not displayed in the "Address" section due to conflicting component names which also appear in the "Summary" section.

Solution
  • Give unique names to the component elements, ensuring that the master data correctly displays on both "Address" and "Summary" sections

Ruleset Management

Able to log into a deactivated ruleset (#126304)

Problem

 

Solution

 


Performance Management

Interpolation to allow decimal actual values (#126547)

Problem

 

Solution

 


 

 

 

 


Revision #1
Created 14 February 2025 09:29:07 by Lee-Ann Janse van Rensburg
Updated 22 April 2025 08:54:37 by Lee-Ann Janse van Rensburg