search string side menu

2025.11

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

After December 17, 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.

New table version

TEAM-1978 The new version of table display, which is enabled using the front_enable_vtable feature flag, allows you to configure how large volumes of data are displayed:

In the table settings, you can enable pagination and choose how rows are displayed:

  • Paginated — data is split across multiple pages;
  • Load on scroll — available when row grouping is disabled. Records are loaded as you scroll down the table.

The number of records per page is specified by the user in a separate field.

In addition, you can enable a counter that shows the total number of rows. This option is also configured in the table settings.

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

Widgets

  1. TEAM-22558 A new Checkbox widget has been implemented. It allows you to display a Yes/No Switch property as a checkbox, with the description placed to the right of the checkbox.This is convenient when using long descriptions, for example: I agree to the processing of personal data. On forms, the checkbox is aligned to the left together with other fields, and its position does not depend on the length of the description text..
  2. TEAM-40605  To improve user experience, the String widget has been renamed to Container.
    The following features have been added:
  • configuration of element orientation (horizontal or vertical) and spacing between elements;
  • enabling automatic wrapping of elements to a new line if they do not fit.

#BreakingChangeAlert

Interface designer

TEAM-40488To improve usability, the toolbar in the interface designer has been visually updated. The toolbar allows you to:

  • save, publish, and debug the configured interface;
  • validate added widgets;
  • undo and redo actions.

Business processes

TEAM-37571 In the process instance page with an error, the Restart steps and Skip steps buttons have been added. They allow these actions to be applied to multiple blocks on the process diagram at once.

Email settings

TEAM-36982 In Administration > Email Settings, an additional connection security method has been added for custom SMTP servers.

Previously, only TLS was supported. StartTLS is now also available.

Low-code CI / CD

TEAM-31340 The elma365pm  utility has been improved to support CI/CD-based solution development.

A new flag has been added to the import command: exclude-upgrade-permissions, which allows you to preserve access rights settings in configurations, solutions, and workspaces. 

Command example:

elma365pm import --token='your token' --host='host company'  --exclude-upgrade-permissions

Available starting from version elma365pm 1.18.0.

Document Management

  1. TEAM-37773  An error notification is now displayed if a document generation template with incorrect syntax is added to an app. The message shows the specific line where the error occurred..
  2. TEAM-38882  In the Send Document / App Item business process activity settings, you can now define whether filling in a comment is required when a user signs a document as part of the review. On the Signature tab, the Comment field can be set to one of the following options:
  • Do not use
  • Optional
  • Preferred
  • Required.
  1. TEAM-40001 A new Notifications tab has been added to the Send Document / App Item and Approval business process activities. During process modeling, you can enable the following options:
  • notify the assignee when an information or approval task is created;
  • display a notification about the start of information or approval in the item’s activity stream.
    An administrator can configure notifications in a company-specific format using template syntax.
    For example, you can add a Comment variable to the process start form for sending a document and display the initiator’s message in the app item activity stream.
  1. TEAM-39335 The mechanism for starting business processes when approval or review sheets are sent to the archive has been optimized. Due to this optimization, invalid sheets are no longer automatically returned from the archive. Previously, if a sheet was archived due to changes in archiving settings, it became valid again when the original settings were restored.
  2. TEAM-38599 The standard Approval document route has been improved. Key changes:
  • when a user sends a file or app item for approval from its view form, they can leave a comment for approvers. The comment is displayed in the associated feed;
  • approval start notifications are improved — they now include the comment and the user who initiated approval;
  • approval completion notifications are improved — they now include the resolution, a link to the approval object, the executor, and their comment.
    If there were multiple approvers, they are not listed in the notification. Their resolutions can be viewed in the approval sheet.
  1. TEAM-40177 A new copy and save to computer action has been added to the context menu (right-click) for image files.
  2. TEAM-39084 The modules for viewing and editing documents online using OnlyOffice and R7-Office have been updated.

Key changes:

  • the ability to choose a light or dark theme for the file view form;
  • optimized document display on mobile devices in both browsers and the BRIX mobile app;
  • a Number of licenses parameter has been added to the R7-Office module settings.

This parameter allows you to limit the number of concurrent file editing licenses.

When all licenses are in use, users will see a warning and the file will open in PDF view mode.

If the parameter is not configured, users will see an error message and will not be able to view the file.

Projects

TEAM-39232  If the BRIX Projects solution is not activated, users can access the Projects workspace and its apps, but cannot work with the project schedule.

Service

  1. TEAM-26537 In custom modules, it is now possible to create an event handler to track changes in the status of an operator handling requests in the Live Chats workspace. During configuration, select the domain Users > Change operator's status. An event is generated in the following cases:
  • manual status change;
  • automatic switch to offline when the operator logs out, is inactive for a certain time, or when the BRIX Service license expires.
     
    The event records the following information:
  • user ID;
  • new operator status;
  • event date
  1. TEAM-37979 For live chats connected to email, the SMTP connection closing process has been optimized under high load. Previously, when the connection limit was reached, connections were not closed properly, which caused messages in the Live Chats workspace not to be sent. Now, limits are released correctly and emails are delivered successfully.

 

Email workspace

TEAM-37861 A search field has been added to the Linked Emails widget. On the app item form linked to an email, users can now quickly find messages by keywords from the email content, as well as use advanced search by parameters such as:

  • type (incoming or outgoing);
  • sender and recipient;
  • subject;
  • sent and received dates, and more.

 

Marketing

TEAM-39473 The logic for determining preference categories for subscribers created from multiple contacts with the same email address has been improved:

  • the subscriber now retains preference categories from all contacts with the same email;
  • deleted contacts or contacts marked as duplicates are no longer considered.

Example: Two contacts are created with the same name and email address, but with different newsletter preference categories. The subscriber is determined based on the rule configured in Administration > Marketing, for example, the most recently created contact. For this subscriber, preference categories from both Contacts app items are applied.

 

CRM

TEAM-36891 A Messenger block has been added to customer journey maps for creating trigger campaigns. It allows you to configure message delivery to a Telegram chatbot.

 

TS SDK and API

  1. TEAM-31501 Working with variables from custom module settings in scripts has been optimized.

Due to possible errors, the following variable access methods are now considered deprecated:

  • Application.params
  • Namespace.params
  • Global.params

Starting from version 2025.11, use the following asynchronous methods instead:

  • Application.getParams()
  • Namespace.getParams()
  • Global.getParams()

Existing published scripts may continue using deprecated methods.

When publishing a new script, such properties will be highlighted in the editor, but publication will still be allowed.

To quickly replace methods in scripts, press Ctrl+H in the editor and enable regular expression search:

//This example uses a simple regular expression. We recommend validating each replacement
 
Search pattern: ([\s\(])([a-zA-Z][\w]+)(\.params)
 
Replace: $1(await ($2.getParams())

#BreakingChangeAlert

  1. TEAM-40421 Web API methods have been added for reading metadata of pages, workspaces, and apps in the corresponding System.scheme branches. These methods are available only in server-side scripts.
  2. TEAM-38326 Retrieval of a user’s priority signature selected in their profile settings has been implemented via the TS SDK.

The DigitalSignItemData model now includes the isDefault attribute (boolean, readonly).

  1. Web API methods for working with process instances have been implemented. The following actions are now available:
  • modifying context and interrupting a process instance — subject to the user’s access rights;
  • updating the version of one or multiple process instances, and bulk interruption of process instances — available to users in the Administrators group.

 

Bugs fixed

  1. TEAM-16324 When creating a calendar event, the Participants field is now required. Previously, an event could be created without filling in this field, and such events were not displayed in the author’s personal calendar.
  2. TEAM-29706 When creating a calendar event, validation of the Start date and End date fields worked incorrectly. Users could set dates in the past. The issue has been fixed.
  3. TEAM-25487 In the Interface Designer, debugging of a created form did not start in the custom module settings. The issue has been fixed.
  4. TEAM-38158 When authorizing on an external portal, two-factor authentication did not work if phone number authentication was enabled and email authentication was configured as the second factor. The issue has been fixed.
  5. TEAM-39050 In the settings of predefined system modules (for example, Alytics, Gravitel, etc.), no warning was displayed when required fields were not filled in. The page could be saved without specifying mandatory parameters. The issue has been fixed.
  6. TEAM-39403 In case of failures in the scheduler service, the current date was not set in Date/Time fields if this option was enabled in the property settings. Now, in such cases, the user sees a warning that calendar data could not be retrieved.
  7. TEAM-39505 If an OTP provider is used to log in to an external portal, users could receive a one-time code even when the module used for provider integration was disabled. The issue has been fixed.
  8. TEAM-39858 When a process was configured to start on a schedule with repetition every N minutes, the option to skip execution on non-working days did not work. The issue has been fixed.
  9. TEAM-40125 For recurring events, the option to repeat on working days (based on the working calendar) was not applied. Events were added on calendar weekends. The issue has been fixed.
  10. TEAM-40298 In the BRIX mobile app, a user without the required access could open the schedule compliance page of other employees. The issue has been fixed. User permissions are now checked when opening the page.
  11. TEAM-8356 Errors occurred when executing the setTimeout, clearTimeout, setInterval, and clearInterval methods. These methods now work correctly in client-side scripts. In server-side scripts, only setTimeout is supported for backward compatibility.
  12. TEAM-11600 Server-side script execution has been optimized. Scripts now run faster.
  13. TEAM-24552 In String (markdown) fields, long horizontal lines defined using ***, ---, or ___ were not displayed. The issue has been fixed.
  14. TEAM-38532 A script for searching items by app did not work if the app identifier contained the - character. The script used the Namespace value to access the app. The issue has been fixed.
  15. TEAM-39658 In the Tracing developer tool, it was not possible to change the retention time for all traces and error traces. The configured values were not saved. The issue has been fixed.
  16. TEAM-39659 In the Tracing tool settings, it was not possible to set a trace retention time greater than 23 hours. The issue has been fixed.
  17. TEAM-35094 In the Workspaces and Solutions Settings window (opened from the main menu and containing a list of all solutions installed in the company), the Live Chats workspace was displayed incorrectly: its name was duplicated in the list. The issue has been fixed. The entry now appears only after at least one live chat is created in the system. The buttons for hiding and showing the workspace in the left menu now work correctly.
  18. TEAM-39918 An issue has been fixed where, when activating the BRIX CX system solution, licenses of the included BRIX Service system solution were incorrectly marked as occupied.
  19. TEAM-40016 An issue has been fixed where a message from an operator to a client in LiveChat was not sent when the WebSocket connection was closed.
  20. TEAM-36982 In Administration > Email Settings, an additional connection security method has been added for custom SMTP servers. Previously, only TLS was supported. StartTLS is now also available.
  21. TEAM-25814 When accessing Files properties in scripts, the file identifier was treated as an object. The issue has been fixed. The __id attribute is now correctly defined as a String.
  22. TEAM-31063 When a system administrator edited access rights to a file or a folder in the Files workspace, that user was displayed as the author of the latest document version. The issue has been fixed. The Created by and Created on fields in the version list are no longer changed.
  23. TEAM-31194 The notification mechanism for adding empty files and images to Files (single or multiple) and Image (single or multiple) fields has been corrected. Notifications now appear on the first upload and on repeated attempts.
  24. TEAM-36175 In the Registration widget, the Register Document button was not displayed for users with registration permissions. The issue has been fixed. The button is now displayed correctly based on the current user’s permissions.
  25. TEAM-36331 An issue has been fixed where it was not possible to sign a resolution within an approval business process task. Now, if mandatory signing of the decision is enabled in the Approval activity settings, the user can complete the task. The signature archive onn the app item page now correctly displays the signing fact and the signed resolution file.
  26. TEAM-39622 An issue has been fixed where, if the File protection option was enabled in Administration > Security Settings, the printable file text was generated incorrectly.
  27. TEAM-39648 An issue has been fixed where disabling local editing in Administration did not actually prevent users from editing files locally. The Disable local file editing option now works correctly.
  28. TEAM-39653 The contract versioning process enabled via the allowVersionsSnapshots feature flag has been corrected. It is now implemented similarly to app versioning.
  29. TEAM-39741 In the File List widget, an issue has been fixed where filtering parameters configured in the widget settings were not applied.
  30. TEAM-39922 An issue has been fixed where scanned documents in .pdf format were displayed incorrectly.
  31. TEAM-40035 The display of created web documents in the Files workspace has been improved:
  • unnecessary scrolling has been removed from the form;
  • the width of HTML-based web documents has been adjusted;
  • the Save and Cancel buttons are now displayed at the bottom of the modal window.
  1. TEAM-40084 Files that do not support preview in BRIX were downloaded to the user’s computer twice. The issue has been fixed.
  2. TEAM-40100 Users who are not members of the Administrators group could not configure the list of available file actions on the app item view form. Settings configured in the Button Control window were not saved. The issue has been fixed.
  3. TEAM-40133 If a user added a file action to Favorites on the document view form, it was not displayed in the context menu. The issue has been fixed.
  4. TEAM-40214 If a filter was pinned on an app page, it was not possible to open a file in a new browser tab from the item page. Instead of the file view form, the app page was opened. The issue has been fixed. Files now open correctly in a new tab.
  5. TEAM-38168 In the Leads and Deals apps, pinned filters for quick search were not preserved after page refresh. The issue has been fixed. If a filter is pinned, only matching items are now displayed when opening the page.
  6. TEAM-39484 In the CRM workspace, deleted records were displayed in duplicate search results. The issue has been fixed.
  7. TEAM-39655 Publishing of a created email template did not work in the Marketing workspace. The issue has been fixed.
  8. TEAM-39667 An error that occurred when creating a subscriber segment using an EQL365 query has been fixed. The segment is now generated correctly.
  9. TEAM-40294 When using the Asterisk telephony module, extra app items with empty fields were created when registering incoming calls. This happened when calls were made to an internal provider number that was not mapped to a BRIX user in the telephony module settings. The issue has been fixed.
  10. TEAM-39966 In the Project Milestones and Project Tasks widgets, filtering parameters for task start and end date fields were not applied. The issue has been fixed.
  11. TEAM-40269 A project plan could not be published by the project manager if it had previously been modified by a system supervisor. The issue has been fixed.
  12. TEAM-39849 An error occurred when configuring dynamic binding in a custom action in a business process created within a module. Properties of type Phone number and Email were not passed to the JSON field. The issue has been fixed.
  13. TEAM-40020 An issue was identified where, if a custom form was configured in a business process and then deleted, the process could not be published. Nothing happened during publication, and no warning was shown. Now:
  • If a deleted custom form is specified in the Task activity settings, a warning is displayed during process publication.
  • If the process contains a deleted form that is not used anywhere, the process is published successfully.
  1. TEAM-36498 The Associated Items widget failed to load when a user without access to the related app opened an item containing this widget via a direct link. The issue has been fixed.
  2. TEAM-38184 The display of the star icon indicating a favorite message in the global #Activity stream has been fixed.
  3. TEAM-39727 In the mobile version of the site, the LiveChat from the Live Chats workspace was displayed incorrectly. When opening the chat, the window was partially overlapped by the LiveChat button and the list of available channels. The issue has been fixed.
  4. TEAM-39652 When importing contacts into Unisender via a file, not all subscribers were transferred. The issue has been fixed. For correct subscriber import, the imported data must contain up-to-date preference category values. Otherwise, the Preference category field remains empty, and contacts are not identified as subscribers.
360010947000.html 2025_10.html