Version 9.1.164.2 (Support Release - 5 June 2025)

Performance Management 
 Performance Management: Incorrect Total after 10/10 Self-Rating and Error on Submit Final Rating (#131647) 
 Problem: 
 
 The scores within ContractPeriods do not round correctly when they round to above 100 
 Due to the increasing number of KPIs and the distribution of their respective weights, there is a potential for precision-related discrepancies during the selection and calculation of the final rating. As a result, the computed value may appear as 10.001 instead of the expected 10. 
 The final ratings could not be submitted due to the system not accommodating a score of 100.0000, which resulted in a submission failure 
 
 Solution: 
 
 Adjusted the rounding issue for ContractPeriods scores to ensure it does not exceed 100 
 New logic was implemented in the score calculation to allow for slight overcalculations, which are then adjusted to the appropriate floor value. 
 The system has been updated to allow for larger max rating scores. 
 
   
 Path to link Signify to Power BI (#132335) 
 Problem 
 
 An additional api required to export all user contract data for a review year and review setup 
 
   
 Solution 
 
 Create a copy of rpc ListReviewYearSetupUserContracts (ListReviewYearSetupUserContractsRequest) returns (ListReviewYearSetupUserContractsResponse); and extend to include all users 
 Include location in org 
 Remove image path for performance 
 
   
 
 People Management 
 [My Profile] Error shown when user clicks on My Profile (#132878) 
 Problem 
 
 When a user who does not have an admin role tries to view their profile, the page breaks. The problem is that it tries to fetch the active products for the tenant/ruleset, but the call to get ruleset information is admin-authorised only. 
 
 Solution 
 
 Changed to get the tenant ID from the available anonymous call, which is then used to fetch the tenant subscription information. 
 
   
 
 Imports 
 PaySpace Signify discrepancy script (#129254) 
 Problem 
 
 When data is not staged in the user stagings for an import, then the exported Excel sheet is broken without data. Data fields are inconsistent in the export 
 
   
 Solution 
 
 Add a check to export a default error 
 Add a cast to shortdatestring for datetime and datetime? fields 
 
   
 Person not updating via Import (#132260) 
 Problem 
 
 When the Payspace client does not grant access to the OrganizationPositionDetail, then the following API call fails as forbidden 
 string url = $"{connector.BaseUrl}/v1.1/{companyId}/OrganizationPositionDetail?$count=true"; 
 
   
 Solution 
 
 Add try catches when pulling data for the OFO code to suppress and log the failure should it occur, and then continue with the import 
 
   
 V9: Import Issue (#132815) 
 Problem 
 
 When providing other data in the import for org level 1 than the default IN01 data, the import fails with the error: The org node to link the user's position to could not be found." 
 
   
 Solution 
 
 Add org level 1 as received data, and fall back to the default only when no data is provided