beqom v10 HF197 - 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: March 26th, 2025 - PRD: April 1st, 2025
Fix version: v10 - HF 197.5 - DB 10.0.992
| Type | Reference | Description | |
|---|---|---|---|
| Zendesk | Jira | ||
| BQM-25371 | When running a merge operation in the Statement generation feature, if Generated File Name or Inbox Display Name, then the HTML character code, and not the accented character, was displayed in the file name and in the Inbox display name of the document. | ||
| BQM-25467 | An issue was reported regarding the login process where, under load, could cause issues for other users when using the system. The issue was related to the direct connection of the process to Launch Darkly (the Feature Flag provider) and has been corrected. | ||
| BQM-25479 | In Pay Predictor, the functionality of the Update prediction and Save buttons was combined into a new button: Update prediction. The previous buttons were removed. | ||
| BQM-25480 | In Pay Predictor, the functionality of the Find Model button was refined. It is now visible only when the core fields of the prediction are updated or if no model is found. | ||
| BQM-25483 | In Pay Predictor, when the user updates a prediction, any previous final offer values are now automatically deleted, with a warning. | ||
| BQM-25484 | In Pay Predictor, when updating a prediction or confirming in the Final Offer widget, the Save and Dischard Changes buttons were removed and replaced with an automatic save mechanism | ||
| #125033 | BQM-25511 | In data grids, when the user entered a value larger than the maximum value for the field type, especially in the case of the int data type, the system displayed an unclear exception that could not be used to correct the issue. The message displayed when the entered value is larger than the maximum value was improved for increased clarity and now reads "The value exceeds the maximum limit for the data type.". | |
| BQM-25516 | To streamline the model prediction save and update processes, a new API endpoint was created to handled both actions in a single request, thus reducing the complexity of the code and improving the performance. | ||
| BQM-25517 | In Pay Predictor, the final offer value was not cleared after updating the prediction, leading to incorrect data retention. The final offer is now cleared after updating the prediction to ensure accurate results. Affected API endpoint: POST /api/ml/prediction/{predictionId}/predict/model/{modelId}/save | ||
| BQM-25523 | A localization issue was observed in the Slack integration parameter, whereby incorrect labels or no labels were displayed for the parameters. Proper labels were added. Impact: new records in rps_localization | ||
| BQM-25618 | An issue was occurring when deploying the hotfix package causing the deployment to fail. Analysis revealed that the problem was due to a missing Sphere update; the update was deployed and the package can now be correctly deployed. | ||
| BQM-25559 | In order to improve the overall quality of the code of the Web Application interface, new test cases were implemented to increase the testing coverage. | ||
| #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. | |
| 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. | ||