beqom v10 HF227 - Release notes

Deployment date: NPR: March 11th, 2026 - PRD: TBD

Fix version: v10 - HF227.7 - DB 10.0.1062

Reference		Description
Zendesk	Jira
116869 117360	BQM-25017	An issue was corrected in the Process Grids where saving decisions with multiple indicator fields configured with SQL default values took 30+ seconds due to the system creating separate database queries for each indicator field. The query logic was optimized to batch requests from the same table and fetch only values needed for calculations, reducing save time from approximately 30 seconds to under 1 second.
122835	BQM-25580	In Analysis, an issue was corrected where frozen table headers in SSRS standard reports did not remain visible while scrolling through data. The headers would disappear as users scrolled down, making it difficult to track column context. The report viewer scrolling behavior was updated so that frozen headers now stay fixed in place during vertical scrolling, creating a more consistent and user-friendly viewing experience.
	BQM-25770	A security issue was corrected in which Excel exports could interpret certain characters (=, +, -, @) at the beginning of cell values as formulas, potentially leading to command execution vulnerabilities when files were opened. The platform now automatically sanitizes these characters by prepending them with an apostrophe, preventing formula injection across all Excel exports including grid data, process data, and ad-hoc exports.
	BQM-25771	A security issue was corrected in which Cross-Origin Resource Sharing (CORS) configuration accepted API requests from any website using a wildcard configuration, potentially allowing unauthorized access to sensitive data. The configuration was updated to validate and accept requests only from explicitly trusted origins as defined in service configuration.
	BQM-25773	A security enhancement was implemented to protect user session cookies across the Login/Passport page and main application. Session cookies were not configured with proper security flags (httpOnly, secure, SameSite), leaving them vulnerable to cross-site scripting (XSS) and cross-site request forgery (CSRF) attacks. Industry-standard security flags have now been applied to all session cookies, preventing attackers from accessing or manipulating session data through client-side scripts.
107508	BQM-26033	In Process > Basic Export, an issue was corrected where calculated indicator fields displayed incorrect values in the exported Excel file when a visible calculated field depended on a hidden calculated field. The formula evaluation logic was updated so that all calculated fields, including hidden intermediate fields in the dependency chain, are now evaluated before applying the visibility filter, ensuring exported values match the UI display.
133959	BQM-26119	An issue was corrected in the data grid grid export/import functionality where an incorrect status message was displayed when a batch error occurred. Previously, when a duplicate identifier was rejected during import, the system incorrectly reported 'count added: 1' even though no rows were successfully imported. The status message now correctly displays 'count added: 0' when batch errors prevent rows from being added.
134188	BQM-26169	In process grids, an issue was corrected where applying a quick search filter in the process grid while grouping was enabled did not return the expected rows, causing relevant results to be omitted. The filter logic was updated to correctly apply where conditions when grouping is active, ensuring that quick search returns the correct rows and the total count accurately reflects the real number of records.
	BQM-26175	A security issue in data grids was corrected where users could access drop-down values and associated field data via API calls even when they did not have the necessary module permissions. Proper authorization checks were added to ensure users can only retrieve grid field data when they have the appropriate Data module access rights.
	BQM-26207	A performance issue affecting data grids was corrected where unnecessary date conversions in grid filters were impacting query efficiency and index usage. The date handling logic was optimized to eliminate redundant conversions, improving overall grid performance when filtering by dates.
	BQM-26208	Database operations executing localization queries were updated to standardize culture parameter definitions across stored procedures and tables. Previously, culture parameters used inconsistent data types (varchar, nvarchar, nchar) and sizes, causing implicit type conversions that impacted index usage and increased CPU consumption. All culture parameters have been standardized to NVARCHAR(10) to match the rps_Localization table definition, enabling better index usage and reducing CPU consumption across grid operations, hierarchy management, and process mobility functions.
	BQM-26209	Database stored procedures used for grid data retrieval and bulk grid operations were optimized to eliminate implicit type conversions that affected query performance and index usage. Parameter casting and sizing were adjusted in the affected procedures to reduce CPU consumption during grid rendering and data manipulation operations.
	BQM-26210	A database performance optimization was implemented for statistics data inserts to the k_stats table. Insert queries were updated to use parametrized queries with proper data types (nvarchar instead of varchar), reducing implicit type conversions from 22 to 4 and improving query execution speed with no impact on data integrity.
	BQM-26316	A security vulnerability was corrected where technical information including server versions, IIS details, X-Powered-By headers, and Swagger documentation endpoints were exposed in production environments across API services, allowing potential identification of vulnerabilities. Debug features and server information headers have been properly disabled in production, and Swagger documentation is now restricted to development environments only across Data API, Object API, Gateway API, EnvironmentManager API, and Analytics API, significantly reducing the attack surface.
136710	BQM-26356	A new eligibility check endpoint was added to the pay prediction functionality. Admins can now verify whether an employee is eligible for a pay prediction based on payee ID or code alone, without requiring a prediction request to first be generated. This enhancement introduces a new SQL function and API endpoint to support pre-prediction eligibility validation.
137717	BQM-26389	Using the "after" (>) and "before”"(<) date filters in process reports generated an invalid @planFilterCustom value because the date was not wrapped in quotes, causing the filter to be ignored and all employees to be returned. Now, the date filters correctly wrap the date value in quotesso custom filters are built properly and the SSRS reports respect the selected date range.
138267	BQM-26409	An issue was corrected in standard reports and data grids where NHibernate lazy load errors occasionally caused slow response times ranging from 5 to 30 seconds when loading grids and reports. The issue was resolved by attaching missing properties to NHibernate models, eliminating 'could not resolve property' errors that were impacting grid and dashboard loading performance.
	BQM-26464	Multiple obsolete feature flags were removed from the system configuration. These flags were no longer needed as the features they controlled had been permanently enabled. This change simplifies system configuration and improves code base maintainability.
	BQM-26466	An issue in the development environment was corrected where both npm and yarn package managers were present in the repository, causing installation conflicts and confusion. All npm-related files were removed, standardizing on yarn as the sole package manager.
	BQM-26474	Multiple security vulnerabilities and code quality concerns detected by static code analysis were addressed. High-priority security vulnerabilities and reliability issues in the application codebase were resolved, improving overall code quality and reducing potential security risks.
	BQM-26477	Test execution time for the front-end unit test suite was significantly improved through library migration and package upgrades. The testing module suite now completes in approximately 22 minutes, a reduction of more than 50% from the previous 50-minute execution time.
	BQM-26508	The mobile app was updated to use the latest SDK versions required by app store platforms, and dependent libraries were upgraded to compatible versions. This technical update ensures continued compliance with platform requirements and maintains app functionality across all features.
122215	BQM-26523	Process grid loading performance was improved by refactoring the generated database query code. The CTE for filtered payee requests was transformed into a temporary table structure, increasing database query efficiency and reducing grid load times.
139132	BQM-26526	In Process > Reports, an issue was corrected where selecting the "any" filter option (logical OR) still applied the AND logic when generating the @planFilterCustom parameter, causing reports to return no data or incorrect results. The filter logic was updated so that "any" now correctly applies OR between conditions, while "all" continues to use AND logic as expected.
140650	BQM-26607	In Pay Predictor, the Export button for prediction templates (PDF) can now be hidden or displayed based on back-end security configuration. The visibility of the button can be controlled through Pay Predictor settings, allowing admins to restrict access to sensitive peer compensation data based on profile, team, or user.
	BQM-26665	An issue in the Process budget widget was corrected where rapidly changing hierarchy nodes or filters caused race conditions with multiple simultaneous requests, potentially displaying incorrect budget data. The issue occurred when a second request completed before an earlier request, overwriting the display with outdated information. The request handling logic was updated to cancel pending requests when new ones are initiated, ensuring only the most recent request completes and displays accurate data.
	BQM-26666	Audit logging was added for the Statement Generation and Dashboard services. System actions including template modifications, merge runs, and dashboard operations are now captured in dedicated audit tables (k_stats_statementgeneration and k_stats_dashboard), providing visibility into user actions and system usage for these modules.
	BQM-26701	Additional logging was introduced in the SSO service to improve visibility into code paths that trigger the use of deprecated AES encryption algorithms. The logs now include stack trace information to support ongoing security investigations and the phased retirement of legacy encryption methods.
114201	BQM-26706	An issue in Processes > Grid was corrected where aggregation values displayed incorrect calculations when users modified data without saving and then removed quick filters. The grid logic was updated to recalculate group summaries by applying unsaved changes to original aggregation values, ensuring aggregations correctly reflect all modifications.
142532	BQM-26708	An issue was corrected where exporting a Manager Report with password protection caused any reload of the report to fail. The export URL logic was updated to preserve all original parameters alongside the export flag, restoring correct refresh behavior and SSRS link functionality.
142763	BQM-26714	An issue in BYOM was corrected where AI prediction model training requests would get stuck in the queue indefinitely due to connection issues and lack of error handling. Connection resilience configuration and proper error handling were added to ensure training requests are tracked throughout their lifecycle, with failed requests now correctly marked as Failed.
142610	BQM-26715	A validation warning was added to Pay Predictor > Prediction when exporting Final Offer PDFs. When a cross-currency movement is detected (i.e., when an employee's current pay currency differs from the prediction currency), a confirmation dialog now appears to alert users about potential data accuracy issues. Users can choose to continue with the export or cancel the operation.
	BQM-26726	An issue was corrected where hidden data grids accessed via direct URL were incorrectly logged in the last 10 visited items list, even though users were unauthorized and could not view the data. Validation was added to skip recording unauthorized grids in navigation history, ensuring only accessible items appear in the last visited list.
142954	BQM-26732	An issue in process grids was corrected where hyperlink-enabled information fields did not respect tree security permission overrides when the is_override_workflow_permission flag was set. Hyperlink values were incorrectly displayed to users even when their security permissions should have hidden them. The process grid now properly validates tree security settings to ensure hyperlinks are only visible to authorized users.
	BQM-26735	An issue in Analysis > Standard Reports was corrected where reports containing iframes failed to render correctly. The issue occurred when a feature flag controlling component rendering was removed. The feature flag has been restored to ensure iframe-based standard reports display properly.
143292	BQM-26747	Pay Predictor now supports role-based field permissions for core segment fields and model fields. Administrators can configure fields to be editable, read-only (greyed out), or hidden based on user profile and workflow type (new hire vs. existing employee), providing granular control over which prediction criteria users can modify. Configuration is managed through new Pay Prediction Settings API endpoints.
	BQM-26753	In Statement Generation, an issue was corrected where processing statements with dynamic images for high-volume payee scenarios (5,000+ recipients) caused performance bottlenecks and message size limitations during recipient processing. Image processing was deferred to document generation time, bulk SQL operations were implemented to reduce database transactions, and image cache building was parallelized, enabling efficient processing of large-scale statement generation runs.
	BQM-26759	The pay prediction for existing employeesin Pay Predictor was enhanced to validate employee eligibility when a payee is selected. If an employee is not eligible for prediction (as configured via the eligibility function), an alert banner now appears with a descriptive message and the Next button is disabled, preventing users from attempting to create predictions for ineligible employees.
143504	BQM-26762	In ad hoc reports, an issue was corrected where queries with numeric filters executed extremely slowly (8+ minutes) due to an incorrectly written function, which prevented SQL Server from using indexes. The function was moved from to the correct clause, enabling index usage and significantly improving query performance while maintaining proper value rounding for display.
	BQM-26767	An issue was corrected in process grids where performing a Basic Export on a process grid that included certain read-only columns resulted in an error message stating "Process basic export is not possible due to an error when fetching values."." The root cause was that read-only columns were not being properly sanitized during the Excel export process. The sanitization logic was updated to temporarily apply sanitization to all columns, including read-only ones, before restoring their original state.
	BQM-26774	Pay Predictor now supports workflow-specific configuration to control visibility of the Final Offer card in the Prediction Summary section. Admins can independently configure whether the final offer is displayed in the new hire workflow, the existing employee workflow, or both, using the finalOfferEnabled setting in pay prediction configuration.
	BQM-26775	A new configuration setting was added to control Candidate Name visibility in the new hire flow within the pay prediction workflow. When the setting is configured to hide the Candidate Name field, it becomes optional when creating new hire or position predictions, allowing organizations to generate predictions for positions without differentiating between individual candidates.
	BQM-26776	In Pay Predictor, an issue was corrected where the Lump Sum and Sign-on Bonus input fields in the Final Offer card were always displayed regardless of the lumpSumActive and signOnBonusActive configuration settings. These fields now correctly show or hide based on the pay prediction settings for each workflow step (New Hire and Existing Employee flows).
	BQM-26777	Pay Predictor now supports configurable field visibility and editability settings based on prediction type (new hire or existing employee). Admins can configure fields to be hidden with default values applied in the background, set to read-only (greyed out), or displayed with pre-populated default values. Field visibility rules are applied per prediction type, allowing different configurations for new hire versus existing employee scenarios.
	BQM-26778	An issue in Pay Predictor was corrected where field validation did not run automatically when opening a new hire prediction, causing core fields and model fields to display inconsistently and requiring manual user action to trigger validation. Field validation now runs immediately upon opening a prediction, ensuring that both core and model fields are properly populated and any required field reviews are indicated at load time.
	BQM-26779	In PayPredictor > Final Offer, it is now possible to adjust base salary using a percentage increase input, which automatically recalculates when the salary amount is changed directly. Two new bonus fields (Annual Bonus % and Non-Annual Bonus %) were added to the Final Offer card, displaying current values with tooltips for context. Configuration options allow administrators to show or hide these fields separately for new hire and existing employee scenarios.
	BQM-26786	A configurable settings system was added to Pay Predictor, enabling admins to control field visibility, export options, and feature availability based on user profile and prediction type (new hire or existing employee). Two API endpoints were implemented: one to define settings per profile and prediction type, and another to retrieve the effective configuration for a given user and context. This enhancement allows organizations to customize Pay Predictor behavior without requiring code changes.
143055	BQM-26789	An issue was corrected in Process Grid where bulk validation or bulk revoke actions failed with a generic error when selecting all rows across multiple pages if the filter query exceeded 4000 characters (typically affecting selections of 250+ items with pagination enabled). The stored procedure parameter limit was increased to support larger datasets with complex filters, allowing bulk operations to complete successfully.
142954	BQM-26792	An issue in process grids was corrected where calculated fields did not respect workflow permission override settings and remained visible when they should have been hidden based on the user's access rights. When the permission override flag was enabled without read access, calculated fields incorrectly displayed values (typically as 0) instead of being hidden. The visibility logic was updated to properly enforce permission override rules for calculated fields.
	BQM-26793	In PayPredictor, the final offer now supports two new bonus percentage fields (Annual Bonus % and Non-Annual Bonus %) that can be edited and saved when updating pay prediction final offers. The underlying data model, API endpoints, and database schema were extended to capture and store these bonus percentage values, enhancing compensation tracking capabilities for both new hire and existing employee scenarios.
	BQM-26795	The Pay Equity URL defined Admin Settings > Technical Admin > Settings Management > Global is now opened in a new browser tab rather than displayed in an embedded frame. This change resolves security issues associated with the previous implementation and provides direct access to the Pay Equity application via the URL configured in the Admin Portal.
	BQM-26796	A new Field Settings feature was added to Pay Predictions, enabling Compensation admins to configure field visibility (Editable, Readonly, or Hidden) and default values per profile and prediction type (New Hire or Existing Employee). Field settings are stored in the tenant database to support bulk configuration updates via direct query. Settings follow an inheritance model: fields default to Editable unless a global setting (all profiles) or profile-specific setting is defined, with profile-specific settings taking precedence.
	BQM-26798	An issue was corrected in statement generation where intermittent PDF generation failures occurred during high-volume parallel processing due to a race condition in license validation. The issue manifested approximately 15% of the time when generating large batches of statements, requiring manual retry. A startup warmup operation was added to complete license validation before concurrent PDF operations begin, eliminating the intermittent failures.
	BQM-26808	The field cascading configuration in Pay Predictor was enhanced to support granular control per Pay Prediction type (e.g. Position flow, New Hire flow). API endpoints were updated to accept a PredictionType parameter, enabling compensation admins to enable or disable cascading independently for each prediction type rather than only globally. This covers the back-end part.
	BQM-26809	In Pay Predictor, the cascading configuration functionality was enhanced to support granular control by prediction type (New Hire or Existing Employee). Field validation and field value endpoints now accept a prediction type parameter, enabling administrators to configure cascading behaviour independently for each prediction type rather than globally across all prediction flows. This ticket covers the front-end part.
	BQM-26832	In Pay Predictor, information icon tooltips were added to the Annual Bonus, Non-Annual Bonus, Lump Sum, Raw Pay Prediction, and Pay Recommendation fields to provide contextual information for end-users. The tooltips can display different text for new hire versus existing employee scenarios, support localization and translation, and appear both in the main prediction display and within the Final Offer edit dialog. If tooltip text is not configured, the information icon is automatically hidden.
	BQM-26833	A performance issue affecting statement generation with large volumes of images was corrected. The File Service was attempting to fetch all tenant documents during the download process, causing resource spikes on the catalog database. The logic was optimized to reference files directly and validate tenant ownership, significantly reducing database load during high-volume statement generation.
142024,144207,145046,145398	BQM-26837	An issue was corrected in Statement Generation where parallel PDF processing caused intermittent native memory access violations, resulting in application crashes and service instability. The parallel execution logic was removed to ensure thread-safe document generation. Statement generation runs now complete consistently without unexpected service interruptions.
	BQM-26853	An issue was corrected where validating records in the process grid resulted in an error message and the operation could not be completed. The issue was caused by incorrect ordering in information column queries that forced a syntax error. Users can now validate employees in the process grid as expected.
	BQM-26860	The in-application cookie policy documentation (accessible via User > Cookies) was updated to remove references to obsolete cookies that are no longer used by the platform. The updated documentation now accurately reflects the cookies currently in use.
145278	BQM-26870	An issue in Pay Predictor was corrected where quickly pressing Enter after beginning to type in the Select Employee field within the New Prediction > Existing Hires dialog caused the page to crash with an error message. The application now properly handles cases where a null or undefined value is selected, preventing the error and allowing users to continue their workflow.
	BQM-26879	A configuration option was added to hide the Candidate Name field in the new hire prediction flow within the Pay Predictor module. When the field is hidden, the Prediction Name is displayed instead of the Candidate Name on the prediction summary page. This configuration supports workflows where predictions are generated for positions without identifying specific candidates.
	BQM-26880	An issue in Statement Generation was corrected where document templates containing non-ASCII character sets (such as Chinese) caused data truncation and processing errors, particularly with large payloads. The serialization logic was updated to avoid encoding/decoding issues, and the PDF generation library was upgraded to properly handle non-ASCII character sets.
142870	BQM-26883	An issue in data grids was corrected where saving or updating records containing binary data fields (such as signatures or documents) failed with a data truncation error. The issue occurred because varbinary(MAX) column definitions were not correctly synchronized during database operations, causing the system to reject data during grid updates. The synchronization logic and grid data handling procedures were corrected to properly recognize and support binary field definitions, allowing records with binary data to be saved and updated without errors.
	BQM-26886	In Pay Predictr, prediction requests that failed due to a missing AI model displayed a generic "Object not found" error message. The error handling was updated to return a more specific "No Model Found" message, providing clearer feedback when no matching model exists for a prediction request.
122632	BQM-26897	An issue in process grids was corrected where grouping by workflow step and performing a Submit or Revoke action caused workflow step group headers to disappear until the page was manually refreshed. The grid refresh logic was updated to correctly recalculate grouped rows when workflow step composition changes, ensuring group headers remain visible after Submit/Revoke actions.
	BQM-26900	Statement generation was enhanced to handle large datasources more reliably by implementing data compression and moving message payloads to an alternative storage mechanism. This corrects an issue where merge runs processing more than 4,000 payees would fail without a clear error message when exceeding the 128MB message size limit. Merge runs now complete successfully for large datasets, and when configured size limits are exceeded, a meaningful error message is displayed in the Export Run Details.
146457	BQM-26910	The pay_prediction_parameter table schema was extended to capture Job Position ID and Job Position Code for all pay prediction requests. Two new columns, id_position and code_position, were added to support audit requirements and ensure data consistency across UI-based and API-based prediction workflows.
	BQM-26915	In Statement Generation, an issue was corrected where merge runs containing only payees not configured in a datasource were marked as failed instantly, behaving inconsistently with runs containing a mix of valid and invalid payees. Error reporting was updated so that all merge runs now report failures at the individual payee record level, regardless of whether one, some, or all payees lack datasource configuration.
	BQM-26916	Newly deployed databases were not compiled correctly, causing the Compensation Planner creation to fail due to non-clustered indexes being created on an incorrect file group. The database deployment logic was updated to explicitly specify the correct file group during index creation.
107477	BQM-26926	An accessibility issue in process grids > conditional formatting was corrected where the multiselect input field in the "Format Cells If" section lacked a proper label for assistive technologies. The missing aria-label attribute was added to improve screen reader support when configuring conditional formatting rules with operators that display multiselect controls.
	BQM-26931	Enhanced diagnostic logging was implemented for deprecated encryption and decryption functions. Warning messages now include stack trace information to help identify what triggers legacy encryption methods, improving troubleshooting capabilities for technical teams.
	BQM-26933	Keyboard accessibility for column drag-and-drop reordering in the Process component was improved to support screen reader users. When screen reader software is active, columns can now be reordered using Alt+Enter to lift an item and Alt+Arrow keys to move it, resolving an issue where default keyboard shortcuts were intercepted by assistive technology. This enhancement applies to the columns dropdown and conditional formatting drag-and-drop controls.
	BQM-26941	An issue in Pay Predictor was corrected where a validation error prevented users from creating a new hire prediction when the candidate name visibility setting had not been explicitly configured. The system now defaults to showing the candidate name field when no setting value exists, maintaining the original behavior introduced prior to the setting's addition.
147575	BQM-26949	Inbox > Team Documents: An issue was corrected where managers could view their own employee statements in search results even when the "Can See Himself" permission was disabled in hierarchy delegation settings. The hierarchy security logic was updated to properly enforce delegation permissions during search operations, ensuring managers can only access statements according to their configured security settings.
	BQM-26972	An issue in the Process component was corrected where clicking Discard Changes while focus remained on an edited cell caused the discarded value to disappear and then reappear. The discard logic was updated to properly handle focused cell inputs, ensuring that the grid returns cleanly to the last saved state without reappearing values.
147885	BQM-26982	An issue in the Process component was corrected where users intermittently encountered a generic 'An error occurred' message and the grid failed to load. The issue occurred when different users with varying profile-based field visibility accessed the same process, causing cache mismatches that resulted in HTTP 400 errors. The grid loading logic was corrected to populate cache with complete reference data regardless of which user accesses the plan first, ensuring reliable grid display for all users.
148536	BQM-26984	AIn Pay Predictor, a new global setting was added to control PDF export availability for compensation predictions involving cross-currency movements. When enabled, the Export button remains visible and displays a warning when cross-currency movements are detected; when disabled, the export button is hidden entirely. This provides administrators with configurable control over cross-currency export scenarios.
148611	BQM-26986	An issue in new hire pay predictions was corrected where profile-specific field defaults configured in field settings were ignored during prediction payload generation, causing hidden or defaulted fields (such as age, tenure, or FTE) to be persisted as null instead of their configured default values or position baseline values. The default resolution logic was updated to apply profile-specific field settings first, falling back to tenant defaults only when profile-specific settings are missing. Prediction payloads now consistently honor the configured precedence: form input value, job position or payee value, then field default value.
	BQM-27012	The PDF generation library (Apryse PDFTron) was updated to version 11.11.0 to resolve a performance issue in statement generation. An issue where certain Unicode characters (PUA characters) used in Word templates caused PDF generation to slow down significantly was corrected. Statement generation now performs as expected when templates include these character types.
148719	BQM-27015	An issue was corrected in which the default interval was no longer displayed as the salary range in pay predictions after the capping feature was implemented. The logic was updated to always display the salary range for the default interval, with capping applied when enabled.
150617	BQM-27070	Attempting to open the "Process" component from the navigation bar opened the "Home" component. The issue was cause by the presence of negative IDs in the default process URL, causing a redirection. The issue was corrected and the "Process" component opens as expected.
	BQM-27038	An issue was corrected where the Individual Planner failed to load when accessed via deep links containing payee identifiers. The routing logic incorrectly parsed the payee ID and UID from the URL pattern, causing endless loading or unintended redirects. The route parsing was corrected to reliably extract payee information, ensuring the Individual Planner loads properly with the expected payee and grid data.
	BQM-27054	An issue was corrected where process grids exhibited significantly degraded response times under high concurrent usage, impacting user experience when multiple users were working simultaneously. The issue was caused by two recent query optimizations that unintentionally introduced database contention. Performance has been restored to previous baseline levels by reverting the affected changes.
	BQM-27061	An issue was corrected where workflow validation on process grids failed with an HTTP 400 error and the message "An error occurred. Please try again.". The error was caused by incorrectly ordered parameters in the bulk validation logic, which generated invalid SQL syntax. Workflow validation and bulk validation now complete successfully.
151806, 151826, 151843, 151955, 152044	BQM-27106	Processes containing at least one negative value in the visible columns could not be exported using the Basic Export feature. The export would fail. To correct this, the export sanitization logic so that the platform distinguishes between negative values and formula injection attempts. Process grids with negative values can now be exported correctly while maintaining safety measures against malicious formulas.

Attachments

zd_v10-hotfixes.4.log-1173141225.zip
8 KB Download