The 2026.3 release introduces two new features and five fixes.
BREAKING CHANGE: Server instability under high rate of simple SQL calls
We have removed the old workflow profiler, which was causing issues when processing large numbers of SQL queries. The server now runs more stably, and MiniProfiler is the only tool available for profiling.
FEATURE: Logging levels in Work Queue procesing
We fixed logging levels in Work Queue processing. Failures of automatic queue processing are now logged as ERROR instead of FATAL, as the previous severity was too high. Failures caused by RuleException are logged on DEBUG level to allow filtering via logging configuration.
FEATURE: Close all tabs context menu
We have added the ability to close multiple windows at once in the client application. This feature is similar to the one in ORGIAM Architect and applies to windows that do not contain any unsaved changes:
FIX: Autocomplete active where it should be off
Fixed Chrome auto-completion of form fields. Some input fields were being auto-completed by Chrome despite having autocomplete=“off”. This was caused by missing name attributes on editors, which triggered browser heuristics. We added attributes to significantly reduce unwanted auto-completion.
FIX: Parameters were not passed to XsltDataPage when using custom filtres
Fixed an issue where Model API endpoints based on XsltDataPage did not pass path parameters when the AllowCustomFilters property was set to True. Parameters are now correctly propagated when custom filters are used.
FIX: Disabling action buttons in lazily loaded screen
Fixed the error message caused by disabling action buttons on the root section of lazily loaded screens. Previously, when action buttons were disabled on the root screen section of a lazily loaded screen, the frontend failed to display the screen and showed the error: “Cannot infinitely scroll on dataStructureEntity: … because it has no default ordering on the displayed form.” Now users get a more comprehensible error message: “The root section with the root entity can’t have action buttons disabled.”
FIX: Occasional null reference exception in for-each workflow block
We fixed an issue where a NullReferenceException could occasionally occur in the for-each workflow block due to incorrect initialization order of the workflow call and event handler registration. The initialization order was adjusted to prevent accessing a null call reference.