beqom v10 HF36 - 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: February 17th, 2021
Fix version: 10 - 42474 - 10.0.397 - BeqomApp.Gateway_10_43956 - BeqomApp.WebApp_10_43925
| Type | Issue key | Description | |
|---|---|---|---|
| Zendesk | Jira | ||
| 35980 | Platform Management Center (PMC) Update In order to be able to correctly access premium languages in the beqom applications, the Platform Management Center (PMC) which is used to manage beqom tenants has been updated. Impact area: None | ||
| 37567 | : Grid Migration with Environment Manager Issue When a grid was migrated from a test to a production tenant using the Environment Manager in the beqom , sometimes it occurred that some fields of the grid were duplicated in the target tenant. After investigations, it was discovered that incorrect values were added in the d_source_tenant and id_source columns in the target tenant database after the migration. The issue has been corrected; now grid migration performed via the Environment Manager no longer create duplicated fields in the target tenant. Impact area: Admin > Grid migration with environment manager | ||
| 38495 | : Unexpected Error Messages when Using Deep Links The following incorrect behavior was reported in the beqom : when users attempted to use deep links from the , the error messages "Error 400, No Page to Display", and then "No Payee Found" were displayed for a short amount of time before the correct link was opened. The issue has been corrected; error messages are no longer experienced by users when using deep links from the . Impact area: Home > Deep links | ||
| 38504 | : Data Grids Permissions Issue When a profile was granted specific rights in order to perform actions in data grids (read, modify, export, etc...), some discrepancies were reported between the actual assigned permissions and the actions that users could perform in the grids. Investigations revealed that these permissions discrepancies were due to missing security checks in the related endpoints. The issue has been corrected and now the application always apply the correct rights related to the users permissions. Impact area: Data > Profile permissions | ||
| 38754 | : "Add Source" Button Alignment Issue in Data Models The following cosmetic issue was noticed in the beqom : when admin users opened a data model in the , the Add Source button was not correctly aligned with the Data Source List search field. The issue has been corrected by adjusting the style of the Add Source button which is now correctly displayed. Impact area: Admin > Add Source button display in data models | ||
| 38755 | : Ad Hoc Data Models Page Incorrect Behavior When admin users accessed the list of Ad hoc data models in the , it was reported that when they opened a model containing a large amount of columns and scrolled the page, the search section on the top of the page was not frozen as expected. The issue has been corrected; now the search section of Ad hoc data models is always displayed frozen (non-scrollable) when users scroll the list of available columns for a model. Impact area: Admin > Ad hoc data model list | ||
| 38756 | : List of Data Models Design Update In order to improve the user experience and to maintain a design consistency through the application, the display of the data models list in the beqom has been modified. From now on, the data models list visible in the component are displayed with the application standard list design. Impact area: Admin > Data model list design | ||
| 38774 | Admin Portal: Bulk Apply Issue in Child Data Grids When working in parent-child data grids to which several child grids were configured, if a user performed a modification and used the bulk apply feature in one of the child grid, it was reported that the modification was also applied to the other child grids if they contained the same column. The issue has been corrected; now the modification performed when using the bulk apply operation is only applied to the selected grid as expected. Impact area: Data > Bulk apply | ||
| 38957 | Image Containers Security Update In order to improve the data protection when using the beqom applications, new enhancements have been performed to secure payee and user images loaded in beqom. Impact area: Application security | ||
| 39098 | Mobile Application/Back-End: Missing Data Grid Hierarchy Security Table It was reported that the grid_data_temp_id_payees_for_hierarchy_security table was missing in the beqom Mobile Application database. The issue has been corrected by adding the missing table in the database script. Impact area: None | ||
| 39267 | : Select All Column Mechanism Update in Data Model Properties As of this Hotfix package, the Select All and Select None buttons located in the source properties of a data model have been removed. From now on to select all the available columns to apply to a data model, the All checkbox has been implemented. Impact area: Admin > Select all column in data model source properties | ||
| 39449 | : Parent-Child Data Grid Mapping Issue with Excel Export The following issue was reported in the beqom : when working with a parent-child grid configured with an association between a drop-down list field in the parent grid and a direct value in the child grid, if the user exported the child grid to Excel and added a new row, the mapping field (field on which the association between the parent and the child grid is based) was not added to the new row as expected. The issue has been corrected and now when an association is configured between the parent and the child grid, the correct associated value is added to the linked field when adding a new row in the exported Excel file. Impact area: Data > Parent-child grid mapping | ||
| 39459 | SQL Injection Security Improvement In order to prevent potential malicious SQL injections, the overall security of the beqom applications has been improved. Impact area: Application security | ||
| 39596 | Back-End: Cannot Update View Based on Datasources Using API v2 On the back-end side of the application, it was reported that the modification of datasources based on views using the API v2 was not working as expected. Investigation of the issue reported that only table based datasources could be updated using API v2. The issue has been corrected and now the APIv2 can be used to update view based datasources. Impact area: Application back-end | ||