Version 9.1.242 (6 July 2026)

Performance Management 
 Resolved Export of Contract With Action Items (#151569) 
 Problem 
 
 When a contract has action plan items and is exported, there is an error that occurs saying the dataset already has this table defined, currently a foreach over each section a table is added to the data set, but the action plans has a different implementation where it builds its own table and adds that to the dataset afterwards, but no check exist likewise to the other foreach to merge if exists 
 
   
 Solution 
 
 Implemented a change to check if it exists; just merge 
 Also added the tab ID implementation to ensure only one file is prompted to download when there are multiple open files 
 
   
 
 Imports 
 PaySpace cell number formatting and position effective date (#150845 & #146760) 
 Problem 
 When employee details are pushed to PaySpace, two issues were causing records to be rejected: 
 
 Cell phone numbers** were sent in a format PaySpace/SARS would not accept. South African mobile numbers captured without their leading "0", and numbers belonging to other countries PaySpace supports, were not converted into the layout PaySpace expects, so the push failed. 
 Newly created employee positions** were rejected with "Effective date required" because the position was sent to PaySpace without an effective date. A related rejection, "Effective date cannot be before the employee's group join date", could also occur when the date used was earlier than the date the employee joined the group. 
 
   
 Solution 
 
 Cell phone numbers are now tidied up automatically using a standard phone-number library that knows the rules for each country. South African numbers get their leading "0", and numbers from other countries are sent in the international "00 + country code" format PaySpace expects. Numbers that cannot be understood are still passed through cleanly rather than blocking the employee. 
 When a position is created for an employee, it is now always given a valid effective date, so PaySpace accepts the record. The date used is the current date, which always sits on or after the employee's group join date, so neither rejection occurs.