beqom v10 HF41 - 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: March 24th, 2021
Fix version: 10 - 42746 - 10.0.437 - BeqomApp.Gateway_10_46293 - BeqomApp.WebApp_10_46305
| Type | Issue key | Description | |
|---|---|---|---|
| Zendesk | Jira | ||
| 38696 | Web Application: Attached Report Resize Issue in Process Grids The following incorrect behavior was reported in the beqom Web Application: when working in process grids to which a report was attached, if users opened the report, increased its size, and then collapsed the hierarchy tree panel, the report window moved to the bottom of the screen. The issue has been corrected; now the size of the attached report window is saved after closing the hierarchy tree panel. Impact area: Process > Attached report size | ||
| 40325 | Web Application: Cascading Association Issue in Parent-Child Data Grids When working in a parent-child data grid in which cascading fields were configured on a drop-down column, if users applied a filter based on that column in the child grid, it was reported that the values were not correctly filtered because values from the parent grid column could be used. The issue has been corrected; now the values of cascading fields are correctly filtered in the child grid . Impact area: Data > Filter on cascading fields | ||
| 40671 | Admin Portal: Cannot Edit a New Hierarchy Admin users were not able to modify an existing hierarchy via > Administration > Hierarchies in the beqom Admin Portal because when they clicked the Edit button, the application displayed a blank page. This issue was related to the deprecation of the PEOPLE component from the beqom Admin Portal. The issue has been corrected by removing the Edit button as well as the Preview button accessible when clicking a hierarchy in the "Hierarchies" tab. Impact area: Organization > Hierarchies tab | ||
| 40672 | Web Application: Missing Indicator for Applied Filter in Standards Reports The following incorrect behavior was reported when working in the in the beqom Web Application: when a standard report was configured with a "Multi selection drop-down tree" type filter, if some of the filters were apply to the report, the "tick" symbols indicating that the filters were applied were missing when opening the filter panel. It was revealed that this issue was caused by a styling conflict in the Web Application. The issue has been corrected; now the applied filters always appear with their boxes checked in the filter panel. Impact area: Analysis > Applied filter indicator display | ||
| 40675 | Web Application: Incorrect Default Time in DateTime Field Type The following issue was noticed in the beqom Web Application: when a data grid was created with a column containing the DateTime data type, when users chose a date for this field, the default time displayed was the current time which was not correct. The issue has been corrected; now the default time for DateTime field is 12:00 am. Impact area: Data > DateTime field default format | ||
| 41003 | Web Application: Removed Field and Custom Views Issue in Process Grids When an indicator field was removed from a process grid although users had previously saved custom views containing this field, the field still appeared when users loaded the custom views which was not correct. The issue has been corrected; now if a field is removed from a process grid, it is automatically removed from all previously configured custom views. Impact area: Process > Custom views | ||
| 41035 | Cannot Access Swagger Interface It was reported that some HTTP 500 errors were experienced when accessing the Swagger interface. The issue has been corrected; now the Swagger interface can be accessed as expected. Impact area: None | ||
| 41040 | Web Application: Cannot Publish Form Containing Information Field Block The following issue was noticed in the beqom Web Application: when users created a form containing an information field block, after they assigned the form to a process and clicked Publish , the form was not published as expected and the error message "Cannot publish form without element" returned by the Web browser console. The issue has been corrected; now forms containing an information field block can be published as expected. Impact area: Forms > Form with information field block publication | ||
| 41225 | Admin Portal: Workflow Step Validation Issue The following issue was reported in the beqom Admin Portal: when working in a process grid with a workflow in which an indicator field was configured with "SQL Field" as the default value type, if a filter was applied to the grid based on that field, users were not able to validate a workflow step for a given payee because the application returned an error. This error occurred because the workflow validation was not managed if the process grid was filtered using fields with "SQL Field" as default value type. The issue has been corrected; now workflow steps can be properly validated when a filter with "SQL Field" as the default value type is applied to the grid. Impact area: Process > Workflow step validation | ||
| 41314 | Web Application: Unexpected Additional Columns in Exported Data Grids The following issue was reported when working in the beqom : when users exported data grids containing associated fields with drop-down lists, additional column with data but no headers were added in the Excel file. Investigations revealed that the issue was related to a configuration problem with column associations. The issue has been corrected; empty columns are no longer added after exporting data grids with drop-downs to Excel. Impact area: Data > Grid export | ||
| 41391 | Admin Portal: Incorrect Event End Date in Scheduler The following issue was noticed when working in the beqom Admin Portal: when an event was created in the Scheduler tool, if the user chose an end date for this event and saved, it occurred that the application was saving the day before the chosen date. The issue was related to a conflict with the local time zone on the users machine. The issue has been corrected; now the Scheduler tool always take into account the user local time zone when selecting an end date for an event. Impact area: Admin > Scheduled event end date | ||