beqom v10 HF228 - Release notes
Deployment date: NPR: April 14th, 2026 - PRD: April 21st, 2026
Fix version: v10 - HF228.5 - DB 10.0.1065
| Type | Reference | Description | |
|---|---|---|---|
| Zendesk | Jira | ||
| 119469 | BQM-25222 | An issue was corrected where the Kernel_SP_Process_PostMassValidation stored procedure (responsible for bulk validation in the Process component) failed due to a data type mismatch. The id_transaction column in the k_m_plans_payees_steps_workflow_xhisto table was defined as INT, but CURRENT_TRANSACTION_ID() returns a BIGINT value, causing an overflow on insert. The column has been promoted to BIGINT across all affected tables and stored procedures, with migration scripts provided to apply or roll back the schema change. | |
| BQM-26471 | An issue was corrected where developers were unexpectedly logged out of the application on local development environments when code changes triggered a hot reload (an automatic browser refresh applied after a file is modified). The root cause was an unpredictable app initialization sequence that could interrupt an active session during reload. App initialization is now ordered predictably, preventing unintended logouts. Features such as changing language or theme, logging in and out, and switching to the admin portal are unaffected. | ||
| 146068 | BQM-26899 | An issue was corrected where Super Admins could not delete uploaded documents when the file_owner_restriction setting was enabled. When a user account was deleted and recreated, the internal user identifier (uid_user) no longer matched the SSO identity (idExternalSSO), causing uploaded files to be incorrectly linked to the user. As a result, the Delete button was hidden and the uploader name appeared as null. User creation and recreation now correctly aligns uid_user with idExternalSSO, restoring the Delete button and the correct uploader name display. | |
| BQM-26928 | A new rich text field type was introduced for indicator fields used as comment columns in process grids. Users were previously limited to entering plain text with no formatting options. With this change, a rich text editor is now available, supporting bold, italic, hyperlinks, and other formatting options. Built-in sanitization protects against malicious content injection. | ||
| BQM-26930 | Clicking a rich text comment cell in a process grid now opens a dedicated modal editor, replacing the previous inline plain-text input. The modal supports formatted text including bold, italic, and hyperlinks. Read-only cells open the same modal in view-only mode, where links remain clickable but no edits can be applied. Built-in sanitization protects against malicious content injection. | ||
| 141711 | BQM-26954 | An issue was corrected where importing new rows via Excel into editable grids based on SQL views failed when the view contained derived or computed fields (columns whose values are calculated by the database rather than stored directly). Imports into such grids now complete successfully regardless of whether the underlying view contains derived or computed fields. | |
| BQM-26996 | A rich text column configuration was added to the QA dataset to support automated testing of the Process Grid Rich Text Comments feature. New API and UI automation tests were created covering field display and initial state, editor opening behavior, text formatting, hyperlink insertion, save and discard behavior, XSS protection (prevention of malicious script injection), size limits, multi-row and multi-user scenarios, export and import, filtering, and conditional validation. | ||
| BQM-27028 | An issue was corrected where clicking on an empty cell in a process grid did not open the expected pop-up editor. The pop-up now opens correctly when an empty cell is clicked. | ||
| BQM-27064 | An issue was corrected where selecting the In or Not In operator for string-type conditional formatting rules in process grids could crash the application, and allowed saving a rule without any values selected. Conditional formatting rules using In or Not In no longer cause a crash, and the Apply button is now disabled when no values are selected, preventing invalid rules from being saved. | ||
| BQM-27072 | An issue was corrected where creating or opening a prediction page failed with a server error when the associated model had no interval configured. The GetPredictionResult service threw a null reference exception when attempting to access interval data that was absent. Null-safe handling has been added in PredictionService and ModelService so that missing interval data is handled gracefully, with no database changes required. | ||
| BQM-27104 | An issue was corrected where opening a Data Grid crashed the application or displayed an error message when the back-end returned an unexpected column configuration response. Data Grid now handles variable back-end column configuration formats correctly, keeping the grid accessible in all cases. | ||
| 151806 151826 151834 151955 152044 | BQM-27106 | An issue was corrected where Basic Export (Values Only) in process grids failed when any visible column contained negative numerical values. The export sanitization logic (which screens cell values for formula injection attempts) incorrectly treated negative numbers as potentially malicious content. Negative values now export correctly, while security protection against malicious formula injection is maintained. | |
| BQM-27112 | An issue was corrected where grid filtering and conditional validation formulas on rich text fields produced incorrect results. Filters and validation logic were being evaluated against the raw HTML markup of the field value (for example, <p>beqom</p>) rather than its visible plain-text content, causing operators to match incorrectly and formulas to fail. Rich text fields now use a plain-text representation for both filtering and conditional validation. Behavior for non-rich text fields is unchanged. | ||
| BQM-27119 | An issue was corrected where process grid saves that internally used simulation mode (a server-side mechanism that validates changes before applying them) were not recorded in k_stats (the application's performance statistics table) in some cases. A database script update to Kernel_View_Simulation_k_m_values resolves the recording gap. Saves performed with simulation continue to pass normally. | ||
| BQM-27125 | An issue was corrected where k_stats (the application's performance statistics table) silently discarded all entries during batch inserts under concurrent load. The batch insert exceeded SQL Server's maximum parameter limit, causing the entire batch to be dropped without error. Batches are now split into chunks that stay within SQL Server's parameter limit, and empty SSO identifiers are correctly mapped to NULL, ensuring statistics are reliably recorded under load. | ||
| BQM-27127 | An issue was corrected where rich text cells that had been cleared in process grids were still returned by the Is Not Empty filter. The database function used for rich text filtering did not correctly handle empty strings, causing cleared cells to be treated as containing content. The function has been updated to treat empty rich text values as null, so cleared cells are no longer matched by Is Not Empty filters. | ||