beqom v10 HF82 - 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: January 26th, 2022
Fix version: v10 - 60730 - 10.0.663 - 82.2 - 60726
| Type | Issue key | Description | |
|---|---|---|---|
| Zendesk | Jira | ||
| 51892 | Web App: Issue with HTML4 Tags in Reports The following issue was reported in the beqom Admin Portal: users could not save reports containing certain HTML4 tags in reports. Investigation of the issue uncovered two problems: certain HTML tags were not allowed by the HTML Sanitization Library. In addition, the SQL injection check layer was causing some performance issues. Both issues have been corrected and the relevant reports can be correctly saved and used. WCF service Impact area: All HTML areas across the application | ||
| 53263 | Web App: Quick Refresh Inoperative in Process Grids The following issue was reported in the beqom : when users attempted to use the quick refresh feature in process grids, the application returned an error. Investigations revealed that the issue occurred because of a unnecessary call to form data. The issue has been corrected by removing unnecessary calls and replacing them by a relation call to attached objects. The quick refresh feature is now working as normal in process grids. Impact area: Process > Quick refresh | ||
| 54143 | Web App: Unexpected Aggregation Call in Process Grids When working in process grids in which no aggregations were configured, it was reported that the method used to call aggregated values was still executed, which was incorrect. The issue has been corrected; the method used to call aggregated values is no longer executed in process grids without any aggregation configured. Impact area: Process > Aggregations method call | ||
| 54381 | Mobile App: New Expand and Collapse Icons in Forms Header In order to improve the user experience when working with the beqom Mobile Application, two new indicators have been added to forms header to better notice when the form is expanded and when the form is collapsed. Impact area: Home and Profile > Forms header | ||
| 54384 | Mobile App: Performance Improvements In order to improve the overall performance of the beqom Mobile Application, especially when working with large amount of data, new indexes have been added on the database level. DB: new [idx_k_mobile_kpi_id_dashboard_id_period_id_payee] to index the dashboard, period and payee fields for the table k_mobile_kpi ; new [idx_k_mobile_dashboard_id_owner] to index the id_owner of the table k_mobile_dashboard ; new [idx_k_mobile_kpi_modifier_state_id_kpi] to index the id_kpi of the table k_mobile_kpi_modifier and new [idx_k_mobile_kpi_payout_curve_group_id_kpi] to index the id_kpi of the table k_mobile_kpi_payout_curve_group Impact area: Application performances | ||
| 54388 | Web App: Attached Reports Unexpectedly Refreshed when Using Several Budget Widgets in Process The following issue was reported in the Web Application interface of the beqom application: when several process budget widgets were used in a single process grids, when users switched widgets with an attached process report open, then the report was unexpectedly refreshed. The problem has been corrected by changing the budget widget switching logic. Impact area: Process > Attached reports | ||
| 54416 | Web App: Incorrect Placement of the Bottom Toolbar in Analysis The following issue was observed in the of the Web App interface of the application: the toolbar located at the bottom of the "Advanced Analytics" section was located on the right side of center panel instead of on the left side. The placement of the toolbar has been modified back into the correct location. Impact area: Analysis > Toolbar placement in the "Advanced Analytics" section | ||
| In this Release Note | |||
| #53828/#54201 Web App: Incorrect Data Loading with Level Filter in Process Grids When working in a process grid configured with the L-1 level filter, if users applied all level filters to the grid, navigated to another component and opened the previous grid again, it was noticed that the application either returned the error "No rows to display" or only the data from the L-1 level filter. The issue has been corrected; now the correct data are displayed after applying a level filter to a grid and reloading the grid again. Impact area: Process > Level filter data loading | |||