side menu

2026.4

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

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

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.

 

System interface design

  1. TEAM-19977 The system interface design has been updated and standardized:
  • The appearance of icons and basic components has been updated.
  • Fonts and colors in some components have been changed.
  • Theme settings have been updated.

The new design also introduces design tokens technology.

Design tokens are the smallest units of visual style stored as named variables. These variables contain specific style values such as colors, spacing, fonts, border radius values, shadows, and more.

For example, instead of specifying “#3366FF” across all layouts and code, the token color-primary is used. If the color needs to be changed to “#4422CC”, it is enough to update the value only in the token file, and it will automatically change everywhere the token is used.

We recommend implementing this approach in custom solutions. To do this, use:

  • The new style editor feature.
  • The new Add design token option added to the Code widget context menu.

To ensure a gradual transition to the updated design, some changes are temporarily disabled by default. A new Theme setting has been added on the Administration > Theme page with two options:

  • V1: the design currently used in your company. Enabled by default;
  • V2: the new design that you can enable.

Planned transition stages:

  • Starting from release 2026.7, the new design will be enabled by default, but you will still be able to switch back to V1.
  • Starting from release 2026.11, only V2 mode will be available, without the ability to switch back to V1.

Important: before release 2026.11, you must adapt your configurations to the new V2 design.

#BreakingChangeAlert

  1. TEAM-37647 A style editor has been added to the custom widget builder, allowing you to write custom CSS styles. Use the Style Editor button on the top panel of the interface designer to show or hide the editor. Main features of the style editor:
  • The Apply button lets you apply styles in real time without publishing or debugging the custom widget.
  • Support for design tokens has been implemented.
  • Styles defined in the widget builder are isolated. They are stored and applied separately from styles defined on the System tab in the HTML styles property or through the Code widget. Styles defined outside the editor continue to work and are not overridden, but we recommend using the new Style Editor.

Additionally, the behavior of the HTML classes property editor has been updated:

  • Added classes are now displayed as tags below the input field;
  • Clicking an already added class saves the widget settings and opens the style editor panel.

Widgets

  1. TEAM-13559 The Code widget now allows rendering a custom widget on a form when its output parameter is linked to the current context.

To do this, use the new option—the icon with two arrows—in the parameter mapping window for the custom widget and current context. Click it after selecting a property for the widget output parameter. The following code will be generated:

<%= UI.widget.render('namespace@some_widget', {
field1: { path: ['item', 'field1'] },
}) %>

An Advanced tab has also been added to the Code widget settings. The following options are available there:

  • Hide contents in builder mode option has been moved there.
  • A new Content redraw option has been added, allowing you to choose when widget data should be updated: on value change, after value change completion, or never. The last option only applies to variables defined using syntax like Context.data.some_field.
  1. TEAM-25082 The behavior of the Hide single-page tabs in the Tabs widget has been changed. Now, if multiple tabs are configured but only one is available to the user, the tab name is hidden. Previously, the tab name was displayed.
  2. TEAM-37259 The function executed after value change completion can now be triggered in widget scripts when the following values are modified:
  • Value of a field changed in scripts, for example Context.data.some_field = 'new_value'.
  • Value of a field linked to a widget parameter.

Previously, the function only executed when a user manually changed the value in the interface.

  1. TEAM-39803 A new Dynamic Table widget has been added. It allows displaying arbitrary data in a table. For example, you can display a button or complex content inside a table cell.
    The widget settings specify a variable of the Table type to pass list data from a standard table into the widget. In the widget template, you can define the number of columns and configure header and cell content templates for each column.
  2. TEAM-42952 A new Status widget has been added, allowing customization of the appearance of content in the Status field. Widget settings include display parameters such as text, icon, color, and more.
  3. TEAM-36222 The Hierarchy widget used to display related items from a single app as a hierarchical structure, now supports app property-level permissions. Users only see fields they have access to.

Apps

TEAM-37096 The number of app items in a list can now be displayed even if the Number of items displayed option is disabled in the app settings. A new icon has been added to the search bar. Click it to display the item count.

Document management

  1. TEAM-31736 Support for previewing .mov videos has been added. If your browser cannot display this format, you will see a prompt to download the file.
  2. TEAM-38412 If email is configured in the Live Chats workspace and file extension restrictions are enabled, files with allowed formats in emails received through live chats are now available for preview. Previously, such files could not be previewed.
  3. TEAM-40362 A new option has been added that allows sharing links to:
  • The file or document preview window.
  • The file or document version preview window.

The new option, represented by a link icon with an eye, is available:

  • In the Files workspace, in the file list context menu and on the file view/edit form.
  • On view and edit forms of apps of the Document type.
  • On the file or document version preview form.

The option for sharing file download links is now available only in the interface designer. For example, you can insert a copied download link into the Code widget.

  1. TEAM-40453 Document template syntax now respects the number of decimal places configured in variable display settings.
  2. TEAM-42011 Workspace administrators can now access files from document templates stored in the workspace. Previously, such files were unavailable for viewing and editing.
  3. TEAM-42380 The SignMe module has been removed from the BRIX distribution. The module is no longer displayed on the Administration > Modules page if it has never been enabled before. If the module is enabled and used in company processes, it will continue working correctly.
  4. TEAM-42480 The settings window of the File List widget on the General tab has been updated:

The Read only option has been renamed to Access settings, and the value is now configured using a switch. The default value is Edit.

  • Create button restrictions have been moved into a separate block.
  • The view option is now configured using a switch with Folder and Filter values.
  • Switching between folder search by identifier or name is now configured using a switch.

Document preview modules

TEAM-42054 Due to changes introduced in release 2026.4, new versions of the document preview modules for R7-Office, OnlyOffice, and WOPI have been published.

Check the module version in Administration > Modules and update it to the latest version.

Compatible versions for 2026.4:

  • R7-Office—version 2.3 or higher;
  • OnlyOffice—version 2.4 or higher;
  • WOPI—version 1.2 or higher.

Updating ensures correct module operation and compatibility with the new system version.

Security Audit module

With the release of version 2026.4, update the Security Audit module to version 3.0 for correct operation.

Changes in version 3.0:

  • Architecture. The microservice is now part of the module and works through the portable services mechanism.
  • Security. Interaction with the BRIX API has been optimized and protection protocols strengthened;
  • Migration process. After updating the system to version 2026.4 or higher, update the module and configure its connection to the current audit database. After configuration, the standalone Security Audit service can be removed.

Behavior of version 2.4.1:

  • Compatibility. The combination of module version 2.4.1 and the standalone service remains operational in system version 2026.4 and higher.
  • Limitations. The audit history viewer widget in the web interface will not be available.
  • Data integrity. All security events continue to be recorded in the audit database as usual.

#BreakingChangeAlert

Live Chats

  1. TEAM-41361 It is now possible to hide the contents of a specific session, for example if it contains confidential information.

To hide a session, an operator enables the Secret session option on the right sidebar of the session page. The session will remain visible in the Live Chats workspace list and in the Live Chat Conversations widget, but its contents will only be accessible to the supervisor and the session operator.

Other operators cannot take a hidden session into work. The session chat is marked as secret, and users see the message: “Secret chat. You do not have permission to view this session.”

If necessary, general access can be restored using the Unhide session option.

  1. TEAM-34669 New options have been added to Administration > Live Chat Settings that allow enabling or disabling popup notifications about new sessions separately for operators and supervisors. By default, these options are enabled.
  2. TEAM-38558 New email handling options have been added to Administration > Live Chat Settings, allowing you to:
  • Quickly preview email text without opening the email page.
  • Return to the live chat immediately after replying to an email without navigating back to the email page.
  • Highlight expanded emails with a gray background. Used when quick email preview is enabled.
  1. TEAM-42154 In Administration > Live Chats, mail connection settings now allow specifying the sender name displayed in outgoing emails.

Telephony

  1. TEAM-38500 Support for configuring a CTI panel for receiving and making calls directly in the BRIX interface has been implemented.

With the the CTI panel, users can:

  • Transfer a call to another employee during a conversation.
  • Put a client on hold, contact a colleague, and then transfer the call.
  • Make outgoing calls with extension numbers when integrated with Asterisk or RunTel.
  • Automatically save calls between employees in Telephony > Internal when integrated with Asterisk.
  • Restrict outgoing call initiation using TS SDK methods.

Any IP telephony provider supporting WebRTC technology can be used. Third-party softphones are no longer required for making and receiving calls.

  1. TEAM-42386 Users can now work with the CTI panel simultaneously across multiple browser tabs. There is no need to keep the main tab where telephony was connected open specifically for this purpose. As long as that tab remains open, the CTI panel will also stay active in other tabs. If the main tab is closed, the CTI panel disconnects in all browser tabs.
    Simultaneous CTI panel operation is only supported within a single browser and for a single user.

User authentication

TEAM-41369 Users can now click the eye icon on the login page to view the value entered in the Password field. Passwords remain hidden by default.

TS SDK and API

  1. TEAM-42969 The following API methods have been implemented:
  • /scheme/namespaces/{namespace}/reports retrieves workspace reports;
  • /scheme/namespaces/{namespace}/reports/{code} retrieves report metadata by workspace and contract code.

The System.scheme.report.* service has been added to TS SDK for the same functionality.

  1. TEAM-42177 The pub/v1/app/items/batch API method has been added for bulk saving items from multiple apps.

The method allows retrieving a list of app items with pseudo-identifiers in the $ref/xxxx format, where xxxx can be any string. When items are saved, such identifiers are converted into UUIDs.

Pseudo-identifiers can also be used to link app items. To do this, pass the pseudo-identifier of the app item into the relation field.

Request example:

{
  "items": [
    {
      "namespace": "apps",
      "code": "app01",
      "context": {
        "__id": "$ref/1",
        "dependedApp02": [
          "$ref/2"
        ]
      }
    },
    {
      "namespace": "apps",
      "code": "app02",
      "context": {
        "__id": "$ref/2",
        "dependedApp01": [
          "$ref/1"
        ]
      }
    }
  ],
  "withEventHandlers": false
}

Response example:

{
  "error": "",
  "pseudoIDsMap": {
    "$ref/1": "f23c2673-b8b4-4bf6-b543-3d0c6bcb99b3",
    "$ref/2": "e7705800-65e6-43c6-9af0-fadaffe277eb"
  },
  "savedItemsCount": 2,
  "success": true
}

  1. TEAM-37434 The following new functions have been added to TS SDK client scripts:
  • System.voip.generateCall makes an outgoing call through telephony.
  • System.voip.getConnectedProviders retrieves a list of available telephony providers that can be used for calls.

Using these functions in scripts allows restricting outgoing call initiation when using the telephony CTI panel. For example, users can only call a customer for a deal at a specific stage.

Bugs fixed

  1. TEAM-7493 If an Event-type app was deleted, events from this app continued to appear in Calendar > My Events without the ability to delete them. Deleted app events are no longer displayed in the calendar.
  2. TEAM-40360 Fixed incorrect week numbering in the calendar.
  3. TEAM-41937 If a table was configured with the Fit Table to Window option enabled and placed on an app form, text input fields were not displayed across the full column width.
  4. TEAM-40949 If an external user was added to the portal using a script, then locked and unlocked, they could not sign in to the portal using the invitation link.
  5. TEAM-42553 The Portal Navigation widget was missing from the widget list in the portal designer. The widget is now available.
  6. TEAM-42639 In Event-type apps, changes made through scripts were not updating the system properties Start date, End date, and Participants.
  7. TEAM-26194 Validation during internal user creation worked incorrectly. If the email field was left empty and Send Invitation was clicked, the required field validation message was not displayed.
  8. TEAM-38932 Fixed an issue where an event handler in a module was deleted during solution installation.
  9. TEAM-42980 The function configured in the Event after value change option was not triggered for Category-type fields.
  10. TEAM-38885 In the table view of an app item list, it was impossible to select and copy table cell content.
  11. TEAM-42117 If a nested property from another app was added to an app form and its value in the Name on form parameter was changed, the configured value was not displayed.
  12. TEAM-38504 If an app contained a Folder-type field with nested folders, the available actions menu did not open when clicking the three-dot icon in the folder list.
  13. TEAM-39890 Fixed behavior of approval sheets when an approval task was reassigned to a user who was already included in the sheet and had already made a decision. Now:
  • The sheet is closed if no other approval tasks remain after reassignment.
  • The previously submitted resolution remains displayed in the sheet and is no longer reset.
  1. TEAM-41808 If a document view form was created and the settings of the Document Versions widget were opened, the linked document file was not displayed in the File from context field.
  2. TEAM-42275 When restoring a file or document version, the comment was incorrectly added to the latest version instead of the restored one.
  3. TEAM-42422 Fixed an issue where a notification about a missing certificate was displayed when signing a document with a NUC certificate, even though signing completed successfully.
  4. TEAM-42481 If tabs were used on a custom Document app form and File-type fields were placed inside them, field values were displayed incorrectly or the fields appeared empty.
  5. TEAM-41319 A new approval sheet or list of informed users is now created when transitioning from the Approval or Send Document / App Item block under one of the following conditions:
  • The sheet is archived.
  • The approval object is not found.
  • There is no access to the object.

Previously, errors occurred because the process automatically attempted to use an archived sheet.

  1. TEAM-40987 If a process configured to start when creating a new session used a script with the System.company.url parameter, the company identifier was incorrectly written to the parameter when a company alias was configured.
  2. TEAM-41514 Emails with content larger than 16 MB and embedded images were not delivered in the Live Chats workspace. Large embedded images are now automatically converted into attachments, and links or text placeholders are displayed instead. Such emails are now delivered successfully.
  3. TEAM-42511 Fixed highlighting of operator message backgrounds in the Send Message to Live Chat widget in the mobile app.
  4. TEAM-42960 Fixed an issue where the Account property was used on a property form and users could select an account type that did not match the form settings.
  5. TEAM-43195 Notifications were added to session pages in the Live Chats workspace for sessions created from channels connected to email, informing users about actions available.
  6. TEAM-42202 In project plans, tasks were marked as overdue on their due date instead of after it had passed.
  7. TEAM-38722 Only .po files can now be uploaded on the Translations tab in custom module settings. Button labels were also updated to Upload PO file and Export PO file.
  8. TEAM-41322 After installing a language pack and changing the interface language in the user profile, some menu items from the installed package remained untranslated.
  9. TEAM-42256 After installing a custom language module, date formats and month names on some system pages were not translated.
  10. TEAM-24904 If a previously configured String-type field value was changed in business process block settings and the block was closed without saving, the modified value was still saved. Fixed for the following blocks: Create App Item, Edit App Item, Assign Value, Generate from Template, Set Indicator Value, "Meeting" task, "Webinar" task, and "Email" task.
  11. TEAM-24560 If an app was specified in the Variable field of the Create App Item block settings and then replaced with another app, the Field values option still displayed properties of the first app instead of the second one.
  12. TEAM-42368 Fixed a situation where errors occurred and tasks from interrupted or completed process instances could not be closed. Tasks can now be closed if all conditions of this scenario are reproduced. Under normal process interruption or completion, no manual task closing is required.
  13. TEAM-42450 In imported apps, approval tasks in processes created at the app level could not be reassigned to another user.
  14. TEAM-43040 If a workspace was exported, then changes were made to a widget server script within the workspace, importing the workspace caused a widget compilation error when server dependencies were missing. The error no longer occurs during import.
  15. TEAM-39418 Fixed an out-of-memory error that occurred when signing files larger than 100 MB using the CryptoPro, Kontur, or SES module.
  16. TEAM-41549 In the table view of app items, the Registration number field could not be used for sorting.
  17. TEAM-42087 Fixed the System.templater.generateText method. Using the BaseApplicationItem parameter no longer causes an error.
360010947000.html 2026_3.html