beqom v10 HF172 - 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: June 26th, 2024
Fix version: v10 - HF 172.2 - DB 10.0.951
| Type | Issue key | Description | |
|---|---|---|---|
| Zendesk | Jira | ||
| BQM-23855 | Web App: Default Profile Required to Change Date Format The following issue was reported in the Web Application interface: when attempting to change the date format for the user under User > Settings , the changes could not be saved and an error message was displayed if no value was selected for the default profile in User > Profile . This behavior has been corrected; the default profile no longer prevents users from changing the default date format. Database update for localization of the error message displayed upon saving | ||
| BQM-23977 | Web App: Custom Localization not Available for Hierarchy Names in In the , when creating a comp round, if the name of a hierarchy was managed using custom localization (i.e. a localization key instead of a chain of characters), the custom localization was not properly managed and an incorrect name was displayed. The problem was corrected; custom localization is now handled as expected. | ||
| BQM-24238 | Web App: Upgrade Front-End Packages As a standard application maintenance procedure, various packages and components used in the front-end of the Web App interface have been upgraded to the latest version. | ||
| BQM-24327 | Web App: Add Logs for Statement Generation In order to offer more analysis capabilities in case of issues with the statement generation feature, new logs have been added to Datadog. | ||
| BQM-24428 | Web App: Cannot Open Process Grid An issue was observed where process grids could not be opened after deployment of the latest application fixes. Investigation of the problem uncovered a misspelled function in the DACPAC and Sphere updates. The problem was corrected by recreating the function with the proper name; process grids can now be opened without error. Database update to drop the misspelled function and recreate it with the correct name | ||
| 103451 | Web App: Default Process Behavior After an inconsistency of behavior was reported between the Web App interface and the Admin Portal interface regarding the default process opened when accessing the (i.e. Admin Portal opened the last opened process while Web App opened the first process in the list), the behavior of the Web App interface has been modified and aligned with that of the Admin Portal interface; now, when the user navigates to a process grid, changes pages and then opens the again, the last opened process grid is opened by default. | ||
| 104203 | Web App: Population Exclusion not Correctly Applied in Team Documents An incorrect behavior was observed in the : when team documents were generated and hierarchy security and population inclusion were used to determine the visibility of the documents, the security parameters regarding document visibility were not correctly applied and unauthorized users could see the documents belonging to hierarchy nodes to which they should not have had access, specifically, the documents of the root node of the hierarchy. The problem has been corrected and the visibility parameters are now properly applied to team documents. New function UDF_IsInTreeSecurityPopulation added to the database, stored procedure Kernel_SP_Hierarchy_GetTreeContent modified | ||
| 105192 | Web App: Performance Improvement for Statement Generation In order to improve the performance of the statement generation feature, an unnecessary index was removed from the application database. Database index removed on table [Statement].bqm_merge_recipient | ||
| 108566 | Web App: Application Crashing when Scrolling Down Process Grid The following problem was reported: when the real-time calculation feature was configured on a process grid and the page of the grid required the user to scroll down to see then last rows of the grid or to see additional columns, if the user made changes in the grid that triggered the RTC and then scrolled an error would occur and the grid would crash. Investigation of the issue revealed that unnecessary RTC execution calls were triggered when scrolling. The logic of RTC validation mechanism has been modified to keep only the required calls and the issue is no longer visible. | ||
| In this Release Note | |||