beqom v10 HF161 - 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 27th, 2024
Fix version: #BeqomApp - v10 - HF 161.5 - DB 10.0.919
| Type | Issue key | Description | |
|---|---|---|---|
| Zendesk | Jira | ||
| BQM-13640 | Web App: Enable Super Admin Users to Access all Advanced Analytics Data Models at Tenant Level In the previous version of the beqom v10, super admin users were able to access only the Advanced Analytics data models created by them or shared to them. From now on, users with the super admin profile will be able to access and manage the entire list of Advanced Analytics data models on tenant level. | ||
| BQM-13641 | Web App: Enable Super Admin Users to Access all Advanced Analytics Reports on Tenant Level In the previous version of the beqom v10, super admin users were able to access only the Advanced Analytics reports created by them or shared to them. From now on, users with the super admin profile will be able to access and manage the entire list of Advanced Analytics reports on tenant level. | ||
| BQM-20787 | Web App: Save Form Button Focus Issue in Attached Forms The following incorrect behavior was reported in the beqom Web App: when working in a form attached to a process grid, as soon as the user clicked outside the form frame, the state of the Save form was immediately changed to disabled even if some modifications were unsaved which was confusing. The problem has been corrected and now the state of the Save form button in attached forms is no longer affected when users change the focus in the application screen. | ||
| BQM-21698 | Web App: Calendar Tool Height Inconsistency in Widget Homepage When working in a widget homepage containing widgets with a date calendar tool, as users were browsing between months to select a date, it was reported that the height of the calendar tool was not fixed and changed according to the number of days of the selected month. The issue has been corrected and now the size of calendar tool in widget homepage is consistent for every selected month. | ||
| BQM-21998 | Back-End: Remove Obsolete Application Packages in DataService On the back-end side of the application, obsolete application packages were removed from DataService to standardize all packages to the same version and infrastructure (v10). This modification has no impact on end-users of the application but will prevent confusion for the development team and clean up the back-end infrastructure. | ||
| BQM-22081 | Web App: Text Overlap in Long Text From Block Type When working in a form attached to a process grid configured with the Allow PDF download feature and with a Long Text block type containing a large amount of characters (displayed on at least two pages), if users downloaded the form, the text in the PDF was overlapping. The issue has been fixed; the content of exported form with large text is correctly displayed in PDF format. | ||
| BQM-22139 | Back-End: Remove PassportClient Dependency In order to prevent any performance and connection risks in Passport and since Passport calls are made directly via APIs, the PassportClient has been removed from RN.PassportProvider . This ticket has no direct impact on end-users of the application and only affects the Passport platform. | ||
| BQM-22972 | Web App: Parent Grid Refresh Issue after Child Grid Update When working in a parent-child data grid, when users opened and performed modifications in the child grid which was affecting the parent grid data, the parent grid was not automatically refreshed as expected and resulted in incorrect data. The issue has been solved; data in parent data grids is now refreshed as expected when a modification affecting the parent grid is performed in the child grid. | ||
| BQM-23014 | Intempestive APIs Calls to the Platform Management Center (PMC) Unnecessary APIs calls to the Platform Management Center (PMC) (beqom's tenant management platform) endpoint were reported which could lead to performance and connection issues. To correct this problem, a mechanism analysing the tenantcode , userid and userprofile from the httpcontext has been introduced to prevent double API calls within the user session. | ||
| BQM-23017 | Back-End: Remove Obsolete Code Related to Conditional Formatting Feature Flag The code related to the Conditional Formatting Feature Flag has been removed from the application back-end because this feature was already released as a standard feature which made the code of the flag obsolete and unused. This ticket has no direct impact on end-users of the application but aims at cleaning the overall application code. | ||
| BQM-23152 | Web App: Cannot Import Modified Process Grid with 0 Precision Decimal Numbers When a user exported a process grid to Excel and modified a value in a drop-down field with a decimal number with 0 after the decimal point (e.g. 23.0), if he attempted to import the grid back into the application, an error was displayed. Investigations of the issue revealed a problem with a cell format of modified decimal values in the excel template was causing the issue. The issue has been solved by fixing the excel template macro file (ExcelTemplate.xlsm) and now users can normally import a modified grid with 0 precision decimal numbers back into the application. | ||
| BQM-23238 | Back-End: Enable App Insights to Send Telemetry Info to Web Application When deploying the new OpenTelemetry logging mechanism, it was reported that telemetry information were missing from RN.Service and RN.WebUI in the App Insights. In order to collect the required information, the telemetry information are now accessible in the App Insights which will significantly help optimizing performance and troubleshoot issues. | ||
| BQM-23300 | Back-End: Incorrect Error for Unauthenticated Access to Analytics Service On the back-end side of the application, it was reported that when an unauthenticated access to the Analytics service was detected, the error returned was incorrect (HTTP 500 error instead of HTTP 401). The problem has been solved; the code for authenticated access to analytics has been changed and now if an unauthenticated access is detected the correct error messages is returned informing about invalid authentication information. | ||
| BQM-23327 | Back-End: Implement "ESLint" and "Prettier" Tools to Web App Configuration In order to improve the overall code quality in the beqom v10, the ESLint and Prettier tools have been integrated into the application configuration. These new tools will help detect any defect and obsolete code as well as providing a file standardization for the development team using the WDIO Project Repository . | ||
| BQM-23639 | Web App: Incorrect Advanced Analytics Report Status after Share The following problem was noticed in the beqom Web App: when a user with a super admin profile shared an Advanced Analytics report, the status of the report was still set as "private" for himself but correctly set as "shared" for the users to which the report was shared. The problem has been solved; the status of shared Advanced Analytics reports is correctly set to "shared" for super admin users. | ||
| BQM-23659 | Back-End: Impossibility to Access API Endpoints due to Session Creation Issue The following issue was reported on the back-end side of the application: if the JWT token was not logged in through the application, the session could not be created which was preventing the access to some API endpoints. The problem has been fixed and now the session is created based on a context identifier request. | ||
| BQM-23769 | Web App: Issue with Widgets Drill Downs in Advanced Analytics Reports The following problem was observed in the beqom Web App: when working in an Advanced Analytics report configured with widgets with drill downs to link a specific report to a value in the widget, when a user attempted to open a linked report by right-clicking a value in a widget, the application returned an error or a blank screen. The issue has been corrected; users can now normally open reports linked to widget values inside Advanced Analytics reports. | ||
| In this Release Note | |||