Skip to main content

Version 9.1.199 (15 December 2025)

Ruleset Management

Set base url when a schema is created during ruleset creation (#137697)

Problem:

When a new ruleset is created or schema setup request is made the module setting SETTING_EXTERNALSERVICES_SAAS_APPLICATION_URL is not updated. This caused the assisgnment document annotation not to work.

Solution:

When the ruleset is created/ schema setup requested sent the MVCUrl in the appsettings to V8.
Use the value to update the application URL
Confirm that the learning and content management API URLs are also synced to V8 and populated in the approriate settings.

Add scheduling to the imports on V9 (#136927)

Problem:

Unable to control how many times payroll connector should run per day on a specific ruleset.
Unable to change the schedule of the V8 bulk sync
Unable to disable the V8 bulk sync

Solution:
  • On ruleset management| Integrations | General add simple scheduling 
    • Make the occurrence always in hour intervals, set the starting time in increments of 5 min. Add an optional ending at field
    • Add a flag to disable the schedule, when disabled that type of import will not run on the ruleset
  • Allow multiple occurrences to be configured for each schedule item e.g
    • Occurs every hour between 6h00 and 10h00
    • Occurs every 6 hours between 11h00 and 24h00
  • Add two separate schedules under Integration | General  : 
    • Run Payroll connector
    • Run Bulk Additional Sevice Imports
  • Add schedules next to each of the bulk pulls
  • Ensure the schedules are disabled when the Tenant subscription expires or the ruleset is disabled


Audit

Move Support backups to central archive V9 (#136527)

Problem:

When doing support an altering data the support dev creates a backup of the data either for just the single rulesets or all ruleset within the live DB. This clutters the DB and increase the size unnecessarily.
 
Solution:

Add a new DB V9_Master_Archive.
In this DB data will be stored as was done in the V8 archive DB. With the DB schema being the the name of the DB where the backup comes from and the table name the concatenation for the DB schema and Table name e.g [V9_Master_Core].[Account_Users_Description]
Make a copy of the sp_backup table in V8 and add ruleset Id to the SP
When the ruleset id is defined then only backup the data for that ruleset, add the ruleset id to the archive table name by default along with a description
Add this SP as a migration in each service


People Management

Streamline V9 to V8 sync (#126727)

Problem statement
The V9 to V8 sync failing causes users not to be able to login to learning portal
Solution

Create new user import same as job structure import C_03427_99999_sysImportJobStructure) for only employee information

As a People Management Admin viewing the Appointment History, I want to change the Reason for Ending (#139964)

Problem

  • Managers previously had no way to edit or correct the termination reason (e.g., Resignation, Termination for Cause) or the last day of service for an employee's appointment after it was terminated, leading to permanent inaccuracies in employee records.

Solution

  • Updated and added existing and new logic so that managers can now edit the termination details (reason and last service day) for terminated appointments directly when editing the appointment's details.

As a People Management Administrator, I want to have two new Reporting Lines for the Parent/Guardian (#134213)

Business Rules 

Two new Reporting Line Type needs to be created  

Primary Parent/Guardian 

Secondary Parent/Guardian 

When logging into the system, the person will only see the people reporting to them in this Reporting Line Type 

Reporting lines to be added to V8 and the sync 

As a People Management Administrator, I want the same functionality as for the Line Manager reporting line type to apply to the Parent/Guardian reporting line type (#134214)

Business Rules 

A standard People Group Role should be created for a parent/guardian on R1 

Parent/Guardian People Group Role 

This is then propagated to all other Rulesets  

When the Parent/Guardian Reporting Line has been selected/filled, the People Group for this reporting line type should be created 

The person who is the Parent/Guardian, should then be given the Reporting Line Type with the Role in User Permissions | People Admin | Permissions based on Reporting Lines 

Remove the ABC Filter and Filtering Search 

Roles to be added to V8 and the sync  

At the end, this should work like the Line Manager reporting line type. 

[People Management][Edit Appointment] Reason for Termination dropdown not saving values (#141429)

Problem

The Reason for Termination dropdown does not save the value that is entered

Solution

Resolved issue to save 


Imports

(#140927)


Translations

(#127238)


Org Structure

(#136630)


Performance Management

New Functionality: Allow Multiple PM Agreements per Year (#134446)