beqom v10 HF45 - 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: April 21st, 2021
Fix version: 10 - 42960 - 10.0.477 - BeqomApp.Gateway_10_46756 - BeqomApp.WebApp_10_47783
| Type | Issue key | Description | |
|---|---|---|---|
| Zendesk | Jira | ||
| 41043 | Web Application: Performance Issue in process grids with Custom Views Some performance issues were reported when users switched from a custom view to another in process grids. Investigations revealed that these performance issues occurred because the current method used to fetch the different users' views was calling separate requests to the database instead of one to fetch all the views at once. The issue has been corrected and now performance issues are no longer experienced by users when switching custom views in process grids. Impact area: Process > Custom views loading | ||
| 41315 | Web Application: Payees Display Issue in Process Grids The following issue was reported in the beqom Web Application: when a user clicked a manager node in a process grid, if he accessed any payee in the hierarchy, performed a sort operation on any column, and then opened the same manager node again, the application returned the screen "No Payees to Display". The issue occurred because of a conflict with the "Manager only" configuration when switching from a manager node to a payee in the hierarchy tree. The issue has been corrected and now payees are correctly displayed in process grids when switching from a manager to a payee. Impact area: Process > Payees display | ||
| 41318 | Admin Portal: Cannot Remove Columns from data grids with a Custom View The following incorrect behavior was reported in the beqom Web Application: when an admin user created a custom view in a data grid, if he switched to the beqom Admin Portal and attempted to remove a column from that grid via > Administration > Grid Editor, the application returned the error "could not execute batch command.[SQL: SQL not available]". The issue has been corrected and now admin users can remove, as expected, columns from a data grid in which a custom view was configured. Impact area: Data > Data grids with a custom view | ||
| 41613 | Admin Portal/Web Application: Drop-Down Lists with Cascading Association Issue in Data Grids The following issue was noticed in the beqom Admin Portal and in the Web Application: when working in data grids configured with drop-down lists with cascading associations between two columns, after the user selected a value in a field in the first column and a second value linked to the first field in the second column, if they saved the modification the association was not done correctly because the value from the first field was not associated to the second field as expected. It was revealed that a mapping issue was causing the incorrect label display. The issue has been corrected; now values configured with cascading associations on drop-downs are associated as expected in data grids. Impact area: Data and Data > Grid with cascading associations on drop-down | ||
| 41875 | Admin Portal: Empty List in the Communication Workbench Section When working in the beqom Admin Portal, even if the user's profile was granted with the correct rights to access the Communication Workbench section in the , he could not access any of the folders (Notification, Task, Document and Report) because the section was empty. The issue occurred because the "title" column of the tables related to the Communication Workbench section were empty on the database side of the application. The issue has been corrected by setting the "title" columns of the related tables to NOT NULL and not users with the correct permissions have always access to the Communication Workbench folders. Impact area: InfoHub > Communication Workbench folders access | ||
| 42221 | Admin Portal: Prevent SQL Injection in Process In order to prevent potential malicious SQL injection in the beqom Admin Portal, the security of the methods used when setting security configuration in the and the have been enforced. Impact area: Application security | ||
| 42392 | Web Application: Cannot Open Individual Planner It was reported that users were not able to access the individual planner in the Web Application. The issue was due to a missing XML file in individual planner service in Swagger. The issue has been corrected; now users can open the individual planner as expected. Impact area: CompPlan > Access to individual planner | ||