beqom v10 HF113 - 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: September 14th, 2022
Fix version: v10 - 93839 - 10.0.762 - 113.4 - 93651
| Type | Issue key | Description | |
|---|---|---|---|
| Zendesk | Jira | ||
| 64131 | Web App/Admin Portal: Incorrect Results After Workflow Step Validation/Invalidation with Missing Permissions The following issue was reported in the beqom Admin Portal and in the Web App: if a user without the correct permissions granted to his profile submitted or revoked one of the workflow step for some employees in a process grid, the application returned the incorrect number of unmodified rows due to missing permissions in the Validation Results or Invalidation Results contextual window. Indeed, the number of unmodified rows was always higher than the actual number of selected rows. The issue has been solved and now the correct number of unmodified rows is displayed in the contextual window when a user without the correct permissions granted to his profile attempts to submit or revoke payee records to a next or previous workflow step. Impact area: Process and Process > Workflow step validation/invalidation results | ||
| 65949 | Admin Portal: Cannot Delete Data Grids with Default View Applied in Web App The following incorrect behavior was noticed in the beqom Admin Portal: if a user created and applied a custom view to a data grid in the Web App, and then switched to the Admin Portal and attempted to delete the grid, the application returned an error. The issue has been corrected and now users can normally delete data grids in the Admin Portal to which a view was applied in the Web App. Impact area: Data > Data grid deletion | ||
| 66664 | Admin Portal: Business Objects Creation Issue The following incorrect behavior was reported when working in the beqom Admin Portal: when admin users created a new object without any parameters in a business universe configuration page and without saving, the object was unexpectedly saved in the database with empty fields. Moreover, if users accessed the and attempted to select the previously created object, the application returned an error. The issue has been corrected and now if a business object is created in a business universe configuration page, the object is no longer saved in the database if the object is not saved in the application. Impact area: Admin > Business object creation | ||
| 66838 | Web App: Quick Filter "Contains" Operator Inoperative on Drop-Down Columns in Data Grids When working in a data grid in the beqom Web App, if a user attempted to use the quick filter feature with the "contains" operator on a drop-down list column, if the entered value led to multiple results, when the user pressed the Enter key on his keyboard, the application only displayed the first result of the list and not all the results containing the entered value as expected. The problem has been solved and now the quick filter "contains" operator is working as expected on drop-down list columns in data grids. Impact area: Data > Quick filter "contains" operator | ||
| 67025 | Admin Portal: Missing Extension After Auto Generated PDF Files Download The following incorrect behavior was observed in the beqom Admin Portal: when users downloaded auto generated files in PDF format from the application, the file extension was not added at the end of the document and the document was thus downloaded as a text file. The issue has been corrected and now the PDF extension is correctly recognized when users download auto generated files in PDF format from the Admin Portal. Impact area: InfoHub > Auto generated files download in PDF format | ||
| 67548 | Web App: New Information Message in Case of Feature Flag API Outage As of this hotfix package and in the case of an outage of the Feature Flag management API, the following message will now be displayed when admin users attempt to access the Feature Flags section in the : "For technical reasons, the list of Feature Flags is currently unavailable. All enabled features are working correctly. Please try and refresh this page later.". Impact area: Admin > Message when Feature Flags section inaccessible | ||
| 68374 | Back-End: Comp Planner Service Security Update In order to improve the security of the Comp Planner service, the framework and libraries version used for that component has been upgraded. Impact area: Application security | ||
| 68431 | Back-End: Improve Feature Flag Activation Mechanisms In order to prevent endless loading activation time when the Object Service is interrupted while a Feature flag migration process is performed, new mechanisms have been introduced to better track and analyze the Feature Flag activation phase. Impact area: Application back-end | ||
| 68533 | Web App: Cannot Activate "Teams" Feature Flag The following issue was reported in the Web App if the "Teams" Feature Flag was configured in the beqom environment: if admins users attempted to activate the "Teams" Feature Flag by toggling the button in the Feature Flags page of the , the feature was not available in the application as expected and was not activated in the Feature Flag management tool. The issue has been corrected and now, when the environment is correctly configured, admins users can activate the "Teams" Feature Flag. Impact area: Admin > "Teams" Feature Flag activation | ||
| 68610 | Web App/Back-End: Admin and User Components Performance Improvement In order to improve the performance when working in the and , new code has been integrated into the application to split the JavaScript bundles and thus only download the required files when accessing both components. Impact area: Application performance | ||
| 68759 | Localization Update In order to make sure that the beqom application is properly localized in all supported languages, the rps_localization table has been updated with all latest translations. DB: Updated rps_localization table | ||
| #68219/#68588 Web App: Cannot Add Conditional Formatting Rules on Columns Without Default View When working in the Web App, users were not able to apply any conditional formatting rules on a column which was not included in the "default view" schema configured in the Admin Portal. The issue has been corrected; now the creation of conditional formatting rules is working properly for columns which are not included in the "default view" schema. Impact area: Process > Conditional formatting on columns not included in default view | |||
| In this Release Note | |||