Version 9.1.125 (21 October 2024)

Ruleset Management

Better ruleset URL handling (#120938)

Problem

• A vague error message is displayed when the ruleset cannot be determined from the URL.

 

Solution

• Display a more appropriate message when the URL is incorrect.

 

Improve reporting line sync - reporting lines created with reporting line import from V9 to V8 (#119203)

Problem

• Currently reporting lines are synced to V8 from V9, row for row 
  

 

Solution

• Do reporting line sync in bulk or batches, at least
  
• Only do incremental updates where there are changes, not all every time

---

Imports

New employee created when you update the username while using the externalId or Employee Code setting (#121154)

Problem

• The username import settings could not be saved on the integrations tab
  
• The setting did not trim the values correctly when comparing the string fields
  
• The external ID is not updated to the new value the user is imported with
  
• The message displayed after the import was incorrect
  
• The order of the import tab was not correct

 

Solution

• Correct the js that selected the checked value of the settings
  
• Added trims when comparing employee and/or ID number fields
  
• Used the correct external ID when updating the user
  
• Change the message displayed from

 

---

Data Warehouse

Add a field for the agreement check-in ratio (#120046)

• Agreement Check-In ratio

Add a step to DWH SSIS Packages to clear the People Group Users table (#115619)

 

---

Report Builder

Have the People Group by default to use when running the report (#115616)

• Always include the People Group filter when adding a report with people data
  • This is added as a dropdown in the Report Filter Options Accordion 
  • This option is always the first one
• The Active People Group will be used as default but can be changed

 

Modify Report Builder Stored Procedure (#115618)

• Modify Report Builder Stored Procedure to include join to DWH people group users table when ‘Users’ data source is included on the report
• Alternatively, we might be able to set up the DWH table as a JOIN to Users, this table should just never be selectable as a data source on the Data Dictionary