beqom v10 HF219 - Release notes
Fix version: v10 - HF219.16 - DB 10.0.1031
| Type | Reference | Description | |
|---|---|---|---|
| Zendesk | Jira | ||
| BQM-20528 | In the "PROCESS" component, a fallback mechanism was implemented for the Real-Time Calculation (RTC) engine, to handle scenarios where WebSocket connections are unavailable or fail to establish. The system now automatically unblocks the row and displays an error instead of remaining blocked indefinitely. | ||
| BQM-25856 | In the "Data" component, the Last 10 Grids Used tool was enhanced to display localized grid names, if any. | ||
| BQM-26019 | The logging level on the k_stats table was enhanced to capture object names, method names, and external SSO IDs this helping improve troubleshooting and incident response. | ||
| 133942 | BQM-26107 | In the Data Integration API, the generic error messages returned when invalid characters are present in JSON data were improved by enhancing error handling to identify and display the specific problematic field(s). | |
| 119472 136234 | BQM-26108 | In the Environment Manager, the rule synchronization API (api/Rule/SynchronizeRules) experienced performance issues and timeouts when environments contained a large number of configured rules. The underlying SQL query generated excessive parameters (1700+), causing slow performance. The query was optimized to handle large rule sets efficiently without parameter limitations. | |
| 136971 137427 | BQM-26319 | An issue was identified where the dimensions and measures of Advanced Analytics endpoints were blocked by an incorrect regular expression introduced after an update. The regular expression was updated to correctly allow access to these endpoints, ensuring dimensions and measures load properly. | |
| 137375 139060 | BQM-26344 | The Excel export from data grids, specifically the formatting for percentage fields, was improved to properly preserve decimal precision and thousand separator settings. Percentage values are now exported correctly (for example: 2,342,234.300% instead of 2342234%), matching the display format shown in the user interface. This ensures data consistency between the Web Application and Excel exports, preventing confusion when working with exported percentage data. | |
| 137788 | BQM-26381 | The employee search feature experienced occasional SqlException exceptions caused by incorrect connection management during periods of high database load. This led to occasional failures when executing search queries. The asynchronous/synchronous connection was fixed and an appropriate connection cleanup was added to RawSqlQueryAsync. | |
| 135982 | BQM-26441 | In the "Process" component and in the "Data" component, an issue where the grid export function was using the incorrect operator (AND instead of OR) when the "Any" filter option was selected with multiple filter values was corrected. The export now correctly uses the OR operator, ensuring that data matching any of the filter criteria is properly exported to Excel. | |
| BQM-26403 | Critical performance enhancements were introduced regarding the generation of statements/letters. | ||
| BQM-26462 | To improve code quality, the ESLint rules were enhanced with stricter validation standards and expanded auto-fixing capabilities. The improved ruleset automatically corrects common code quality issues during development, reducing the need for manual corrections. This update helps maintain consistent code quality across the platform and accelerates development by catching issues earlier in the development cycle. | ||
| BQM-26463 | AI-powered rule sets were added to the development environment to enhance the experience of working with AI-assisted features. These rule sets provide intelligent code validation and guidance during AI-generated code integration. This improvement ensures higher code quality standards and better consistency when leveraging AI capabilities within the platform. | ||
| 139513 | BQM-26541 | In process grid filters, the "Show results matching ANY of the following criteria" option did not work correctly when combining information column filters with indicator field filters. Previously, only rows matching the indicator criteria were returned, and the ANY matching logic for information fields was ignored. The filter logic now correctly applies the ANY operator, regardless of the field types used in the filter definition. | |
| BQM-26603 | In the "User" component, under the About section, the link to the Knowledge Base was renamed Help Center and now points to the new Help Center hosted in Zendesk and set to be launched into production on November 12th. | ||
| 141104 | BQM-26604 | In the Pay Predictor, the position search was not using row-level security, which could allow users to access data outside their permission scope. The issue was corrected by implementing row-level security for the position search, ensuring that search results are properly filtered according to user access rights. | |
| 141531 | BQM-26633 | In the "Process" component, an issue where the process Widget API endpoint was called multiple times when changing hierarchy was corrected by optimizing the widget loading logic. | |
| BQM-26634 | In process grids, the unnecessary caching of user plan data was removed in order to increase and maintain grid loading performance. | ||
| BQM-26640 | For more understandable audit trail, the id_profile value is now available in k_stats. | ||
| 142763 | BQM-26714 | InBYOM, when training AI prediction models, there was an issue where training requests would get stuck in the queue indefinitely due to MassTransit connection issues and lack of error handling. This behavior was corrected by adding connection resilience configuration and implementing proper error handling to update training status to Failed when issues occur, ensuring training requests are properly tracked throughout their lifecycle. | |
| BQM-26798 | Errors were occurring when attempting to generate large amounts of documents using the PDF generation feature, due to a synchronization issue related to the processing of multiple threads simultaneously. The issue was corrected by adding a warmup operation that ensures proper synchronization of the various processes of the task. | ||
| BQM-26833 | The CatalogDB ran out of resources when attempting to download documents -generated using the PDF generation feature, because the file service was attempting to download all tenant documents simultaneously. Now the file to be downloaded is referenced explicitly in the request and compared with the tenant UID. | ||
| 145046 | BQM-26837 | The generation of documents using the PDF generation sometimes caused to native access violation issues which led to application instability due to paralleled execution. | |
| BQM-26862 | Crashes were occurring when generating documents using the PDF generation feature. Investigation revealed that this was due to fast processing times of the tasks which caused collisions on system-version tables. To correct the problem, a delay and retry logic was added to the submission of updates to records. | ||
| BQM-26900 | In the statement generation feature, when using large data sources, the rabbitmq message size would sometimes reach the limit of 128MB. A compression mechanism was introduced to reduce the size of message. | ||
| BQM-26901 | Following the end of support for .NET framework 4.5, the application project was updated to reference version 4.7.2. | ||