beqom v10 HF102 - 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: June 29th, 2022
Fix version: v10 - 81354 - 10.0.731 - 102.3 - 81041
| Type | Issue key | Description | |
|---|---|---|---|
| Zendesk | Jira | ||
| 51943 | Admin Portal/Web App: Unexpected Timeout Error in SSRS Reports The following issue was reported in the beqom Admin Portal and in the Web App: when users opened an SSRS report, after five minutes of inactivity, an unexpected timeout error was returned by the application. Investigations revealed that this problem occurred because the parameter responsible for keeping the session alive in the Report Viewer had been disabled. The issue has been corrected by enabling the parameter again and now timeout errors are no longer experienced by users after a few minutes of inactivity while working in SSRS reports. Impact area: Analysis and Analysis > SSRS report timeout | ||
| 57130 | Web App: Missing Soft Conditional Validation Error After Process Grids Export/Import The following issue was reported in the beqom Web App: if a process grid configured with a soft conditional validation (e.g. the numeric field should be less than 1000) and a hard conditional validation (e.g. the field cannot be empty) and with associated warning messages was exported to Excel, if users entered values in Excel which triggered both errors, and then imported the grid back into the application, the list of errors returned in the "Import Errors" window was incomplete because the soft validation errors were missing. The issue has been corrected; now all the configured errors messages are displayed if validation conditions are not met after importing a process grid into the beqom Web App. Impact area: Process > Soft conditional validation error message display | ||
| 63191 | Web App: Visibility and Validation Rule Configuration Issues in Forms In the beqom Web App, if users created a new form with a block type with the "required" option and a visibility rule on a specific profile, after they selected a profile and clicked out the field, the profile unexpectedly disappeared form the field. Moreover, if users configured a form block type with a validation rule, the rule was inoperative when the form was published. Both issues have been corrected and now the configuration and the use of visibility and validation rules are working as expected in forms. Impact area: Forms > Form configuration | ||
| 63281 | Back-End: Logs Errors in Data Grids with "Allow Track Changes" Parameter Disabled On the back-end side of the application, logs errors were reported in the Application Insights in the following case: if users applied modifications in a data grid and saved, if for some reasons the saving process failed (incorrect value in the field for example), even if the grid was not configured with the Allow Track Changes parameter (in "DATA" > Administration > Grid Editor), the history table responsible to track the changes in the grid was unexpectedly updated. The issue has been corrected; now if a data grid is not configured with the Allow Track Changes parameter, the history table is not updated as expected and thus errors are no longer experienced in the Application Insights. Impact area: Application back-end | ||
| 63810 | Admin Portal: Filters Inoperative in Process Grids Visibility Setup Section When users with the correct permissions opened a process grid visibility section via > "Any Grid" > Setup > Visibility > Visibility Permission in the beqom Admin Portal, if they attempted to filter the list of available profiles or columns, it was observed that only the "contains" filter was operative. The issue has been corrected; now users can correctly filter the list of available profiles and columns in a grid visibility setup section with all the available filters. Impact area: Design > Filters in visibility setup section | ||
| 64004 | Back-End: Exception Logged by Application Insights for Every 401 Errors from Red Nimbus On the back-end side of the application, Application Insights exceptions were reported each time a 401 error was returned from Red Nimbus. The issue has been corrected by introducing a telemetry processor to filter unauthorized exceptions and thus make the logs on application insights more readable and understandable. Impact area: Application back-end | ||
| 64005 | Back-End: Irrelevant Telemetry Logged by Application Insights to RN.Service and RN.WebUI On the back-end side of the application, it was reported that Application Insights logged telemetry that is irrelevant to RN.Service and RN.WebUI. The issue has been corrected by introducing a telemetry processor to filter unwanted traffic telemetry and thus make the logs on Application Insights more readable and understandable. Impact area: Application back-end | ||
| 64287 | Web App/Back-End: Conflict Between Object Service and Feature Flags Page Access The following issue was reported in the beqom Web App: if the object service was not correctly operating on the back-end side of the application, the access to the Feature Flags page in the Web App was not accessible. The issue has been corrected; now the Feature Flags page is accessible as expected even if the object service is not operative. Impact area: Admin > Feature Flags page access | ||
| 64627 | Mobile App: Support Cumulative KPIs As of this hotfix package, team and personal dashboards in the beqom Mobile App can now be configured with cumulative KPIs. This type of KPI has been introduced in order to calculate the global payout of a payee based on the achievement of his objectives (underachieved or overachieved) over several periods of time. DB: added is_cumulative parameter in k_mobile_kpi_definition table Impact area: Home > KPIs in personal and team dashboards | ||
| 64638 | Localization Update The rps_localization table has been updated in order to make sure that the beqom application is fully localized. Update to the rps_localization table Impact area: None | ||
| In this Release Note | |||