beqom v10 HF185 - 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: October 17th, 2024
Fix version: v10 - HF 185.3 - DB 10.0.960
| Type | Issue key | Description | |
|---|---|---|---|
| Zendesk | Jira | ||
| BQM-24780 | Application Scale: Migration from .Net6 to .Net8 As part of beqom's effort to continuously improve the TCM v10 application, the .Net framework used in the platform has been migrated from version 6 to version 8, thus bringing more stability and better performance to the product. | ||
| 106389 | Web-App: Default State of the Hierarchy Panel in Process Grids It is now possible, using a dedicated configuration option, to define the default behavior of the hierarchy panel in process grids. The configuration option is located in the Global Settings page of the in Web App, under the Component Settings section, as illustrated in the following figure: Two options are available: Enable : select this option to collapse the hierarchy panel by default when opening a process grid; Disable : select this option to keep the original behavior of the hierarchy panel (i.e. expanded by default) This is an note/information message. The Disable option is selected by default. | ||
| 107483 | Web App: Form Sections not Properly Displayed in Process Grid The following problem was reported in the component of the Web App interface: when working with attached forms in a process grid, if the user entered and saved some values in the form for several payees, and then switched multiple times between forms, the sections displayed in the form were not always correct, especially in the case of a section with conditional visibility. The problem was related to the data saved in the application cache regarding form sections and was corrected. | ||
| 107519 | Web App: Custom View Reset When Opening the Payee Report in Process Grid When working in a process grid, if the user applied a custom view to the grid and then selected a payee in the grid to display the payee report, the custom view was reset or reverted to the previously applied view upon opening the report. Investigation revealed that the problem was due to an incorrect view key applied when opening the report. The issue was corrected; the view is no longer reset when opening the report. | ||
| 109418 | Web App: Read-Only Permission not Correctly Applied to Attached Documents in Data Grids An incorrect behavior of the attach document permissions was observed in the : users who were granted a read-only permission regarding attached documents (i.e. could view attached documents, but not upload any new documents) were still able to attach documents to the grid, which posed a security concern. The issue was corrected and the behavior of the Add Document was adjusted to make sure it is visible only when the user has the appropriate access rights. | ||
| #107928/#112717 Web App: Incorrect Number of Rows in Data Grids The following issue was observed in : when working in grid based on a view, when a sort order was applied and the grid was manually refreshed, the number of records displayed in the pagination tool in the grid toolbar fluctuated after the refresh. The issue was corrected; the number of rows displayed in the pagination tool is now stable for data grids based on views. | |||
| #116723/#117152/#117161 Web App/Admin Portal: Emails not Sent from the Scheduler An issue with the email distribution using Scheduler tasks was reported after the migration to the .Net8 framework: emails did not go out as scheduled. Investigation revealed that the problem was due to a change of SMTP email components between the two versions of the framework (.Net4.7 to .Net8), and specifically to a change of SMTP credential management. The issue was corrected; emails are now sent as expected by the Scheduler service. | |||
Ongoing deployments
| # | Changes | Impact | Comment |
|---|---|---|---|
| BQM-24217 | API changes: New API endpoint POST api/ml/settings DB changes: Changes to catalogDB | This update is related to the Pay Prediction feature flag, which is currently available as a limited release. | This enhancement introduces the possibility for the pay predictor tool administrator to configure which values are displayed in the adjusted prediction card. |
| BQM-24797 | API changes: - DB changes: - | This correction is related to the upgrade from the .Net6 to the .Net8 framework. | As part of the normal testing phase for the .Net framework upgrade, an issue related to the deployment of the application was uncovered and promptly corrected. |
| BQM-24800 | API changes: - DB changes: - | This correction is related to the upgrade from the .Net6 to the .Net8 framework. | As part of the normal testing efforts for the .Net framework upgrade, an issue related to Excel export was discovered; specifically, an extra sheet was added to exported file. The problem was corrected; the export now behaves as expected. |
| BQM-24803 | API changes: - DB changes: - | This correction is related to the upgrade from the .Net6 to the .Net8 framework. | As part of the testing phase for the .Net framework migration, an issue was discovered related to the scheduler feature, where it was no longer possible to define a scheduler event. The problem was corrected and the Scheduler works as expected again. |
| BQM-24808 | API changes: - DB changes: - | This correction is related to the upgrade from the .Net6 to the .Net8 framework. | The body of the response returned by the API endpoint /Population/GetJsonList was incorrect due to a difference of interpretation of null values between the two versions of the framework. |
| BQM-24815 | API changes: - DB changes: - | This correction is related to the upgrade from the .Net6 to the .Net8 framework. | An issue with the creation of teams was raised in the context of the migration to the .Net8 framework. |
| BQM-24824 | API changes: - DB changes: - | This correction is related to the upgrade from the .Net6 to the .Net8 framework. | A few issues were raised after the migration to .Net8: the folder structure for data grids in the DATA component no longer worked, errors appeared when creating a population in Web App and filters could not be applied to data grids in Admin Portal, due to a change in the operation of the trees in the new framework. |
| BQM-24837 | API changes: - DB changes: - | This correction is related to the upgrade from the .Net6 to the .Net8 framework. | The interpretation for null values when it comes to building out tree items in .NET 8 is different (blank arrays are replaced with null), which created issues in most trees in the application. |
| BQM-24853 | API changes: - DB changes: - | This correction is related to the upgrade from the .Net6 to the .Net8 framework. | A null check was missing which led to errors in operational processing processes. |
| BQM-24878 | API changes: - DB changes: - | This correction is related to the upgrade from the .Net6 to the .Net8 framework. | Following the migration to the .Net8 framework, the mentions and the Save and simulate buttons stopped working. This was due to the fact on first synchronization for a process, the imported data source ID was null. The issue was corrected; the system now created a data source with a correct ID. |
| BQM-24879 | API changes: - DB changes: - | This correction is related to the upgrade from the .Net6 to the .Net8 framework. | Following the migration to the .Net8 framework, the execution of rules was no longer possible. |