beqom v10 HF19 - 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: September 23rd, 2020
Fix version: 41337 - 10.0.226 - BeqomApp.Gateway_10_36238 - BeqomApp.WebApp_10_36344
| Type | Issue key | Description | |
|---|---|---|---|
| Zendesk | Jira | ||
| 30804 | Admin Portal: Child Data Grid Import Issue The following issue was reported in the beqom Admin Portal: when working with a parent-child data grid, if users exported the data of the child grid to Excel, and then imported it back to the application without having performed any modification, the error message "Batch Update" was displayed. The issue has been corrected; now users can correctly import a child data grid without having previously performed any modification. Impact area: Data > Child grid import | ||
| 31069 | Web App: Data Display Issue After Save in Data Grids The following incorrect behavior was reported in the beqom Web Application: when working in data grids configured with data security on a drop-down list, if an unauthorized user attempted to add a row to the grid, then saved, the application returned the error “Access Denied” as expected, but the data of the list field column were no longer displayed after the operation. Refreshing the grid would return the grid to the expected display (new row deleted, all relevant data displayed) The issue has been corrected; now when unauthorized users attempt to modify values in a data grid, they receive an error as expected, but there is no longer any impact on the data. Impact area: Data > Data security | ||
| 31641 | Web App: Cannot Delete Logo When users with admin profile attempted to delete the current logos used in the beqom Web Application, the error "An error occurred. Please contact the administrator" was displayed. The issue has been corrected by allowing the Read permission for Settings Management for admin profiles via the beqom Admin Portal. Impact area: Admin > Delete application logos | ||
| 31642 | Web App: DocuSign Data Saving Issue The following issue was noticed in the beqom Web Application: when admin users entered the data related to the DocuSign integration in Admin > Integrations > DocuSign section, if users reloaded the page or logged out of the application, the data were not saved as expected. After investigation, it was revealed that the issue was due to the incorrect update of the DocuSign parameters in the k_parameters table. The issue was corrected; now the data entered by admin users in the DocuSign integration section are automatically saved. Impact area: Admin > DocuSign integration | ||
| 31855 | Connection Issue Between RabbitMQ and beqom The following issue was reported in the beqom application: when RabbitMQ was subjected to connection failures, object and data services were impacted and caused the application to crash. The issue has been corrected; now the beqom application is running properly in the case RabbitMQ encounters connection failures. Impact area: Application connection | ||
| 31859 | Redis Retry Connection Policy Implementation In order to enable a retry connection policy in the case the RN service failed to connect to the Redis cache server, several modifications have been performed on the back-end side of the application. The two following parameters have been added to the RN service: ReconnectRetryPolicy: name of the retry connection policy; ReconnectRetryTime: time in milliseconds for the back-off interval between each retry connection (default: 5000ms) In addition, the following modifications have been performed to the Redis connection string in the database: abortConnect: set to false; connectRetry: number of allowed connection attempts (default: 3); connectTimeout: connection operation timeout in milliseconds (default: 5000ms) Impact area: Application back-end | ||
| 32007 | SonarQube Services Update In order to improve the security and the performance when using beqom Advanced Analytics objects, the following fixes have been performed to the SonarQube services: Fields should not have public accessibility; Mutable fields should not be "public static"; Generic exceptions should not be ignored Impact area: Application security | ||
| 32020 | Web App: Save Without Refresh Feature Implementation As of this Hotfix package, the Save Without Refresh feature has been implemented in process grids in the beqom Web Application. When configured, the Save Without Refresh button will enable users to save a process grid without having its data refreshed. This is an note/information message. The configuration of this feature will shortly be documented in an FAQ article (beqom Knowledge Base). Impact area: Process > Save without refresh | ||
| 32026 | Admin Portal: Cannot Delete Hierarchy Security An issue was reported when managing hierarchy security in the beqom Admin Portal: when users with the correct permissions attempted to delete a hierarchy security which had a reference to the k_tree_security_payee_access table, the application returned an execution error. The issue has been corrected; users are now able to correctly delete a hierarchy security with a reference to the k_tree_security_payee_access table. Impact area: Organization > Delete hierarchy security | ||
| 32101 | Web App: Performance Improvement In order to improve the performances and the user experience when working with process grids in the beqom Web Application, the following modifications have been performed: Enable the display of process grids containing more than 20 columns and 50 rows; Virtualization introduction; Typescript introduction; Column management improvement; Fix column header sorting; Summary row display improvement; Enable hyperlinks in process grid cells; Remove typeahead feature from process grid cells Impact area: Process | ||
| 32123 | Web App: Process Grid Loading Issue After Successive Actions The following issue was noticed when working with process grids in the beqom Web Application: if a user clicked a payee in the hierarchy tree and immediately clicked a second payee, the record for that payee was not displayed and the spinning wheel endlessly remained on the screen. The issue has been corrected and now if a user successively click on several payees in the hierarchy tree, the process loads as expected. Impact area: Process > Grid loading | ||