search string side menu

New releases > BRIX SaaS / 2025.8

2025.8

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

After September 18, 2025, 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.

Data types

  1. TEAM-36660 For the Arbitrary App field, it is now possible to select multiple items from one or more apps at once. In the window for adding items, you can check the desired entries or select all items in the app.
  2. TEAM-3426 The Folder data type has been implemented. You can add a field to the app or page that will display a link to the folder with documents from the Files workspace.

Widgets

TEAM-29158 In the Field widget, you can now set its name on the form using a variable from the context. To do this, click the paperclip icon next to the field and select the desired properties. This feature is useful if the string name needs to be dynamic, for example, if it changes depending on the company’s language.

Delete app items

TEAM-14152 Permanent deletion of app items from the system along with their links has been implemented.

To do that:

  1. The item is softly deleted from its page or using a bulk delete action.
  2. The user goes to the list of deleted items, applying the Deleted filter in the search window.
  3. On the opened page, you can delete items without the possibility of recovery:
  • One item: open its page and click the Delete permanently button.
  • Several items: select the records on the page and apply the Delete permanently bulk action.

To enable this feature, contact technical support to activate the feature flag.

Structure versioning

If the allowVersionsSnapshots feature flag is enabled in your company, the following features are available:

  1. TEAM-37674 Created and stored versions of registration settings when they are changed in a Document type app.
  2. TEAM-36007 Added saving of version history in the Projects workspace for the Project Types app. A version is created when certain app settings are changed. It is possible to restore the previous version of the base project type and apply it as the current one.
  3. TEAM-35989 The version storage mechanism has been updated for app forms and widgets. The following actions are now available in the version history: compare with the current version, download the version as an .e365 file, unpublish, and restore the version.

Process and error monitor

  1. TEAM-18309 On the Process Monitor page, the list of instances now displays the current version of the process where the instance is running.
  2. TEAM-36668 On the Process Monitor page, active instances with malfunctions, such as prolonged execution of an automatic action during a process, are now highlighted in yellow. You can immediately identify such an instance, see at which step the process stopped, and optimize its settings.
  3. TEAM-35554 In the Administration > Business Processes workspace, a setting has been added to display processes created within remote apps and workspaces. To do this, click the gear icon in the upper right corner of the page and enable the display of the Other processes folder.
  4. TEAM-36246 The Migration button has been added to the Error Monitor page. It triggers the update of data in the table and the addition of instances with errors that occurred before the enableUpdatedErrorListMonitor feature flag was enabled in the company.

The feature flag activates the updated error monitor with the ability to search for instances by parameters, view error text, customize the table appearance, and sort records in it.

Document management

  1. TEAM-29465 The View only option has been added to the File List widget settings. It allows you to restrict access to actions with files displayed in the widget. When this option is enabled, users will only be able to open the file view page.
  2. TEAM-35861 Improved user experience when working with file versions in apps such as Document or on the document view page from the Files workspace.

Previously, users could only download previous versions of the file to their computer.

Now, from the Document Versions widget, you can open any version of the file in a separate window. Here, you can view information about the file, correspondence in the activity stream for a specific version of the file, make the version current, download or delete it, and compare it with previous versions for .doc or .docx documents.

  1. TEAM-36880 In the Approval activity on the Signature tab, you can now configure the comments addition from the user who signs the file or its attributes in the approval task.

You can select the following options: Do not use, Optional, Preferred, Required.

  1. TEAM-37034 For issuing simple e-signature certificates during the business process, the Request Signature activity settings have been adjusted:
  • On the General tab, the Phone and Middle name fields are now optional. The certificate can be issued without specifying a phone number, however, if two-factor authentication is enabled for signing with a simple e-signature, the user will see an error about the missing phone number when performing the task.
  • On the Personal ID tab, when selecting an e-signature provider, only the Document number field needs to be filled in.
  1. TEAM-38018 The interface appearance in the approval sheets and lists of informed users has been improved. Now, if the user does not complete the task independently, the following is displayed next to their name in the sheet:
  • If substitution is configured: a red arrow and the substitute name are displayed.
  • If the task is reassigned: a blue arrow and the name of the new performer are displayed. When you hover over the arrow, tooltips are displayed: Reassigned, in progress or Reassigned.
  1. TEAM-29309 Improved user experience when configuring sorting settings in the Files workspace. You can now access the settings by clicking the gear icon in the upper right corner of the page.

Table approval routes

TEAM-34364 The ability to configure approval routes with multiple stages and different executors and send any type of app items along them has been implemented.

This feature is activated using the enableApprovalRoute feature flag.

The basic principle of working with table approval routes is as follows:

  1. A special Approval route activity is added to the business process. The process is linked to the app.
  2. The Approval routes widget is placed on the forms for creating or editing this app.

When creating an item, users specify the approval route in the widget: they manually add any number of approval stages and assign executors for each of them.

After starting the process linked to the app, when it reaches the configured activity, the item is approved taking into account all the stages specified in the page.

  1. The View approval routes widget can be added to the app view form.

Then, on the item page, users will be able to see which approval stages are configured for the item.

  1. Optionally, at the preliminary settings stage, you can install the Approval routes business solution from the official BRIX Store catalog.

It includes a system directory where you can create approval route templates, link a route to a specific app in the system, or make it general.

Then, on the app form in the widget, the employee selects a ready-made route from the directory, adjusts it if necessary, and starts the approval process.

Projects

  1. TEAM-22921 The option to create tasks in a project plan using the copy option has been implemented. Tasks can be copied while retaining related and nested tasks.
  2. TEAM-34825 In the project creation page, the Completion date field is now required. Previously, if the field was left blank, the completion date was set automatically and incorrectly.

In addition, to improve the user experience, a hint has been added for filling in the Use business calendar field.

  1. TEAM-34903 The ability to close multiple project tasks that are under the user’s control has been implemented. You can select the desired tasks in the list and accept their completion or return them to work.
  2. TEAM-37735 The ability to select multiple project plan items and perform bulk actions on them (copy or delete) has been added.

Service

  1. TEAM-31861 Added the ability to display all TelegramBot channel sessions in the Live Chat Messages widget.

Previously, if a client without a public name (no username specified in the settings) wrote to the live chat, the client account value in BRIX was empty. Such sessions were not displayed in the Live Chat Messages widget with the By account link.

Now, for a client whose phone number is hidden and no public name is specified, the external Telegram user ID is transferred to BRIX as the account. Using the session ID, you can display the client in the Live Chat Messages widget, search for the client, and initiate a session in the line with Telegram and TelegramBot channels (taking into account the client’s privacy settings).

  1. TEAM-32191 Changed the logic for processing and storing files sent by the client from the LiveChat window connected to the live chat. Now image files are available for preview in the chat, they can be zoomed in, downloaded to a computer, or printed. When you click on a file of a different type, it will automatically download to your computer.
  2. TEAM-32213 Automatic updating of links to files sent by the operator to the live chat from LiveChat has been implemented. Now, files sent by customers are always available to them in the LiveChat window.

Even if the file link has expired, the customer can click on the file icon in the chat to update it and then view or download it. However, if the file has been deleted from storage, the user will see a notification that the file is unavailable.

  1. TEAM-33032 The ability to enable client identification by JWT token has been added to the LiveChat channel settings. This will allow you to identify the user even if they use different browsers or devices and download the chat history.

If automatic authorization is configured in LiveChat, updating and verifying the user’s JWT token can be used as additional protection against unauthorized access.

  1. TEAM-37100 A new message indicator from the operator has been added to LiveChat on the website. The client can see it on the button that opens the LiveChat window.
  2. TEAM-34302 The allowExtendedInboxMode feature flag has been removed, as starting with version 2025.8, the new interface for processing messages from the email client in sessions is available by default. For more information on working with such messages, see the official BRIX help.

CRM

  1. TEAM-24939 In the event handler settings for the Tasks event type domain, it is now possible to select custom CRM tasks.
  2. TEAM-37182 The logic for searching for overlapping events when creating CRM tasks has been improved. Now, if tasks follow one another, i.e., the end time of one task coincides with the start time of the next, this is not considered an event overlap.

Business solutions localization

TEAM-37354 Added the ability to disable comparison of the user language and the source language of the imported component. This was implemented to avoid blocking administrator settings for localized workspaces and apps.

To use this feature, you need to:

  1. In the target company to which the localized solution will be imported, disable the comparison of the user language and the component using the environment variable setting. To do this, contact technical support.
  2. In the current company, configure the solution in the source language and prepare localization for it.
  3. In the settings of the current company, change the language to the localization language.
  4. Export the solution.
  5. Import the solution into the target company.

Administrator settings will be available for the components of the imported solution.

TS SDK and API

TEAM-34254 A new property called inboxPayload with the Read only option has appeared in the TS SDK session message model, which stores:

  • The email subject (string): subject.
  • The sender (link to the app item with clients): from.
  • Recipients (array of links to app items with clients): recipients.
  • Recipients in copy (links to app items with clients): cc.
  • Recipients in blind copy (links to app items with clients): bcc.

The property is filled in messages from sessions created with the allowExtendedInboxMode feature flag enabled or after updating the system to version 2025.8.

Bugs fixed

  1. TEAM-35241 When editing a template page of an external portal in the interface designer, the following error occurred: “An error occurred in the portal.template.widget.name@_portal-header-logo widget when calling the onInit method”. This error occurred if the portal was created within the workspace exported from another company. The issue has been fixed.
  2. TEAM-37296 Fixed an issue where users who were not members of the Administrators group could access the external portal settings page by going to its direct URL.
  3. TEAM-37582 The layout of the external portal settings window on the Authorization tab has been fixed.
  4. TEAM-37079 Fixed an issue where validation was triggered when filling in the Phone number field on the form when the extension code was specified using the ext separator. Now, the # symbol can also be used as a separator.
  5. TEAM-37326 If a Number (integer) property was specified in a script, its value could change, resulting in a fractional or rounded number being displayed. Now the value is displayed correctly according to the property subtype.
  6. TEAM-37360 Fixed an issue where the user was not shown a notification about unsaved changes when exiting the action settings in business processes of the Script type created within the module.
  7. TEAM-37393 Fixed an issue where EQL queries of the NOT [string] IS NULL or NOT [string] IS EMPTY form for searching the String field were executed incorrectly. As a result, strings with empty values were returned. Now, such a query can find all items in which the specified string field is filled in.
  8. TEAM-37868 Fixed a configuration export issue that occurred the day after a company was created.
  9. TEAM-37956 When calling an API method created within the module in a script, the data in the query parameter was not displayed. The issue has been fixed. Now, in client and server scripts, the query parameter is sent to the server and can be retrieved in the response.
  10. TEAM-38115 TEAM-38115 Fixed an issue where the task end date and time were calculated incorrectly if the time format was changed in Administration > Locale Settings.
  11. TEAM-38151 In the Low-code CI/CD tool for exchanging components, the ability to link an external company to the current one by its IP address has been added. Previously, when attempting to set up such a connection, a format error for the entered value was displayed in the link creation window.
  12. TEAM-29231 To improve the user experience in the interface, the App (multiple) field display on the form has been corrected. Now the item search bar is located above the list of already selected records.
  13. TEAM-16977 When access to the Document Categorization workspace was restricted, the user was able to open it via a direct link. This issue has been fixed. Now, when navigating to the workspace via a direct link, access permissions are checked. If there are no permissions to the workspace, the user will be redirected to the main page of the system.
  14. TEAM-16983 The Sign button remained active if the user signed the current version of the file. The issue has been fixed:
  • Now the signing widget and the Sign button are displayed depending on the app type, signing settings, and file version.
  • The “No signature type selected” error is now displayed when attempting to sign a Standard app item during the process if the following settings are specified in the activity: Sign attributes > Do not use, Sign file > Required.
  1. TEAM-19011 Fixed an issue where a user could restore and move a file in a folder for which they did not have the permissions to create and edit files. Now, when attempting to move or restore a file, the user will see a notification that they do not have the necessary permissions.
  2. TEAM-36823 If watermark printing was enabled in a Document type app, and then an item was created and a file was uploaded as part of a business process, the file could not be viewed in subsequent stages of the process. The issue has been fixed, and documents with watermarks are now displayed correctly in the view form.
  3. TEAM-37917 In the File List widget, it was possible to navigate to top-level folders if the Limit root directory option was enabled in the settings and the My Files folder was selected for display.

This issue has been fixed. Now, if you do not have access permissions to the linked folder, the widget displays the following notification: “Access to the folder is prohibited or it has been deleted. Contact your administrator.”

  1. TEAM-38380 When opening the file view page, the sidebar with information is displayed by default if there are approval or review tasks assigned to the file. Previously, the panel was hidden and only displayed if there were completed tasks with a resolution.
  2. TEAM-25613 In the Files workspace, automatic data updates have been added when performing actions with items via the context menu that opens when you click the three dots icon. Previously, you had to refresh the page manually after performing the Rename or Add Version actions.
  3. TEAM-31573 In the settings for the Convert to PDF, Insert Watermark, and Generate from File activities, the tooltips indicating the supported formats for input documents have been updated.
  4. TEAM-36531 Fixed an issue where the provider parameter values were displayed incorrectly in the Sign activity settings when reopening the business process designer to edit a page.
  5. TEAM-36978 Fixed an issue where the configured filtering on the Email workspace page was reset after viewing a message, closing its page, and going to the list of all messages.
  6. TEAM-37177 In the user module for integration with IP telephony, the logic for matching provider users and BRIX users has been corrected. Previously, when changing matches in the script using the VoipGetMembers() method, they were not updated in the settings interface. Now only current mappings are shown in the settings.
  7. TEAM-37350 Fixed and issuer where call records were incorrectly added to the Calls app items.

The callId field, which is the call identifier in the external system, has been added to the methods for user modules for integration with VoipWebhookRequest and VoipCallRecord IP telephony. It is used to map multiple telephony events to a single call in the Telephony > Calls workspace. If the field is filled in, call records are correctly linked to app items.

  1. TEAM-38268 When using telephony, the user did not see the list of missed calls in the window that opens when clicking on the phone icon in the upper right corner of the page. The issue has been fixed.
  2. TEAM-11191 If the Allow executor to reassign the task to another user option was enabled in the new version of the process for a task and an already running instance was updated, the new settings were not applied to it. The reassign option was not available for tasks.

This issue has been fixed. The logic for checking the possibility of reassigning a task in the process has been corrected.

In addition, the ability to reassign tasks with the First Response option has been added. Previously, this was only available when selecting a task from the list. When reassigning, all users who were considered executors are replaced by one employee.

  1. TEAM-15715 Fixed an issue where the start event form in the business process did not display the additional properties of the app, only a link to the app item itself.
  2. TEAM-32062 In the Administration > Business Processes workspace, copying to another workspace was not applied for processes created within the module. This issue has been fixed.
  3. TEAM-37275 Fixed an issue where the instance page displayed a notification about a successful process version update, even if the action could not be performed. Now, if an error is detected during the update, the correct notification about it is displayed on the page.
  4. TEAM-37732 If a parallel gateway was configured during the process, the swimlane was assigned incorrectly, and System was specified as the executor in the tasks. This issue has been fixed.
  5. TEAM-37782 Fixed an issue that prevented tasks assigned during a business process from opening in some cases. Users could not view the task page:
  • If the process context contained an App type variable that specified a remote app.
  • If an App type field was added to the task form and an item was selected in it that the task executor did not have access to. At the same time, the Prevent save conflicts option was enabled in the linked app settings.
  1. TEAM-37893 When updating a workspace to a new version, conflicts were detected in the business processes included in the workspace. The date of the process change was not displayed in the window showing the detected conflicts. This issue has been fixed.
  2. TEAM-30279 Fixed the assignment of the update date when restarting a business process instance. Now the date is specified according to the time zone in the system.
  3. TEAM-37479 Fixed an issue where the second AD server domain was not added in the Active Directory module settings.
  4. TEAM-37608 After the specified user inactivity limit expired, /api/auth/substitutions/list requests were created in the system to release concurrent licenses, which caused user activity. As a result, licenses were not released. This issue has been fixed.
2025_9.html 2025_7.html