beqom v10 HF139 - 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: July 26th, 2023
Fix version: v10 - 144627 - 10.0.840 - 139.3 - 143409
| Type | Issue key | Description | |
|---|---|---|---|
| Zendesk | Jira | ||
| BQM-19990 | Admin Portal/Web App: Hierarchy Exclusion Issue in Process Grids The following incorrect behavior was reported in the beqom Admin Portal and in the Web App: when working in a process grid configured with a population with a specific hierarchy security applied, users could search payees which were excluded from the hierarchy. The issue has been corrected and node exclusions in hierarchy are working as expected. Impact area: Process > Hierarchy node exclusion | ||
| BQM-20929 | Web App: Infinite Loading Screen in Form Preview When working with forms in the beqom Web App, if users opened the Preview tab of a form, the application returned an infinite loading screen. The issue has been corrected and now users can normally access the Preview tab of any form. Impact area: Forms > Preview tab display | ||
| BQM-20954 | Web App: Attached Forms Content Display Issue The following issue was reported in the Web App: sometimes when users opened an attached form in a process grid, the data of the form was not correctly rendered and something the form fields were missing. The issue has been corrected and now the data and fields in attached forms are correctly displayed. Impact area: Process > Attached forms content display | ||
| BQM-21109 | Web App: Cannot Click Export Button After Collapsing Data and Process Grid Hierarchy Panel When working in a process or a data grid, if a user collapsed the hierarchy panel and then scrolled down the grid, a blank space appeared at the bottom of the grid which prevented to click the Export button. The issue has been corrected; the blank space is no longer visible at the bottom of a grid after users collapse the hierarchy panel and thus the Export button is operational. Impact area: Process and Data > Access to Export button | ||
| BQM-21236 | Web App: Missing Localization for Accessibility Keys The rps_localization table has been updated in order to make sure that the beqom application is fully localized. Update to rps_localization table Impact area: None | ||
| 81874 | Back-End: Database Performance Issue On the back-end side of the application, performance issues were reported in the catalog database regarding API execution and data loading. After the correct fix has been applied, the performances issues are no longer experienced in the catalog database. Impact area: Application back-end | ||
| 87469 | Web App: Conditional Validation Warning Message Visible when Disabled in the Data Grid Configuration The following issue was reported in the beqom Web App: if the Show warning message parameter for a conditional validation was disabled in a data grid configuration in the Admin Portal ( Grid Editor tab), a warning message was still displayed when users entered an incorrect value in a data grid field configured with the condition. The issue has been corrected; now if the warning message for a conditional validation is disabled in the Admin Portal, the warning will not appear in the Web App as expected. Impact area: Data > Conditional validation warning message | ||
| 88117 | Web App: Incorrect Profile ID when Switching Profiles The following issue was reported in the Web App: if a user had two profiles assigned with hierarchy security configured on both, when he switched from profile one to profile two, the incorrect profile identifier was saved by the application. The issue has been corrected and now the correct identifier is saved when switching profile in the Web App. Impact area: Process > Profile identifier | ||
| #84262/#84526 Web App: Date Format Issue in Attached Forms The following issue was observed in the beqom Web App: when users created a form with a date block type, if the form was attached to a process grid and published, the date format when a date was selected was different than the one configured in the application settings. Investigation of the issue revealed that the problem occurred because the application was using the user's local timezone to display the date. The issue has been solved; now the date format is displayed according to the configured timezone as expected in forms attached to process. Impact area: Process > Date format in attached forms | |||
| In this Release Note | |||
Ongoing deployments
The following improvements are being deployed progressively:
| Type | Issue key | Description | |
|---|---|---|---|
| Zendesk | Jira | ||
| BQM-19499 | Back-End: Code Refactoring In order to improve the overall code quality and prevent any security breach, the code related to the management of documents has been refactored. Impact area: Application back-end | ||
| BQM-19591 | Web App: Improve Screen Readability on Buttons in Several Areas As of part the Accessibility Compliance program, in order to improve the user experience when using screen reader applications, metadata information have been added on buttons and action items in following areas of the application: : delete rule, delete group, collapse group, expand group, delete block, copy block, edit block settings, delete element, drag and move group; Data and process grids: refresh grid, click to choose filter; : click to collapse hierarchy explorer and click to expand hierarchy explorer; : click to expand simulation overview panel and click to collapse simulation overview panel; : click to expand populations overview panel and click to collapse populations overview panel; : click to expand folder tree overview panel and click to collapse folder tree overview panel; : click to expand rules tree overview panel and click to collapse rules tree overview panel; : click to expand analysis tree overview panel and click to collapse analysis tree overview panel Impact area: Buttons and action items mentioned above | ||
| BQM-20759 | Back-End: New API to Retrieve Documents Identifiers In order to correctly retrieve documents identifiers based in documents' titles and prevent any identifiers mismatch, a new API endpoint is now used: api/Notification/GetUserDocumentIdByTitle . Impact area: Application back-end | ||
| BQM-20998 | Front-End: New Global Mock File to Use in Unit Tests In order to improve unit testing on the front-end side of the application, a global mock file has been created, which will also prevent mock duplication. Impact area: None | ||