side menu

2026.3

Here is the list of changes that you can explore right now by activating the BRIX trial version.

After April 13, 2026, all changes will become available to our clients in their active companies. Please note, the list may grow after the release.

The changes will become available in BRIX On-Premises after the next major release, 2026.4.

Please pay special attention to any updates with the #BreakingChangeAlert tag. They might require you to take extra steps to adapt or adjust your current configuration.

Business Processes

TEAM-31184 Added permanent deletion of process instances. The option is available when the processor_enable_instanceDeletion feature flag is enabled. In this case, a Delete Permanently button is displayed on the instance page with the status Completed, Interrupted, or Archived. Along with the instance, all its tasks are also permanently deleted.

#BreakingChangeAlert

Data types

  1. TEAM-9917 Search within values has been added for the Category field type. When filling in the field, start typing the required value. The list will then display only matching options for selection.
  2. TEAM-41306 Improved EQL search for data of Arbitrary app type. It is now possible to use only the namespace and code in the syntax without specifying the zero GUID.

Equivalent syntax examples that can be used:

[contract] = Refitem(‘clients’, ‘contracts’, ‘00000000-0000-0000-0000-000000000000’)
[contract] = Refitem(‘clients’, ‘contracts’)
[contract] = ‘clients:contracts:00000000-0000-0000-0000-000000000000’
[contract] = ‘clients:contracts’

  1. TEAM-41437 A Default option has been added to the settings of the Link field type. If the field is not filled with another value, the default value will be applied when the item is saved.
  2. TEAM-41691 The Date/Time field now supports an extended date range. It is now possible to set dates up to the year 2999 inclusive.

Widgets

  1. TEAM-37646 It is now possible to select a fragment of a template in a widget and create a new custom widget from it using the Copy to new widget option. A creation dialog will open to enter the widget name and code.

All necessary settings are automatically copied into the new widget: the selected template fragment, widget and field configurations used within it, as well as context settings. Previously, all of this had to be configured manually.

Copying the selected template fragment to the clipboard has also been added. The copied fragment can be pasted into the current or another widget, including in the interface designer of another company, such as a test environment.

  1. TEAM-41970 When mapping widget parameters to context variables, it is now possible not only to select an existing property from the Context tab, but also to create a new field.

To do this, click Link to field and select + New Field from the properties list. A property creation window will open with the name and type of the new field already prefilled according to the widget parameter. You can either configure additional settings or immediately click Create.

Structure versioning

  1. TEAM-15341 Version management for workspaces has been implemented. Available when feature flags allowVersionsSnapshots and exp_exchange_enable_packageVersions are enabled and the exchangeSrv service migration has been completed.

After that, in Administration > Developer tools, you can open Configuration Version Management. A configuration tree with system workspaces will be displayed. Clicking the three-dot menu next to a workspace name allows you to Freeze version or open the list of workspace versions.

Version context menu actions include: renaming a version, adding comments, viewing version contents, comparing with the current version, and restoring from archive.

  1. TEAM-37673 Versioning for folders has been implemented in the Document Categorization workspace. Feature flag allowVersionsSnapshots is used to enable it.

A new folder version is created when a folder is created or its settings are modified.

If a user restores an app version or imports a solution, workspace, or app, a check is performed. If registration is configured for the app and:

  • the registration office, section, and folder from the new version do not exist in the current version—they are created automatically. The folder receives its first version;
  • the registration office, section, and folder already exist—registration settings are restored from the new version, while folder settings remain unchanged, as one folder can be shared across multiple items. No new folder version is created.

Folder versions can be viewed, restored, and deleted in Administration > Document Categorization Settings. Open the version history via the three-dot menu next to the folder name.

Apps

TEAM-40063 Optimized bulk hard deletion of items. It is now performed in a single request.

External Portal

TEAM-40178 If a portal page is hidden for a user using the Page visibility option, the page name is now also hidden in the left portal menu.

Document Management

  1. TEAM-37839 Import/export of a solution, workspace, or app no longer fails if a document template reference exists but the file itself is missing (e.g. manually deleted). A warning is shown about the missing file, and the system administrator can replace the template and continue the process.
  2. TEAM-38021 Settings in Administration > Files > Available File Extensions for Upload have been updated:
  • the term “File formats” has been replaced with “File extensions” in labels;
  • a new option Use extension only has been added. When enabled, the system allows uploading files of specified extensions without validating their signatures. This enables support for formats without available signatures, such as .txt;
  • multiple signatures can now be defined for a single extension.
  1. TEAM-38209 A new option Configure Create button has been added to the File List widget settings (General tab). It allows restricting the available creation options when a user clicks Create in the Files workspace. You can disable creation of app items, web documents, folders, or files. This applies only to the configured widget and is available when Read-only mode is disabled.
  2. TEAM-40364 Improved user experience when creating shortcuts for files and folders. Now, selecting Create shortcut opens a dialog to choose the destination folder.
  3. TEAM-40415 It is now possible to navigate from an approval or information task to the item or file submitted for approval or information.

The link to the item or file is available at the top of the task sidebar in the Associated item widget.

  1. TEAM-39382 The watermark HTML template now supports retrieving signer data from an electronic signature (Subject) to display it in the document watermark.

The following fields have been added to the __$ES object:

  • IssuerSurname: signer’s last name;
  • IssuerName: signer’s first name and patronymic;
  • IssuerTitle: signer’s job title.

Live Chats

TEAM-42032 The graphical element Receive incoming message has been renamed to Receive Message in Live Chat to better reflect its purpose.

TS SDK and API

TEAM-41947 Added API methods for working with contracts:

  • /scheme/namespaces/{namespace}/contracts gets workspace contracts;
  • /scheme/namespaces/{namespace}/contracts/{code} gets contract metadata by workspace and contract code.

A corresponding service System.scheme.contract has been implemented in the TS SDK with similar capabilities.

Bug fixes

  1. TEAM-16063 In Administration > Schedule Compliance, when editing the Threshold value field without saving changes, the value was still displayed after page refresh or when reopening the page.
  2. TEAM-22432 Tasks executed in process debug mode were incorrectly included in schedule compliance reports under the employee responsible for their execution. This has been fixed, such tasks are no longer included in performance statistics.
  3. TEAM-29663 Deleted users were displayed in Company > Employees.
  4. TEAM-35730 If module settings contained parameters with default values, after exporting and importing the solution into another company, these parameters were reset to empty values.
  5. TEAM-41432 In the schedule compliance report, the target KPI color has been changed to gray to distinguish it from the actual KPI value.
  6. TEAM-41874 If access to an event was restricted, users belonging to the System Administrators group were incorrectly shown in the list of users with access.
  7. TEAM-40407 In the script editor, errors in typing and autocompletion occurred for app reference fields when a hyphen was present in the workspace code.
  8. TEAM-38169 When debugging an interface page configured in the designer, a variable set in the initialization script was not passed into the context. Context handling in debug mode has been fixed. Values are now displayed correctly.
  9. TEAM-41517 If field validation was implemented via script on a form and the property name in addContextError was misspelled (e.g., variablee instead of variable), the user could not save the form. No on-screen error message was displayed, although the error appeared in the browser console. This has been fixed, property names are now validated against the context.
  10. TEAM-41980 Widgets placed on a page stopped loading after navigating away and returning to the page. Redundant duplicate server requests have been eliminated, and widgets now load correctly across navigation.
  11. TEAM-42004 After adding a Code widget to a form or editing an existing widget in the interface designer, the Scripts tab content was not displayed. This tab now opens correctly.
  12. TEAM-41214 Files generated from templates in BRIX with names longer than 700 characters could not be downloaded from a Document-type app form via the File Preview widget. A 502 error appeared in the browser console. This has been fixed.
  13. TEAM-41360 When adding a file version, the File Update event handler was triggered twice, resulting in duplicate webhook requests and two process instances being started. This has been fixed, the event is now triggered only once.
  14. TEAM-41878 If file protection was enabled in Administration > Security Settings and the ELMA365_EXP_AUTH_ENABLE_AUTHORIZATION_V_2 parameter was active, errors occurred when opening, downloading, or editing files via document viewer services. Fixed, file protection now works correctly with all authentication settings.
  15. TEAM-41916 Fixed an issue where images could not be inserted into the Image field using the Paste from clipboard option.
  16. TEAM-41946 Fixed errors occurring when navigating to folders in the Document Categorization workspace.
  17. TEAM-41958 Fixed an issue where data added via script was not written to the system field __file of an app item, and the file was not saved.
  18. TEAM-41971 A solution with configured document categorization could not be installed due to a structure import error. Fixed.
  19. TEAM-42023 Opening the Files workspace caused long page loading due to the configured folder tree. In some cases, console errors occurred. Fixed by adjusting child folder loading.
  20. TEAM-42234 Fixed an issue where PDF files with very long names were saved as .pdf when downloaded to a local computer.
  21. TEAM-41057 Subscribers did not receive messages sent to an associated activity stream during a process using the Notification block. Fixed.
  22. TEAM-38947 An error occurred in Administration > Files when uploading .eps files.
  23. TEAM-41195 With self-signed OpenSSL certificates configured, the office editor did not launch for local file editing. Fixed by correcting network requests during local editing.
  24. TEAM-40739 In table view mode with Auto-refresh list enabled, when a table widget was added to the view form, loading errors occurred across browser tabs and newly created items were not displayed in other tabs. Fixed.
  25. TEAM-41123 Emails received via a connected channel sometimes arrived without attachments or, in rare cases, without a message body. After fixing incoming message processing and database updates, emails are now received with full content preserved.
  26. TEAM-41792 If email notifications for tasks and approvals were enabled in user profile settings, approval task notifications were not delivered, while other task notifications worked correctly. Fixed.
  27. TEAM-41868 Session creation in Channels > My sessions did not work. Clicking + New Session resulted in the error “No available channels at the moment,” even though the channel was correctly configured. Fixed.
  28. TEAM-42197 Improved synchronization of incoming and outgoing call activities in contact cards. Previously, call records were created only after call completion, and manual edits were not reflected. Now activities are updated based on changes in the call page.
  29. TEAM-42267 If email notifications were enabled in the user profile, emails about new tasks assigned via processes or the Tasks workspace were not delivered. Fixed.
  30. TEAM-41952 When updating estimate dates in a project task and submitting an estimate, the changes were not saved. Project estimates are now correctly reflected in the project calendar.
  31. TEAM-42009 Fixed an issue where new stage tasks and milestones in project plans were assigned number 0. Numbering now starts from 1 and follows the correct sequence.
  32. TEAM-38135 The link to the item created via the Create App Item activity was not written to the process context. Fixed.
  33. TEAM-41189 Added validation and UTC normalization for the nearest task due date when updating app fields dependent on task lists.
  34. TEAM-41816 Fixed an error occurring when completing a process task with a nested property from a user-type context variable placed on the form.
  35. TEAM-42205 Fixed an issue where a “First response” task in a multi-assignee swimlane was not assigned via API request.
  36. TEAM-5317 When saving a department with a long name in the organizational chart, automatic line wrapping caused a space to appear inside the word in Company > Company Structure.
  37. TEAM-17158 In SAML-authenticated sessions, the User Successfully Authenticated event handler was not triggered, and script logs were not created. Fixed.
  38. TEAM-23564 During initial company login, users were loaded in batches of 100, generating a high number of requests and heavy network load. Lazy loading from IndexedDB has been implemented. #BreakingChangeAlert
  1. TEAM-38708 In the new table version, if rows were populated via formulas from another table, the table was not displayed on the form, only the header was shown. Fixed.
360010947000.html 2026_2.html