﻿# 2026.10

> [HTML Version](2026_10.html)

Here is the list of changes that you can explore right now by activating the BRIX trial version.

The current 2026.10 release is a major release. After November 17, 2026, the update will become available to clients using BRIX SaaS and BRIX On-Premises. Please note, further changes may be added to the list later.

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.

## Apps

1. TEAM-41175 New options have been added to the **Table** display mode on app pages:

- Display nested properties of **App** and **Users** fields to show data from linked apps or user information in the table. For example, if the **Companies** app has a field linking to the **Contacts** app, you can display the linked contact's **Phone number** field in the companies table. Only first-level nested fields are available.

- Set custom column names that differ from the field names.

2. TEAM-41198 You can now configure a custom search form for app items. This lets you remove unnecessary fields, group them on the form, and more.  
This feature is available when the `application\_enable\_searchCustomForm` feature flag is enabled.  
In advanced form settings, on the **Search** tab, you can enable and configure one of two types of custom search forms:

- Simple form. Select the fields used to search app items and set their order. When this option is used, employees cannot use filters.

- Advanced form. In the interface designer, create a custom widget where you select search fields, group them, add buttons or links, etc. Then, configure a client script with system functions for the widget to define search behavior:

	- Search function. Required. Defines search conditions using the `Application.createFilter()` method.

	- Clear search function. Optional. Configures resetting parameters to default values. If not defined, fields are cleared using the system mechanism.

	- Get and apply search context functions. Optional. Configure saving and applying filters. If not configured, the system mechanism is used.

## System interface design

TEAM-45031 You can now configure design tokens to customize the visual style of the system directly in the BRIX interface without writing CSS code.

A design token editor has been added under **Administration > Theme**, allowing you to define colors, fonts, and the sizes of interface elements. The editor also lets you preview a new theme before publishing by applying it only to specific users.

## Tasks

TEAM-25155 You can now display information in a table format in the **Associated Tasks** widget. In the widget settings, you can configure columns and manage record filtering and sorting.

## Interface designer

1. TEAM-44433 Improved the display of the **Text box** widget in the interface designer. If its displayed text is bound to a **String** field with no value set, the template displays the field name with % symbols instead of an empty container, for example: `% Client name %`. This lets you identify the widget's content without opening its settings.  
If the **String** field is not empty, its value is displayed in the widget.

2. TEAM-38038 In the interface designer, nested properties of **App** and **Users** fields can now be made editable. You can add them to a form or a widget placed on a form.  
Employees can then edit the linked item's data without opening its page. Once the form is saved, the information in the linked item is automatically updated.

3. TEAM-34034 When configuring widget visibility using the **Show for groups** option, you can now disable permission inheritance based on org chart. To do this, the **Consider the organizational chart** option has been added to widget settings.  
Previously, the widget was always visible to supervisors of users in the specified group.

## Document management

1. TEAM-24442 Search in the **Files** workspace has been improved to match the search in apps. The following options have been added: search by parameters and by conditions, EQL search, and filter usage. You can also switch between searching only files and only folders.

2. TEAM-41618 In the business process designer, you can now enable or disable notifications about task assignment and signing results for the **Sign** activity.  
Please note that in processes published in system versions earlier than 2026.10, signing task assignment notifications will continue to be sent if the **Send notifications about new tasks by email** option is enabled in the user's profile. To completely disable notifications, enable and then disable the **Task assignment notification** option in the **Sign** activity settings, and then publish the process.

3. TEAM-44716 You can now send a specific version of a file or **Document**-type app item for approval and information. The following options are now available for versions:

- Send for approval and information from the BRIX interface. A **Send** button has been added to the version view form.

- Approval and review during a business process.** **Using a script, you can retrieve a document version with the `getVersions()` method and save it to an **Arbitrary App**-type variable for approval. If a draft is sent for approval, you can set it as the current version using the `setAsCurrent()` method.

- Archiving an approval sheet or a list of informed users. When editing a draft version, associated sheets or lists are archived.

## Live Chats 

1. TEAM-44965 In the business process designer, you can now configure Cc and Hidden copy recipients and specify recipients to exclude from the recipient list in the **Send Live Chat Response** activity.

2. TEAM-43907 When a user account is blocked, connections across all communication channels in their personal live chat are automatically terminated. Sessions in these channels are closed but remain saved in the system.

## CRM

1. TEAM-33268 In the business process designer, you can now send two types of email copies to additional recipients in the **Email Notification** activity:

- Cc. Additional recipients are visible to all conversation participants.

- Hidden copy. Recipients are hidden from other participants.

2. TEAM-45652 Added a license for the** Duplicate Objects in apps** tool, allowing you to search for and handle duplicates outside the **CRM** workspace.

3. TEAM-45055 In the **Telephony** workspace, you can now identify a contractor not only by a linked contact from the **CRM** workspace, but also by any app that has a field linking to the **Companies** app. To do this, specify that app in the **Contractor** field under **Administration > Call Settings**.  
When handling an incoming call, if an employee selects a linked item from the specified app, contractor information is added from its page.

## Authentication

1. TEAM-25809 You can now use authenticator apps such as Google Authenticator, Authy, and others for two-factor authentication in the system. These apps generate one-time authentication codes on the user's device without transmitting data over the network, enhancing security.  
The system administrator enables authenticator apps as a second factor under **Administration > Security Settings**. Users can then connect their preferred app in their profile settings.

2. TEAM-44410 When a blocked user attempts to log in, two-factor authentication is no longer triggered and an error is displayed immediately. This helps reduce costs associated with supporting a second authentication factor, such as sending SMS messages.

## TS SDK and API

TEAM-45663 In server scripts, methods for bulk adding, updating, and deleting app items now run with system administrator permissions. The current user's permissions to import data into the app are no longer required to perform these operations. 

In client scripts, import permissions are still checked before performing bulk actions.

**\#BreakingChangeAlert** 

## Bugs fixed

1. TEAM-41785 When a user opened an **Event**-type app containing a large number of items (more than 10,000), records would sometimes fail to appear.

2. TEAM-44090 In the **Calendar** workspace, users could create a recurring event with an end date earlier than or equal to the start date. An error is now displayed when invalid dates are entered.

3. TEAM-45965 If a user created an event in the **Calendar** workspace  and then edited its start date, the changes were not saved.

4. TEAM-44129 In the **Calendar** workspace, if a user moved an event and the new time slot partially overlapped with the original one, a warning appeared stating that the event overlapped with itself. The current event is now excluded when checking for overlaps.

5. TEAM-45966 Fixed an issue in the **Calendar** workspace when canceling an event move. If a user manually moved an event so that it overlapped with another longer event, a warning window appeared. Clicking **Cancel** still moved the event. Now, canceling the action discards the changes.

6. TEAM-39799 Pop-up notifications confirming that the action succeeded are now displayed when creating and publishing an event handler in a module.

7. TEAM-45774 Removed unnecessary text above the **Field Exclusions** table in app signature settings.

8. TEAM-45238 In the BRIX desktop app, an issue with displaying `.pdf` files incorrectly in view mode has been fixed. Instead of the document text, a string of garbled characters was displayed. 

9. TEAM-45667 In the **Files** workspace, the checkboxes next to files and folders  are now aligned with the other elements on the page.

10. TEAM-45909 An issue has been fixed with populating a **Users **type field when the **Read only** option was linked to a **Yes/No switch** variable. If an employee selected a user in this field on a form and then used the variable  to disable and re-enable editing, the selected user was cleared from the field. 

11. TEAM-37580 When deleting a document registration record using the `deleteRegistration()` method, the registration number was not removed from the document's `\_\_register\_name` system field. The number is now removed in this case.  
Please note that if a document was registered multiple times with the same registration numbers, all matching numbers are removed when the method is called.

12. TEAM-45678 If a document was signed using a script with the `uploadSign()` method, an error could occur when calling the `getDetails()` method to retrieve detailed information about the signature. The issue has been fixed.

13. TEAM-45808 In the **Files** workspace, sorting in the recycle bin did not work correctly when there were more than 50 deleted files.

14. TEAM-45869 In the **Files** workspace, access to subordinates' documents for supervisors based on the org chart was fixed. The following now open correctly:

- The **Users** folder, which contains all documents that subordinates have added to their **My files** folders.

- Subordinates' folders via direct links.

15. TEAM-46098 Fixed an error when comparing versions using the WOPI module where the comparison file failed to display.

16. TEAM-43409 When a session in a live chat with a connected email account was assigned to an operator via a script using the `assignToOperator()` method, the email action buttons were not displayed in the  **Live Chats Messages** widget until the page was refreshed.

17. TEAM-45795 In the **CRM** workspace, the **Delete** button did not work in app item pages in the **Deals** app. A deletion notification was added in the activity stream, but the item was not deleted.

18. TEAM-45892 In the **Live Chats** workspace, after listening to a voice message in full, attempting to play the file again displayed a notification stating that it was not found or had been deleted, and the file only became available again after reloading the page. Voice messages in live chats can now be replayed without refreshing the page.

19. TEAM-45976 In the **CRM** workspace, the **Most Recent Activity** widget on all deal pages displayed the date 01.01.0001. It now displays the correct date of the last interaction with the deal.

20. TEAM-46092 In the **CRM** workspace, task management buttons on **Meeting**-type task forms were displayed to task participants even though only the executor could use them. For example, if a participant clicked a button to close the task, the specified completion result was recorded, but the task remained open. The buttons are now hidden from participants.

21. TEAM-32788 If a checklist was added to a task assigned during a business process, its items appeared under **Tasks > **. Attempting to open checklist items from this section caused an error and froze the page. Checklists are no longer displayed in the **Assigned by Me** group and are only visible on the pages of the tasks for which they were created.

22. TEAM-45576 Fixed an issue when launching subprocesses during a parent business process. If a step configured to launch a subprocess was executed multiple times, duplicate subprocess instances were mistakenly created. For example, when re-approving a document after a rejection, the subprocess configured in the **Approval** activity was launched again. The subprocess now launches only on the first execution of such a step.

23. TEAM-45608 Fixed an issue that occurred after importing a business process containing an activity configured to launch a subprocess. In the activity settings, on the **Start Process** tab, the **Process** field was empty.

24. TEAM-45633 Fixed validation for API requests to start a process. If an invalid value format was passed for a property in the request body, the response indicated a successful launch and returned an instance ID, even though the process did not start. A validation error is now returned and the process is not started.

25. TEAM-45684 Fixed an issue where a parent process resumed prematurely, before all child processes had finished. If multiple subprocesses were launched without enabling asynchronous execution and one of the instances stopped due to an error, the parent process resumed once the remaining instances finished. The parent process now waits for all subprocesses to finish, including instances with the **Error** status.

26. TEAM-45879 Fixed an issue where a process stopped with the **Waiting** status if a command to stop the processor pod was received while transitioning from one task to another. The process now remains in the **In progress** status.

27. TEAM-46123 If multiple branches were configured in a business process using two inclusive gateways and a **Task** activity was placed after the merging gateway, the task was assigned multiple times based on the number of branches. The task is now no longer duplicated.

28. TEAM-45151 Validation did not work for **Table**-type fields on app item edit forms. If a column was configured as required, no warning appeared when the item was saved with that column left empty, and the changes were saved anyway.

29. TEAM-45337 If sorting by a **Number**-type field with the **Ascending** option was configured in the table view settings on an app page, closing and reopening the page sorted items in descending order instead. The setting is now applied correctly.

30. TEAM-45458 Fixed an issue where the solution version was not recorded when exporting a solution.

31. TEAM-45617 For external users on a portal, an internal user's **Full name** appeared as an empty field on app item pages.

32. TEAM-46112 On an external portal, opening parameter search in the **Table** widget displayed the **Save as Filter** button, which did nothing when clicked. The button is now hidden on the portal.

33. TEAM-45681 Updated the `whatsmeow` library to ensure proper operation of live chats connected to WhatsApp.

34. TEAM-45676  If a value that could not be converted to JSON was assigned to a property of the **Arbitrary type** in a widget's client-side script and then passed to a server-side script, the property was set to an empty value. This value was then assigned to the widget context, which could cause script errors.  
Now, in this case, the property value in the context remains unchanged and server-side processing is skipped. If the value can be converted to JSON, it is passed properly between server-side and client-side scripts.

35. TEAM-43994 On the search form, the names of the **Time**, **Relative Time**, and **Collection Item** functions in the EQL search field were not translated when the interface language was changed.

36. TEAM-44378 If a system administrator's language differed from the company language, date formats were displayed incorrectly in the **Administration > Locale Settings** workspace in the **Date and Time **field . When the **Use default** option was enabled, the available formats in the list were displayed in the company's language. They now appear in the current user's language.

37.  TEAM-45675 Documents in Thai were displayed incorrectly in the **File Preview** widget. This issue has been fixed, and the text is now displayed correctly. 