beqom v10 HF198 - 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 this release.
Deployment date: NPR: April 1st, 2025 - PRD: April 8th, 2025
Fix version: v10 - HF 198.4 - DB 10.0.996
| Type | Reference | Description | |
|---|---|---|---|
| Zendesk | Jira | ||
| #116396 | BQM-24927 | In data grids, if a table had an id < 0 and object security was defined, the table was no longer visible in the Rapide "Synch" tables and also disappeared from the Grid Editor page in Admin Portal. The issue was corrected and tables are now visible as expected. | |
| #110648 | BQM-25250 | A new section was added to the document details panel of the Team Documents section of the Inbox component There, users can see the history of the document, with events such as the creation date, the update date, the status or download history. | |
| BQM-25471 | In the Pay Predictor interface, the prediction type value is now automatically defined. In addition, the drop-down selection list is now hidden when one data set is available. | ||
| BQM-25473 | In the Pay Predictor interface, the prediction creation window was redesigned and a new option was added to enable users to manually select the prediction. In addition, a button was added to automatically populate the name of the prediction. | ||
| BQM-25474 | In the Pay Predictor interface, when running a scenario for a new hire, a new drop-down list was added to enable users to search for a position by position name or ID. | ||
| BQM-25477 | In the Pay Predictor interface, when creating a prediction based on the position, all core fields and model fields are now automatically populated based on the data in the position table. | ||
| BQM-25488 | In the Pay Predictor interface, when running a prediction for a payee, the currency can now be set dynamically. For this purpose, a new function was created in the tenant database, which returns the currency code and exchange rate based on customer logic. | ||
| BQM-25535 | This improvement is the back-end implementation of the functionality to run a pay prediction based on the position (not based on a payee). | ||
| BQM-25560 | In previous versions of the Pay Predictor, there was no possible to delete all unused data snapshots at one. API endpoints were created to delete all unused snapshots and to delete snapshots for a given data set ID:
| ||
| BQM-25570 | This quality improvement removes an intersection-observer polyfill library that was used for Internet Explorer browser compatibility. Since Internet Explorer has been deprecated, this library is no longer needed. | ||
| BQM-25612 | To improve the general quality of the Pay Predictor code, an unnecessary asunchronous declaration was removed. | ||
| #128029 | BQM-25621 | In Pay Predictor, a correct value was used for the EoyRating3 parameter, but an incorrect value was stored in the database causing an error when running a prediction via API. The incorrect data storage was corrected. | |
| BQM-25628 | The initial currency code of the payee (current_pay_code_currency) is now returned in the response when running the prediction results API. Impacted endpoint: API /api/ml/prediction/{predictionId}/results | ||
| BQM-25629 | The currency for the Current Salary card of the Pay Predictor interface is now based on the current_pay_code_currency value. | ||
| BQM-25667 | An improvement to the RN service for subscription processing performance caused another performance issue when working on subscriptions. The original improvement was reverted. | ||
| #128568 | BQM-25708 | The fix introduced in ticket #120703/BQM-25337 (deployed in hotfix package 196) introduced a regression that gave the real-time calculation an unexpected behavior. This ticket rolls back the fix introduced in #120703/BQM-25337 and restores previous functionality until an acceptable fix can be found. | |
| #129185 | BQM-25723 | The following issue was reported in the Admin Portal interface: users kept getting logged out when using a custom profile. Investigation revealed that the issue was related to the use of a profile image that required an unnecessary permission to display this image. The dependency on this permission was removed. | |
| #128061 | BQM-25623 | When an email was sent via the scheduler, if the scheduler was recurring, and an email was processed, then the values in the Scheduler queue were not updated correctly, leading to the same email being sent multiple times. The issue was corrected; emails are now sent only one time and the Scheduler statuses are properly updated. Erratum: this fix was not included in the original hotfix package. It was added on April 10th, 2025. | |
| #128119/#129599/#129674 | BQM-25740 | A regression was introduced with the addition of the Slack integration, causing scheduled emails to sometimes not be sent. The issue was resolved; emails are now sent at their intended scheduled time. | |
| #129896 | BQM-25760 | A regression was introduced by the fix done in BQM-25740 due to an added condition on ScheduledDate. The logic did not account for cases where ScheduledDate == NULL, which appears to be a common scenario. The issue is now corrected. | |