beqom v10 HF69 - 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: October 13th, 2021
Fix version: 10 - 44167 - 10.0.620 - Release-BeqomApp-v10-Package-HF69.2 - BeqomApp.WebApp_10_55965
| Type | Issue key | Description | |
|---|---|---|---|
| Zendesk | Jira | ||
| 46368 | : Error when Switching Node in Process Grid Tree The following incorrect behavior was reported in the beqom : if a process grid was configured with an attached manager report opened by default when opening the grid, the application returned an error when users attempted to access another node in the grid hierarchy. The issue has been corrected; now users can correctly open another node in the grid hierarchy tree while having a manager report opened. Impact area: Process > Grid hierarchy node access | ||
| 48106 | : Incorrect Child Data Grid Values after Row Addition When working in a data grid with parent-child relations, if users opened a child grid and added a new row to the grid, if they repeated the operation in another child grid, it was noticed that the metadata from the previously opened parent grid were linked to the child grid which was incorrect. The issue has been corrected; now the correct metadata are linked from a parent to a child data grid after adding a new row to the grid. Impact area: Data > Parent-child metadata display | ||
| 49329 | Back-End: Incorrect Data Type ID in Synchronized Table If a table with an integer data type column as the primary key was synchronized in the application, it was reported that when adding data to that table via the classic-datasource/{id:int}/data in gateway api/v2 API, the data type ID returned was not integer as expected. The issue has been corrected; now the correct data type ID is returned when using the mentioned API to add data to a synchronized table with integer data type as primary key. Impact area: Application back-end | ||
| 49381 | Admin Portal/ : Cannot Filter Standards Reports with Decimal Values The following issue was reported in the beqom Admin Portal or in the : when working with standard reports, if users attempted to filter a "numeric box" field with a non-decimal value (more than 1000), the application returned an error. Investigations of the issue revealed that the error occurred because of a conflict with the thousand separator option and integer values. The issue has been corrected, now users can filter standard reports with integer values a expected. Impact area: Analysis > Filter report with integer values | ||
| 49880 | Admin Portal: Data Operation Calculation Issue in Exported Process Grids When several data operations were configured between different fields in a same column in a process grid, if users exported the grid to Excel and modified the fields values, the calculations were not triggered as expected. The issue happened because the application back-end was not supporting more than one data operation at a time on a same column. The issue was corrected; now several data operations can be configured on between different fields in a same process grid column. Impact area: Process > Data operation calculation in exported grid to Excel | ||
| 49989 | : Enable Custom Default Navigation Theme In the previous version of the beqom , the default navigation theme was "dark" and this parameter could not be changed. As of this Hotfix package, admin users can choose the default navigation theme ("dark" or "light") of the application for all the tenant users. Each user's navigation bar theme parameter will now be set to "Default System Setting" which corresponds to the theme chosen by the administrator. Therefore, users will still be able to choose their own theme via User > Settings > Navigation bar theme . This is an note/information message. According to the option chosen by your administrator, your application theme might change from the previously chosen one. Updated sphere scripts with a new k_parameters 'PRM_DefaultNavigationBarTheme' entry: navigationBarTheme column default value changed from "default" to "dark" Impact area: UserSettings > New "Default System Setting" in navigation bar theme drop-down | ||
| 50091 | Localization Update The rps_localization table has been updated in order to make sure that the beqom application is fully localized. Updates to rps_localization Impact area: None | ||
| #49035/#49816 Back-End: WalkMe Stylesheet Loading Issue It was reported that when users with the correct permissions to their profile added the WalkMe key into beqom, the application was not able to load the WalkMe stylesheet parameters. The issue occurred because of missing Content Security Policy (CSP) rules for the WalkMe third-party application. The issue has been corrected by adding new rules into the CSP header allowing the WalkMe application to add custom styles and fonts. Impact area: Application back-end | |||
| In this Release Note In this package, we have integrated #49768 and #49769 as part of the ongoing integration of new features in the beqom application. | |||