search string side menu

2025.10

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

After November 19, 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.

System data types

  1. TEAM-26020 For String properties with the Markdown option, you can now preview the text you’ve entered. To test how the markup looks, just hit the Preview button in the bottom right corner of the field.
  2. TEAM-37696 For Date/Time properties, you can now specify the time in a specific time zone on forms. To do this, enable the Use a fixed time zone option when configuring the field and select a time zone.

In scripts, when searching by this property, the time will be converted to a fixed time zone while preserving the values of the year, month, day, hour, minute, and second.

New table version

The new version of table display, which is enabled using the front_enable_vtable feature flag, implements the following:

  1. TEAM-38112 The BRIX mobile application now supports sorting data in tables in the new version.

To sort data in a table, click the three dots icon in the upper right corner of the table and select the sort type: ascending or descending. Then specify the column where you want to sort the data.

To reset the settings, close the table and reopen it.

  1. TEAM-18383 An option has been added to the table settings that allows you to prohibit the creation of new rows. This helps prevent accidental or intentional unnecessary data addition.
  2. TEAM-22797 It is now possible to change the order of rows using the Drag-and-Drop method. This allows you to quickly and conveniently manage the data sequence.

To move a row, click and hold the dots icon next to its name and move the row up or down.

Rows can be moved within a single table. If rows are grouped, moving is only available within the group.

Archiving structures

An option to archive data in system components has been added. This will optimize the load and ensure that users only work with up-to-date data.

This feature is currently in test mode and may be unstable. To activate it, contact technical support to enable the feature flag.

After that, the following functionalities will be available in the system:

  1. TEAM-18676 Archiving app items. The data is not displayed in the interface but is stored on the server side in a separate database table. It cannot be restored.
  • Automatic item archiving. In the app settings on the Item Archive page, the administrator enables the option and sets the archiving rules using the EQL365 language. Automatic archiving runs every 6 hours.
  • Manual item archiving. It is designed for selective archiving of individual items. The administrator can add an Archive button to the app form. Users who have been granted the right to delete items will be able to move items to the archive.
  1. TEAM-32293 Calendar events archiving. Like app items, records moved to the archive are no longer displayed in the system. They cannot be restored.
  • Automatic event archiving. In the calendar settings on the Event Archive page, the administrator enables the option and sets the period (month, half-year, year, 3 years) after which items with the Closed status are automatically moved to the archive.
  • Manual event archiving. The event creator can move it to the archive, regardless of the automatic settings, by clicking the Archive button. It appears on event pages only after the archiving option is enabled in the calendar settings.
  1. TEAM-32270 Completed process instances archiving. It is available only to the system administrator. After archiving, all objects are displayed in the Administration > Process Instance Archiving workspace on the History tab. Here you can view them and restore them from the archive.
  • Automatic instances archiving. On the Process Instance Archiving page, you can set the schedule and archiving rule using the EQL365 language. For example, completed instances of a certain type can be moved to the archive once a week.
  • Manual instances archiving. on the Process Monitor page, the administrator can open the instance page and click the Archive button, as well as select several records with a checkbox and apply a bulk archiving action.

Important: In the On-Premises edition, upgrading to version 2025.10 may take a long time due to the addition of the ability to archive process instances.

Structure versioning

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

  1. TEAM-35994 Creating app versions when changing item numbering settings has been implemented. A new app version is created when the following changes are made on the Counters page:
  • Number assignment method: when opening a form or after saving an item.
  • Numbering type: cross-app or within a single app.
  • Section for cross-app numbering.
  1. TEAM-36003 Versioning has been implemented for the Report component. Component versions are created when the following parameters are changed:
  • Report name or icon.
  • Source settings.
  • Table and list of filters for searching on the report page.

To view the list of saved versions, click the gear icon next to the report name and select Version History. Here you can restore the previous version of the component.

System search

  1. TEAM-36429 EQL search now allows you to create a query with the COUNT function to find identical values in fields within a single app.

Example:

COUNT (FROM [_clients._contacts] WHERE PARENT.[_email] = [_email]) > 1
The Contacts app searches for items that contain identical email addresses and phone numbers.

  1. TEAM-39090 In the Tasks workspace, you can now quickly find the records you need by their author on the My Tasks tab and by performer on the Assigned by Me tab. To do this, enter the employee’s last name in the search bar and press Enter on your keyboard.
  2. TEAM-39516 The Full-Text Search option in the app context settings, which allowed users to find values by partial string match, has been renamed to Quick Search.

Business processes

  1. TEAM-15867 A Description tab has been added to the settings for business process graphical elements. It contains service information for administrators working with the process.

Users can go to the business process designer, open the activity settings, and view its result, as well as the details of the settings specified for it. For example, for the Task activity, you can describe the task purpose, for the Notification activity, you can specify who will receive the notification, etc.

  1. TEAM-34887 In the business process designer, the connector logic when clicking the Back button on the top panel has been improved. Now the user returns to the page from which the process was opened in the designer.
  2. TEAM-37318 A button for updating data has been added to the business process instance page. It is displayed on the top panel as a circular arrow icon.
  3. TEAM-37850 The ability to resume the process instances execution has been implemented, even if they were paused without an error being detected.

When an instance has stopped at a certain step but is not displayed in the error monitor, the user can resume the process. For example, if the task is complete but the connection with the next activity has not occurred, and no explicit error in execution has been detected.

The following improvements have been added to handle such situations:

  • On the Process Monitor page and the instance page, the system administrator can use buttons to skip a step or force an action restart.
  • A button has been added to the instance page to update the current task status.
  • Error checking has been improved. Now, the task status and any text errors that occur are taken into account in order to suspend the instance with the malfunction and display it on the Error Monitor page.

To enable the implemented features, contact BRIX technical support to activate the feature flag.

Widgets

TEAM-25739 Added the Previous Task Executor widget to display the user from whom the task was reassigned, for example, after creating a substitution. The widget is placed by default on the system task form added from the Tasks workspace. It can be moved to the task form template in the business process.

Modules

TEAM-6739 User modules now have the ability to delegate API method execution to a portable or external service. A field has been added to the method settings at the module level to specify the address of the service where the method is to be executed.

Low-code CI / CD

  1. TEAM-37284 When configuring the Low-code CI/CD developer tool, you can now add a separate channel for sending messages to the #activity stream about successful data exchange between companies.
  2. TEAM-39162 In the Low-code CI/CD tool, the API token from an external company is no longer displayed when viewing a created link. This option has been implemented to improve security.

#BreakingChangeAlert

Document Management

  1. TEAM-38484 The file pages appearance now matches the Document type app forms display.

The following changes have been implemented:

  • The view form: the Edit button, which was previously located on the top panel, has been moved to the bottom. By default, the page opens in a reduced size as an app form, as users can expand it to full screen. The sidebar with document properties is displayed by default. It can also be collapsed.
  • The editing form: the avatar sizes for users working with the file has been refined. The user activity indicator has been changed: instead of the pencil and lock icons, the Editing: and Locked: tooltips have been added.
  • Approval and information forms: the Approve and Reject or Inform buttons, which were previously located on the top panel, have been moved to the bottom. The task name is displayed on the top panel. By default, the page opens as an app form, but users can expand it to full screen.
  1. TEAM-38756 Added the ability to select favorite options for working with a file, which will be displayed on the top panel of its view form for quick access.
  2. To do this, click the three dots icon on the file view form to open a list of all available actions. Then select Manage Buttons and move the actions to the Favorite Functions column in the window that opens. The maximum number of favorite functions is 3.

Table-based approval routes

  1. TEAM-39348 Starting with 2025.10 release, the table-based approval route functionality will be available to users without the need to enable the enableApprovalRoute feature flag.
  2. TEAM-37975 When configuring a table-based route, it is now possible to specify sequential approval. As with parallel approval, users, user groups, and organizational structure items can act as approvers.

The employees specified in the stage settings will perform their tasks in turn. If one of them does not approve the document, the stage will be assigned a general resolution of Rejected.

Projects

  1. TEAM-30296 A project creation from a ready-made template has been improved. Now, the folder structure specified in the template on the Files tab is copied to the new project.
  2. TEAM-30767 The View Project Plans widget now allows you to customize the task table, for example, to add a project status display. You can place the widget on a user app form and set the table parameters in the same way as on the project page itself.

Service

TEAM-36794 Improved Chat with live chat operators and Live Chat Messages widgets appearance. Improved performance in widgets, dialogue scrolling, and date display has been standardized.

Telephony

TEAM-34818 Automatic calls linking to companies via the contact specified in the call has been implemented. With the help of improvements in the Call Register widget, the connection between calls and companies is now displayed correctly. Now the widget can be placed on the Company app form and used to display all conversations with representatives of that organization.

TS SDK and API

  1. TEAM-8048 Updated the Web API page interface for app, processes, reports, and contracts. Now the main available methods are listed on the page in a single list. You can expand the section with the method, view the parameters and possible responses to the request, copy the method, and compose and test the request, receiving its full address and response from the server.
  2. TEAM-37940 To improve security in the system, the API tokens in the Administration > Tokens workspace display has been hidden. Now the value can only be copied when creating a token. It is not displayed on the page afterwards.
  3. TEAM-33516 When searching for data using TS SDK scripts, app item data partial selection has been implemented.

Selection modes:

  • Include: select only the specified fields:

const results = await Application.search()
 
.fields({ __name: true, __createdAt: true, total: true })
 
.all();
 
// Returns only the __id, __name, __createdAt, total fields

  • Exclude: excludes specified fields from the complete set. Excluded fields are marked with the false value in the query:

const results = await Application.search()
 
.fields({ total: false, history: false })
 
.all();

Operation notes:

  • The __id field is always returned, the rules do not apply to it.
  • If the .fields() method is not called, all fields are returned because the rules are not filled in.
  • When using contradictory operators, the rule is set in the Include mode:

// EXAMPLE 1
 
const results = await Application.search()
 
// Set the requirement to select only the total field and exclude the history field.
 
.fields({ total: true, history: false })
 
.all();
 
// Only the total field (and __id) is returned
 
// EXAMPLE 2
 
const results = await Application.search()
 
// Set the history field selection and simultaneously exclude the history field
 
.fields({ history: true, history: false })
 
.all();
 
// A typing error, because the field name value can only be used once, is returned.

For more information about partial sampling in the Web API, see BRIX public API.

  1. TEAM-39172 Added the ability to get a list of approval and information sheets via Web API: POST /pub/v1/docflow/{namespace}/{code}/{id}/lists.
  2. TEAM-39173 Added the ability to get information about document registration via Web API: POST /pub/v1/registration/{namespace}/{code}/{id}/lists.
  3. TEAM-39174 Added the ability to search the file storage via Web API: POST /pub/v1/disk/files/search.

Filtering is supported by the following properties:

  • File name (partial match search).
  • ID of the user who created or modified the file.
  • Range of creation or modification dates for filtering.
  • Maximum or minimum creation and modification dates (inclusive).
  • Directory ID.

You can apply the option to return results starting from a specific item, as well as specify the number of items to return (the maximum number is 10,000).

Bugs fixed

  1. TEAM-7649 The mechanism for granting access permissions to internal users has been adjusted. Now, in order for users to access the external portal, they need to be granted visibility permissions for the workspace within which this portal was created. This rule does not apply to employees added to the External Users group.
  2. TEAM-18701 When setting up two-factor authentication on the external portal, validation has been added for the field where the SMS provider is specified. The user will see a notification when saving the settings if the entered provider is not connected.
  3. TEAM-20864 When registering a user using OAuth2, re-authentication was required after editing the profile. The behavior has been fixed.
  4. TEAM-35429 Fixed the structure of the 400 error returned in the Web API for the following methods:
  • Creating an app.
  • Assigning an app item status.
  • Updating an app item.
  • Continuing a delegated action by ID.
  • Starting a process by workspace and code.
  • Saving data by key in the app storage.
  • Saving data by key in the workspace or module store.
  • Saving data by key in the System object storage.
  1. TEAM-37833 Fixed an issue where In the Account property settings, the Multiple option was not displayed in the list of possible types. Now you can specify the type for the field, and the selection is displayed in the app form settings.
  2. TEAM-38810 Fixed an issue where it was impossible to match the Number variable with the status ID before the change or the status ID after the update in the business process used in the Status Change event handler.
  3. TEAM-39483 Fixed an issue where a script using the create() method generated an object with binary data (Blob) instead of a file in a business process.
  4. TEAM-39561 Fixed an issue that prevented scripts from executing fetch() calls over HTTPS with invalid or self-signed certificates, even if certificate verification was disabled.
  5. TEAM-38301 When using the call() method with the FormData object passed to the body, the request body was passed as a string. As a result, methods that expected FormData values ended with a 400 error. Now the call() method works correctly.
  6. TEAM-38636 When opening tasks via the BRIX mobile application, the description and attached files were not displayed on the form. This issue has been fixed.
  7. TEAM-39324 Incorrect behavior was detected when applying a search to app fields. This issue has been fixed. Now the search is performed only on fields marked with the Quick Search option.
  8. TEAM-36444 The ability to select and copy text in the Live Chat Messages widget has been restored.
  9. TEAM-39727 Improved LiveChat display in the mobile version. After the fix, the main LiveChat button is located behind the message window, the authorization form, and the email sending form. The buttons for channels connected to LiveChat are collapsed.
  10. TEAM-30589 The logic for granting permissions in a process task has been fixed. Now, in a task with a transition to signing, rights to edit an app item are granted automatically. Previously, the system displayed a 403 error if the user signing the item did not have the permissions to edit it.
  11. TEAM-22520 The Signature Status widget displayed an incorrect value. This issue has been fixed. Now, the widget on the item sidebar displays information about the current signature, which is the user who signed the item last.
  12. TEAM-37656 Adjusted settings in the Register Account and Pending Account Registration business process activities. Now you cannot select an electronic signature provider in them, since the activities are only necessary for working with the MyDSS service.
  13. TEAM-38217 If, during a business process, an .xlsx file with multiple rows in a cell was converted to .pdf format, only the first row was displayed in the final document. This issue has been fixed.
  14. TEAM-39223 Automatic data update has been added when changing the sorting mode in the file addition window from the Files workspace. Now it is not necessary to reopen the window to apply the sorting.
  15. TEAM-39282 Added automatic data update in the Files workspace when renaming and deleting a file using the context menu, as well as when unlocking a file from its preview form.
  16. TEAM-39573 In the Approval business process activity, if the deadline set via a Date/Time variable had passed, the process instance would stop.

The issue has been fixed. Now, under such conditions, the approval task is assigned with an expired deadline, it can be completed, and the process can continue.

  1. TEAM-36284 If the Kanban board data display mode was enabled in the Deals and Leads apps and a search by parameters was specified, the filters were reset when the user opened a task from an item page and returned to the page. This issue has been fixed.
  2. TEAM-38801 Fixed an issue where changes made when editing the project type in the Administration workspace were not saved. At the same time, new app items were created in the Projects > Project Types workspace for each time the changes were saved.
  3. TEAM-39102 Fixed an issue where the linked tasks were not shifted in the Gantt chart if the user enabled auto-planning on the project page and edited the end date of one task in the table.
  4. TEAM-39202 Fixed an issue where the contents of the Project Settings page were not displayed in the Administration workspace.
  5. TEAM-39707 The following issue has been found: in the Tasks > Project Tasks workspace on the Control tab, the executor could perform actions with several tasks: Accept or Send Back.

The behavior has been fixed. Now, bulk actions on tasks under control are only available to the project supervisor.

  1. TEAM-38099 The notifications settings about project tasks has been improved. Now, enabling and disabling parameters on the project page works stably and correctly.
  2. TEAM-11115 If an asynchronous subprocess ends after the parent process has finished, the logs record the following errors: “instance is terminated and Task Id not recognized.” This issue has been fixed, as now the process ends correctly.
  3. TEAM-12284 Fixed an issue where the Move option for changing the process placement level did not work in the Administration > Business Processes workspace.
  4. TEAM-24541 If the notifier service was unavailable, execution errors occurred in business processes. This behavior has been fixed, as now processes will continue to run if the service is disabled at any step.
  5. TEAM-32373 When multiple process instances (more than 100) were launched simultaneously for a single app item and tasks were assigned, the value of each person responsible for the task was not recorded in the system and written to the Executor app system field in time. As a result, some data was lost. Changes locking to system properties in the item has been added. Now, values from tasks are written to app fields one at a time, rather than simultaneously.
  6. TEAM-36086 If a created App (one) type variable was deleted in a business process context, the Multiple subtype was incorrectly specified when it was restored. This issue has been fixed.
  7. TEAM-37218 In the Administration > Process Monitor workspace, the tree display settings were set incorrectly. If the user enabled the option, it was not applied, and vice versa. This issue has been fixed.
  8. TEAM-37318 On a business process page, automatic data updating on its map has been implemented when updating the version, skipping or restarting a process step.
  9. TEAM-38725 The mechanics of simultaneously launching multiple process instances have been refined. Previously, if the limits on the number of instances in a given time interval were exceeded in the system, a delayed launch was performed. This led to uncontrolled growth of timers in the scheduler service. Now, when the limit is reached, instances are not launched.
  10. TEAM-39009 Fixed an issue where the bulk action of interrupting process instances did not work in the Administration > Process Monitor workspace.
  11. TEAM-39115 Actions in business processes of the Script type with the Result Request execution model did not work correctly. The business process continued even if the check() function, specified in the action to check the result of the request to an external service, returned false.

This issue has been fixed, as now the action is repeated until the function returns true.

  1. TEAM-39284 The parent process continued to run immediately after the child process started if the Asynchronous start option was disabled in the subprocess launch activity settings.

This issue has been fixed. Now the parent process waits for the child process to complete, unless asynchronous launch is used.

  1. TEAM-39487 Fixed an issue in the business process action with the Script type and the Result Request execution model. Now, the transfer of a dynamic output variable to the process context using binding is performed correctly.
  2. TEAM-37750 Fixed EQL search issues that occurred:
  • When using the IN operation.
  • When searching for users by org chart item using an EQL query.
  1. TEAM-38680 Improved the mechanism for granting access permissions to calendar events. Now:
  • All events in which the user is specified as a participant appear in the personal calendar.
  • The user can grant permissions to edit and delete only those events where they are the author. For other events, they are only granted viewing permissions.
  • A line manager, according to the org chart, has default access to view employees’ personal calendars and the events in them.
  • The system administrator does not have full access to calendars. All rules for granting permissions to events apply to them.
360010947000.html 2025_9.html