beqom Pay Suite 17.1 - Detailed release notes
This article lists the new features that have been added to the platform, as well as the bugs that have been corrected in the intermediate 17.0 release of the Pay Suite application and in the subsequent patches.
17.1
Deployment to staging environments: November 4th, 2025
Deployment to production environments: November 11th, 2025
| Type | Issue key | Module | Description | |
|---|---|---|---|---|
| Zendesk | Jira | |||
| AC-15723 | Performance Management | An issue where a vertical scroll bar appeared in the Chat widget of the goal page was corrected. | ||
| 128278 | AC-17246 | Performance Management | Users now have the possibility to define their own time zone in the Settings page available from their avatar menu. | |
| AC-17282 | Compensation | The default display name generated by the system for data points in the column configuration tool of the Team planner view step of the compensation round configuration wizard was improved to generate names for each data model field based on its type. | ||
| AC-17283 | Compensation | The payroll data drop that Global compensation administrators can download from compensation rounds now contains the effective date of the round. | ||
| AC-17502 | Data Foundation | Code quality issues raised by internal quality tools were corrected in order to increase overall code reliability. | ||
| 135688 | AC-17562 | Performance Management | The goal type name and the goal plan name are now included in the goals endpoint of the outbound API. | |
| 136915 | AC-18237 | Performance Management | An error 422 was displayed in Workbench when attempting to add additional review owners to a historical performance rating upload. | |
| 136280 | AC-18376 | Performance Management | When adding new local owners to a review template, the change did not trigger a republishing of the template (i.e. the owner of the template needed to republish it manually). | |
| AC-18391 | Performance Management | As part of the implementation of the "goal setting" review type, managers can now see and edit reviews of this type. | ||
| AC-18400 | Pay Transparency | When editing a pay information request, HRBPs now have the possibility to upload a static PDF document to the request. | ||
| AC-18580 | Pay Transparency | A bearer token issue that made the documentation of API endpoints in Swagger unavailable was corrected. | ||
| AC-18584 | Pay Transparency | As part of the yet unreleased implementation of the pay information request feature, it is now possible to update an information request with the option to generate a document, select a document an d use a snapshot as a data source. | ||
| AC-19025 | Compensation | When using the payroll data drop feature from a compensation round, the code and the label of any custom fields included in the exported file are now visible in the export. | ||
| AC-19108 | Compensation | In order to improve the quality and ease of maintenance of the code, the way hierarchy data is retrieved in different views within Planner was homogenized. | ||
| AC-19181 | Pay Intelligence | An API endpoint was created to provide Pay Transparency with information regarding the fields that have a larger weight in the determination of the pay and salary progression of a worker. | ||
| AC-19254 | Pay Intelligence | New authorization roles were created based on PayAnalytics actions to simplify access management in the context of the integration of Pay Suite and PayAnalytics. | ||
| 138545 | AC-19353 | Authorization | An issue where some users could no longer be proxied after a creating a new organization and importing worker data was corrected. | |
| AC-19364 | Pay Intelligence | The auto-update functionality was implemented in the Machine Learning model configuration wizard. | ||
| 138689 | AC-19488 | Performance Management | In Planner, when a manager selected a team member, feedback information was displayed in the drawer, including information related to public feedback, even if the feature was not used. This was due to the fact that the permissions were not properly checked when displaying the drawer. | |
| AC-19529 | Pay Intelligence | In the Model Factory feature of Pay Intelligence, a warning indicating that the features will be cleared is now displayed when the user changes the population of a model. | ||
| AC-19668 | Compensation | Page headers were missing in the Compensation Management pages. They were added to ensure proper accessibility of the platform. | ||
| AC-19681 | Pay Intelligence | The query that retrieves user details in PowerBI reports was replaced with a new query using materialized views instead of common table expressions. | ||
| AC-19786 | Compensation | The way that alerts are displayed to users in list of compensation rounds Workbench > Compensation Management > Compensation Rounds was redesigned to make it more consistent and less disruptive to the overall layout of the list. | ||
| AC-19808 | Compensation | The experience of the audit trail when working in a compensation round in Planner was redesigned for a more consistent experience across the platform. | ||
| AC-19812 | Authorization | An event trigger was added to synchronize custom authorization attributes with Elasticsearch. | ||
| 139403 | AC-19846 | Authorization | A timeout error when uploading data into the data foundation was corrected. | |
| AC-19870 | Data Foundation | Data upload notifications were enhanced to include the impacted unique keys in the case of a partial upload so that the user can decide if they want to make a snapshot of the difference based on the notification. | ||
| AC-19873 | Data Foundation | The data upload log file now contains the number of ingested records in order to avoid triggering unnecessary live data snapshot update. | ||
| AC-19893 | Data Foundation | Conditional presence rules for Min/Max and Currency fields were put in place in all relevant entities of the Data Foundation in order to be able to perform conditional validation on these fields. | ||
| AC-19988 | Compensation | In the list of bonus plans, under Workbench > Compensation management > Bonus Plans, Compensation admins and Global compensation admins can now see an alert next to bonus plans in Draft or Ready status to which a goal plan is attached if any change is made in the Goal, GoalPlan or GoalPlanGoalAssignment entity. | ||
| AC-20004 | Compensation | The platform theme (i.e. the application color) can now be selected and saved at platform level under Workbench > Platform Setup > Appearance. | ||
| AC-20039 | Compensation | A new option is available in the Team planer view step the of the compensation round configuration wizard. Specifically, the Feature enablement tab was renamed Planner add-ons and now contains a Worker compensation history option where compensation admins can configure the compensation elements, as well as the number of events available in the compensation history of the workers. | ||
| AC-20045 | Compensation | A drawer was created to configure the Worker compensation history from the Team planer view step the of the compensation round configuration wizard. In this drawer, compensation admins can configure the compensation elements, as well as the number of events available in the compensation history of the workers. | ||
| AC-20049 | Pay Intelligence | In the Machine Learning service, a computed IsCategorical property to the ModelFeatureDto class to automatically determine whether a field is categorical based on its type. | ||
| AC-20064 | Performance Management | Goal population sychronization timed out when the tenant contained a lot of data. The synchronization process was optimized to ensure that the synchronization works properly. | ||
| AC-20071 | Compensation | useCustomFetcher was replaced with Axios to centralize error handling, improve debugging, and gain full control over network requests at platform level. | ||
| 139372 | AC-20076 | Compensation | Graceful handling was added for network disconnections to prevent crashes, display clear user messages, and enable automatic request retries when the connection is restored. | |
| AC-20092 | Data Foundation | The IsDeleted database column is now handled in all entities and enums of the Data Foundation. | ||
| AC-20123 | Pay Intelligence | A configuration page was created to configure analysis data sets in the context of the integration between PayAnalytics and Pay Suite. | ||
| AC-20127 | Pay Intelligence | API endpoints were created to populate and configure the Data set mapping configuration screen of the PayAnalytics/Pay Suite integration. | ||
| AC-20142 | Pay Intelligence | An API endpoint was created to retrieve and populate a list of available analyses in the context of the PayAnalytics/Pay Suite integration. | ||
| AC-20163 | Compensation | Invalid HTML server responses are now handled to prevent crashes, inform users clearly, and enable automatic retries when recovery is possible. | ||
| AC-20178 | Compensation | Pluralization was added for the bulk deletion messages of custom/calculated fields in the compensation round configuration wizard. | ||
| 141524 | AC-20182 | Missing translations were added for all standard application languages in the application back-end repository. | ||
| AC-20196 | Pay Transparency | The ClamAV (antivirus) image of the platform was upgraded. | ||
| AC-20210 | Compensation | All numeric fields in generated PDF statements, included data model fields, comp round input fields, comp round calculated fields or converted amounts, are now displayed with two decimals. | ||
| AC-20287 | Authorization | A validation mechanism was added for custom attribute imports to allow only values defined in MongoDB, and ensure deleted attributes return empty arrays to clear outdated data. | ||
| AC-20312 | Pay Transparency | In the context of the pay information request implementation, an API endpoint was implemented to be able to preview and attach documents to pay requests without the "preview only" watermark. | ||
| AC-20322 | Performance Management | After the system administrator had enabled the Microsoft Teams/Outlook plugin for Performance Management, workers could still not access the plugin due to an error when retrieving the Microsoft Office settings. | ||
| AC-20336 | Data Foundation | New improvements were introduced to the Data Modeler, namely the size of the drawer, the list view which now contains a In use column and the possibility to extend models (add new fields). | ||
| AC-20340 | Pay Intelligence | The size of the font in the insights (statistics cards) used in Workbench pages was changed to a smaller size in order to not make the pages appear too busy. | ||
| AC-20355 | Compensation | When defining a budget in the Budget step of the compensation round configuration wizard, if the user entered 0 in the Outcome formula, the value was not saved. | ||
| AC-20390 | Compensation | The Validation step of the compensation round configuration wizard could not be opened in view mode; an error 500 was displayed. | ||
| AC-20392 | Compensation | When creating a compensation round with a data model containing compensation history fields, the compensation element code was not added to the display name of the fields in the Team planner view step of the compensation configuration wizard. | ||
| 141047 | AC-20399 | Performance Management | When a user created a goal by copying an existing item, published it, and then clicked Back from the copied goal, they were redirected to the Reviews page of Passport instead of the Goals page. | |
| AC-20427 | Performance Management | When managers attempted to open an existing goal from Planner, a message "An unexpected error has occurred." was displayed and the goal could not be opened. The issue was related to an incorrect API call and was corrected. | ||
| 141163 | AC-20428 | Compensation | Inputting a "&" character in the search bar at the top of the application window resulted in an error 500. The issue was corrected and the ampersand character can now be used in the search field. | |
| AC-20433 | Performance Management | In Workbench > Performance Management > Performance Review Templates > <TemplateName> Manage reviews, clicking View all to display the list of reviews resulted in an error 500. This error was due to an impossibility to retrieve review data and was corrected by adjusting the corresponding API calls. | ||
| AC-20434 | Performance Management | When a user created a goal and added their direct reports to the goal, the worker exclusions were not correctly applied and some workers could see the goal even though they should not have been able to. This was due to an incorrect API call and was corrected. | ||
| AC-20439 | Performance Management | After disabling the Microsft Teams/Outlook plugin, it was still possible to log into the plugin using the back button of the browser. The settings and permissions are now checked and properly enforced to prevent this action. | ||
| 140364 | AC-20566 | Pay Intelligence | The bonus and salary percentages were not displayed in the compensation dashboards in the Analytics Hub. These values were added to the relevant report pages. | |
| AC-20599 | Pay Intelligence | The Dataset Mapping Configuration feature was hidden from Workbench > Pay Intelligence for all roles other then the PayAnalytics-related roles. | ||
| AC-20605 | Performance Management | An error 403 related to the dataset mapping configuration endpoint was displayed when attempting to open Workbench. | ||
| AC-20617 | Authorization | externalId was added as a claim in access tokens to improve user identification and support external system integrations. | ||
| AC-20623 | Compensation | When users with only the HRBP role or with only the Compensation manager role opened the Planner and attempted to view the compensation history data of a worker from a comp round, the list did not open and an error was displayed. This was due to the fact that an endpoint to which these roles did not have access to individually was used. | ||
| AC-20707 | Compensation | An error 422 was returned when a user with the Compensation admin or Global compensation admin attempted to create a compensation round, after filling in the Key dates section and clicking Next due to the presence of a parameter of the API request that was not present in the back-end. | ||
| 141696 | AC-20722 | Authorization | Aan SSO login issue where oversized session cookies exceeded the browser’s 4KB limit, preventing users from logging in or returning to the previous page was corrected. | |
| AC-20756 | Authorization | When a professional role was assigned to a user, if that professional role was removed and the user had no other professional role, the user then could not log into the application anymore. | ||