beqom v10 HF51 - 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 9th, 2021
Fix version: 10 - 43279 - 10.0.512 - BeqomApp.Gateway_10_49843 - BeqomApp.WebApp_10_49837
| Type | Issue key | Description | |
|---|---|---|---|
| Zendesk | Jira | ||
| 41966 | /Back-End: Grid Synchronization Issue from Source to Target Tenant The following issue was reported on the back-end side of the beqom : when users attempted to migrate a grid from a source to a target tenant via the Environment Manger, an exception was thrown and the migration could not be completed. The issue occurred because the application returned a validation exception because the tenant unique identifier was different from the unique identifier registered in the catalog database for table synchronization. The issue has been corrected; now grid synchronization is working as expected when migrating a grid from a target to a source tenant via the Environment Manager. Impact area: Application back-end | ||
| 42601 | Admin Portal/ : Cannot Filter on Column with Percentage Fields in Process Grids The following issue was reported in the beqom Admin Portal and the : when working in process grids configured with a column containing percentage fields, if users attempted to filter the grid based on that column, the filter was not applied as expected. The issue has been corrected and now users can correctly filter process grids based on percentage field columns as expected. Impact area: Process (Web App) and Process (Admin Portal) > Filter on percentage field columns | ||
| 43068 | Admin Portal: Security Enhancements In order to prevent unauthorized users from downloading, approving or rejecting notifications and documents in the beqom Admin Portal, the security of the mentioned processes have been enforced. Impact area: Application security | ||
| 43430 | : Manager Report Incorrect Behavior when Switching Process Grids When working in a process grid to which a manager report was attached, if a user opened the report and switched to another process containing a manager node, it was reported that the manager report from the previous grid was attached instead of the correct one. The issue has been corrected; now the correct manager report is attached after switching from a process to another. Impact area: Process > Manager report display | ||
| 43881 | Admin Portal: Data Component SQL Injections Security Improvement (Part 2) In order to improve the overall security of the beqom applications and more precisely to prevent unauthorized users to export data grids, the security against SQL injections have been enforced in the . Impact area: Application security | ||
| 43931 | : Cosmetic Issue in the Appearance Section of the The following cosmetic issue was noticed in the beqom : if an incorrect HEX value was entered in the Appearance section of the , the sentences "Minimum 6 characters are required." and "UPLOAD CUSTOM LOGO" were overlapping. The issue has been corrected by adjusting the layout code and now the two sentences are no longer overlapping when an incorrect HEX value is provided. Impact area: Admin > Cosmetic issue in appearance section | ||
| 44060 | Admin Portal/ : Always Accept "PNG" Format Images as Profile Picture As of this Hotfix package, the upload of "png" format images as profile picture in the beqom Admin Portal and the is now always allowed. Furthermore, admin users are no longer able to deselect the "png" format in ADMIN > Settings Management > Global > User Image Formats in the beqom Admin Portal. Impact area: UserSettings (Web App) and "User Settings" (Admin Portal) > Profile picture upload | ||
| #41428/#42251 : Home Page Displayed in Analysis Report The following incorrect behavior was reported in the beqom : if a standard report was configured on the , when users accessed the component but switched to the before the report was fully loaded, if they clicked any of the available reports, the Home page screen was displayed instead. Investigations revealed that the issue was due to the Web browser blocking the request to display of the correct report when users rapidly switched from the "Home" to the . The issue has been corrected and now when users switch from the Home to the Analysis component the correct report in the Impact area: Home , Analysis > Report display | |||