2026.7

BRIX On-Premises 2026.7 includes all updates from intermediate BRIX SaaS 2026.5, 2026.6, and 2026.7 releases. For more information about changes to the release cycle, see the official documentation.

 

What to check before installing the release

The #BreakingChangeAlert tag indicates changes that may impact your existing configuration: processes, interfaces, scripts, or integrations may behave differently. Manual reconfiguration is not always required, but affected scenarios should be verified before installing the release.

The BRIX SaaS update in which the change was first introduced is indicated in square brackets next to the task number.

All changes in release 2026.7 marked with this tag are listed below.

  1. TEAM-44552 [SaaS 2026.7]. Starting with release 2026.7, Design V2 is used by default. You can temporarily revert to V1 in Administration > Theme. Starting with version 2026.11, the V1 design will no longer be available, so please check and adapt your user interfaces in advance.
  2. TEAM-42463 [SaaS 2026.5]. Handling of non-critical errors in business processes has been changed. Now, such errors, such as service unavailability, interrupt the process. The system administrator receives an error message and decides whether to continue the process.
  3. TEAM-42555 [SaaS 2026.6]. Settings of connectors in business process activities have changed. A separate connector is required for each action or event. If a primary connector from the block is not configured along with time-based escalation, the process cannot be published. The Interrupt option is considered disabled if the next step is not set for it.
  4. TEAM-39233 [SaaS 2026.6]. Status groups have been added for apps. As a result, the interface for configuring lead and deal pipelines in CRM has been changed. If your configuration uses pipelines, check their settings after installing the release.
  5. TEAM-26149 [SaaS 2026.6]. Fixed an error when the process linked to the Save button on the item creation form might not start if the user closed the page immediately after saving. The process now starts in this case as well.
  6. TEAM-31038 [SaaS 2026.7]. Changed the logic for recursively terminating subprocesses using a script from the parent process. By default, terminating no longer causes an error. You can revert to the previous behavior using the processor_enable_scriptTerminateInstanceDeadlock feature flag.

Key changes in release 2026.7

This topic describes a brief summary of the most notable functional changes in the release. They are grouped by system area. You can find full descriptions of all changes and fixed bugs at the end of this topic.

Apps and data management

  1. TEAM-506 [SaaS 2026.5]. In advanced app search, you can specify multiple conditions and combine them with AND and OR operators.
  2. TEAM-43516 [SaaS 2026.7]. When searching by conditions, you can use nested properties of a linked app. For example, search for requests by the region of the linked counterparty. This feature is enabled using the app_enable_subfieldFiltration feature flag.
  3. TEAM-43862 [SaaS 2026.7]. Working with status groups requires a separate license. Previously configured groups will continue to work, but without a license, you won't be able to edit them or create new ones.

Business processes and solutions

  1. TEAM-42394, TEAM-35997, TEAM-38272 [SaaS 2026.6]. Version management for solutions, modules, and API methods has been added. You can capture version composition, compare versions, and restore archived versions. This feature is enabled using the allowVersionsSnapshots and exp_exchange_enable_packageVersions feature flags.
  2. TEAM-38803 [SaaS 2026.6]. The Approval Routes and View Approval Routes widgets can be placed on the custom form of a business process task.

Documents

  1. TEAM-43016 [SaaS 2026.5]. File versions are divided into Current, Outdated, and Deleted statuses.
  2. TEAM-42870 [SaaS 2026.5]. Outdated file versions can be soft-deleted, restored, and, if necessary, permanently deleted.
  3. TEAM-43032 [SaaS 2026.6]. Draft document versions are added.

Email and Service

  1. TEAM-27510 [SaaS 2026.6], TEAM-43680 [SaaS 2026.7]. Automatic email linking can be configured for any number of apps containing the Email-type field. Previously, linking was only available for the Contacts app, and then there was a limit of five apps.
  2. TEAM-43892 [SaaS 2026.7]. A business process can be launched from the email page and email data can be passed to it.
  3. TEAM-31445 [SaaS 2026.7]. Users can create personal live chats, connect communication channels to them, and communicate with clients.

TS SDK and Web API

  1. TEAM-43264 [SaaS 2026.6]. Methods for skipping and restarting process steps, including bulk processing of instances, have been added to the Web API.
  2. TEAM-40870 [SaaS 2026.5]. The System.applications.batch() method has been added to the TS SDK for bulk saving of associated items from different apps.
  3. TEAM-35774, TEAM-38011 [SaaS 2026.6]. Methods for bulk status changes and permanent deletion of app items have been added to the TS SDK. The hardDelete() method applies only to soft-deleted items and can be enabled by contacting BRIX technical support.

Additional changes in BRIX On-Premises 2026.7

In addition to the new features released with BRIX SaaS 2026.5–2026.7 updates, the current release includes the following changes:

  1. The BRIX On-Premises 2026.4 Long-Term Support (LTS) version has been locked.
  2. Support for the Gateway API has been added to BRIX add-ons. This ensures compatibility when migrating from Ingress-NGINX.
  3. Infrastructure fixes have been implemented to improve the stability of platform components.

Full list of changes included in the release

2023_10.html 2026_4_op.html