beqom v10 HF60 - 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: August 18th, 2021
Fix version: 10 - 43759 - 10.0.536 - Release-BeqomApp-v10-Package-HF60.2 - BeqomApp.WebApp_10_53045
| Type | Issue key | Description | |
|---|---|---|---|
| Zendesk | Jira | ||
| 44504 | Web Application: Incorrect Behavior of Process Security with Workflow Override When some nodes in a hierarchy security were configured to use the worklfow override, the behavior of the other nodes was not following their configuration (read-only instead of read/write, for instance). Investigation of the issue revealed that the Web Application did not fetch the correct workflow for the selected hierarchy node du to an incorrect parameter sent to the application back-end (idTreeSecurity). The issue was corrected and the application now uses the correct workflow behavior. Impact area: Process > Hierarchy security | ||
| 45026 | Web Application: Incorrect Values Written when Using RTC When the real-time calculation was configured to be used in a process and the user made manual changes to a field impacted by the RTC (effectively overriding the RTC), the application still saved the value calculated by the real-time calculation in the database. The problem has been corrected; the application now saves in the database the actual value visible in the process grid. Impact area: Process > Real-time calculation | ||
| 46249 | Web Application: Cannot Check the last Checkbox Displayed on Screen in a Data Grid When working in a data grid with boolean fields (checkboxes), if the user attempted to check/uncheck a box in the last row displayed on screen, they could properly click, but the state of the box was not changed. Investigation revealed that the issue was related to the zoom applied to the browser. If the user changed the zoom, the focus of the cursor was not correctly applied. The problem has been corrected by the changing the styles applied to the page Impact area: Data > Page styles | ||
| 46254 | Back-End: Remove Legacy Logger Database Configurations Two database configurations related to the application's legacy logging system were still present. These configurations have been removed from the application code. Impact area: None | ||
| 46569 | Web Application: One-Click Profile Switch with Deep Links A new feature has been implemented in the beqom Web Application. It is now possible to configure deep links in the application that will trigger a profile change for the user, thus eliminating the need to perform several clicks for users who have access to processes with several different profiles. This is an note/information message. This feature will be fully documented in the beqom Knowledge Base. Impact area: Profile switch | ||
| 46746 | Admin Portal: Incorrect Behavior of Drop-Down Lists The following behavior was observed regarding drop-down lists in the of the beqom Admin Portal interface: when a default value was defined in a drop-down list, the user needed to click twice to expand the drop-down list; the list closed back after the first click. The problem was related to ExtJS and was corrected. Impact area: Analysis > Drop-down lists (all types) | ||
| 47378 | Web Application: Configuration of the Real-Time Calculation Timeout As of this package, a new parameter, called Real-Time Calculation Timeout on Save (in Seconds), is available in the , under Components > Process to define the duration of the RTC timeout. This parameter, enables system administrators to define the duration for which the application waits for real-time calculations to finish before saving (if the user clicks Save before the RTC has finished running). DB update 10.0.536 required This is an note/information message. This feature will be fully documented in the beqom Knowledge Base. Impact area: Admin > Process configuration | ||
| 47475 | Web Application: Environment Manager Inoperative The environment manager feature was inoperative in the Web Application interface. When attempting to migrate objects from an environment to another, an error was thrown and the operation was not performed. The issue was related to a behavior of the environment manager: it expected a specific response after the deployment that was not actually returned. To correct the problem, the environment manager has been modified and no longer expects a specific response. Impact area: Admin > Environment manager | ||