search string side menu

New releases > BRIX SaaS / 2025.7

2025.7

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

After August 13, 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.

Apps

TEAM-28666 A mechanism for controlling saves when collaborating on app items has been implemented. The Prevent save conflicts option is activated in the app settings, which includes:

  • Atomic attribute changes: only changed fields are saved, not the entire item.
  • Conflict control and change blocking:
    • When a conflict is detected, the user receives a notification.
    • Saving is blocked until the user refreshes the page to avoid losing changes.
  • Item versioning mechanism:
    • Contains a unique version identifier (__version).
    • Is updated each time the item is saved.

This mechanism solves the problem of simultaneous item editing by different users and possible inconsistencies or data loss.

The option applies to: manual item editing, business process tasks with app subfields on the form, process activities with automatic or manual item changes, and editing items using scripts.

#BreakingChangeAlert

Data types

  1. TEAM-2023 A new data type, App type, has been added. This property allows you to store a reference to any type of app in the system (namespace + code). The main use case is the development of modules and flexible links between apps in the configuration.

For example, when creating a module for integration with an external system, you can add the App type (multiple) property to the settings and then specify which types of apps need to be integrated.

  1. TEAM-29153 A new subtype has been added for the String (hidden) data type. This option visually hides data entry and display on the form. The data is still accessible to the user as a regular string and is loaded in an open form. This type can be used, for example, when filling in confidential data on a form.

Tables

TEAM-34476 Optimized work with tables in the system. Now you can add rows to the desired location in the table or delete them using the context menu:

  • To add a row in the editing mode, click on the desired row and select the appropriate action.
  • To delete a row in the editing mode, open the row’s context menu and select the action.

To start using the new tables, you need to:

  • Enable the front_enable_vtable feature flag.
  • Go to the table settings.
  • Enable the Show new table version option.

Chats

TEAM-37131 Improved the chat sidebar display. Now, when returning to the chat page, the sidebar remains expanded or collapsed depending on the state previously set by the user.

Access permissions

TEAM-36504 Access permissions to workspaces and tasks have been optimized. Now, if a user does not have access to the Company workspace, they will not have access to any pages there. Previously, users without access permissions to a workspace could view another employee’s performance discipline and task list.

Import and export

TEAM-8456 Now, in the window for exporting app items to an .xlsx or .csv file, you can select the fields from the context that you want to export. After adding the fields, you can configure the order in which they will be arranged in the table in the file.

Modules

  1. TEAM-31258 When using business process activities from modules in a process, you can now delete a value associated with a property and select a new one.
  2. TEAM-32537 When configuring business process activities from modules, the ability to specify a specific value for input or output variables has been added. Previously, a variable could only be linked to another property from the process context.
  3. TEAM-31297 For business process activities in modules, working with a configured dynamic binding form has been improved. Now, when creating new fields in the business process activity context, the activity settings in the process are updated, as existing variable links are preserved, and new fields are added to the settings.
  4. TEAM-37358 If one user is editing the module settings, and a second employee attempts to access the settings, a warning is added stating that the module is already in use.

It is implemented when simultaneously editing or opening the following settings in two tabs:

  • API methods in the module.
  • Business process activities in the module.
  • Event handlers in the module.
  1. TEAM-37233 The Send messages to HTTP service event handler type performance has been improved. Now, when delegating event handlers to an external service, the system does not wait for a response from the service. This significantly speeds up the event queue processing.

SAML integration

TEAM-36939 SSO is now disabled in the following cases:

  • Logging out of a user account due to exceeding the number of concurrent licenses.
  • Logging out of a user account due to exceeding the idle time.
  • Logging out of a user account due to exceeding the number of concurrent sessions.
  • Session termination by the administrator.
  • Voluntary logout from the system.

Business processes

  1. TEAM-12865 The process instance map now explicitly displays the activity where the error occurred, as it is highlighted in red. The History tab also shows the name of the activity with the error instead of the Error label.

The following improvements have been made:

  • Skipping a step is now triggered for a specific step.
  • Restart is called from a specific step, but the entire process instance is restarted.
  1. TEAM-36826 Synchronization of the Process Monitor and Business Processes pages has been implemented in terms of filtering, displaying the hierarchical directory, and settings for the appearance of the process table on the page.

Document management

  1. TEAM-35045 The ability to print with a watermark for all versions of documents has been implemented. In previous versions, only the current version of the document was printed with a watermark.
  2. TEAM-37125 For visual optimization of the interface, the icon for the Pending approval status has been changed in the approval sheets on the Document app forms.

Projects

  1. TEAM-25960 In Gantt chart editing mode, instead of the Approve button, which launched the process of approving the finished plan and its subsequent publication, you can add a button to launch any business process. To do this, go to Administration > Project types, configure the button, and link the process.

Please note that it is recommended to add the Project plan publication activity to the custom business process that you plan to link to the button, otherwise the project plan will not be published after the process is completed.

  1. TEAM-36837 For tasks on the Gantt chart, the free time amount has been added: these are days to which a task can be moved without moving the following related tasks or the project boundary. It is indicated by a shaded gray area.
  2. TEAM-36754 In auto-planning mode, when editing a project plan, an option has been added that allows you to set a delay period for related tasks. For example, task 2 starts after task 1. If you do not use the delay option, when you move tasks, the start date of task 2 will be set immediately after the end date of task 1. To set a later start date for task 2, double-click on the connection line and specify the number of days of delay in the window that opens. Now, when you move tasks, the specified delay period will be observed.

Service

  1. TEAM-29821 In the Administration > Live chats workspace, the display of available settings on the LiveChat tab has been improved:
  • Parameters have been regrouped into horizontal tabs.
  • Notifications have been added depending on the result of the settings validation.
  • The interface and dynamics of the LiveChat form preview display have been optimized.
  1. TEAM-33033 The functionality for connecting LiveChat to a live chat has been expanded.

List of improvements:

  • A new account type has been added: LiveChat. When adding a customer who has written to LiveChat and linking them to an app item for communication, the customer’s internal ID is recorded in the account field.
  • The operator can now initiate a conversation with a client who previously contacted via LiveChat.
  • The operator can now create a new session by selecting a contact with a LiveChat account type.
  • The Send Live Chat Message activity has been improved, as now accounts with the LiveChat type can be specified in the Recipients field.
  • The Send Live Chat Response activity has been improved, as messages are now sent correctly to sessions with customers with LiveChat accounts.
  • The Send Reply Message option has been improved when configuring routing rules: the messages are now sent correctly to sessions with customers with LiveChat accounts.
  • Improved filtering of sessions in the Live Chats widget: when selecting the By account setting, sessions with LiveChat customers are correctly displayed in the widget.

Telephony

TEAM-27576 The Hide the messages of linked contacts option has been added to the settings of the Linked Emails widget. When this option is enabled, only those emails that are linked to the current item are displayed on the app form, for example, in a deal. Without activating this option, the widget displays emails that the user has linked to the app item, and other emails from the contact specified in them are automatically added.

TS SDK and API

  1. TEAM-30104 Improved script hints when hovering over variables. Now, not only the variable type is displayed, but also its name, which is specified in the context section. This greatly simplifies working with scripts and speeds up the debugging process.
  2. TEAM-36651 Added the ability to set filtering for the Arbitrary app field by its namespace and code in the script. If only one system app is identified as a result of filtering, the selection of items of this app is performed.

mso-border-alt:none windowtext 0cm;padding:0cm;mso-ansi-language:EN-US">Context.fields.ref_item_app.data.setFilter((f, ctx, g) => g.and(f.namespace.eq("_clients"), f.code.eq("_opportunities")));

  1. TEAM-35775 The scripts now support the use of conditions for bulk actions with app items. An additional method, where(eql, params), has been added for update and delete operations. You can specify multiple search conditions and combine them using and.
  2. TEAM-29169 Previously, scripts in the module could access the same module through the Global.ns.ext_moduleuid variable. This object was always equal to the Namespace of the current module. In the new version, the property from Glonal.ns has been removed, and you must always use Namespace to work with objects of the current module.

#BreakingChangeAlert

Bugs fixed

  1. TEAM-21170 Added a clear error message when scripts refer to an unavailable or disabled external portal via the Namespace.portal property.
  2. TEAM-36318 Fixed an issue in the opened window display when you click the My Portals button on the external portal page. Previously, the window opened with a transparent background and did not cover the main page.
  3. TEAM-37405 Fixed an invalid example of time specification in the BRIX Web API. More correct requirements have been formulated.
  4. TEAM-36206 Fixed an issue with incorrect color display of holidays or weekends in the Date/Time field. Previously, when creating exceptional holidays or weekends in the calendar, they could be incorrectly highlighted in green.
  5. TEAM-36328 In the API method settings in the module, it was not possible to scroll through the list of added files in edit mode on the Files tab. The issue has been fixed, and scrolling through the list has been added.
  6. TEAM-36616 When calling the action of one module using actions through the imports variable in the scripts of another module, a compilation error occurred. Because of this, the component where the script is located, for example, a widget, might not be published. The issue has been fixed.
  7. TEAM-36995 If you do not fill in the field of type Arbitrary app (multiple) when creating an app item, the view form will display an incorrect hint “Item is loading” in this field.

The issue has been fixed. Now the field of the type Arbitrary app (multiple) remains empty if it is not filled in.

  1. TEAM-37094 Fixed an issue where the phone number with an extension was displayed incorrectly on the form. Now the extension is written after a comma from the main number.
  2. TEAM-37283 During long-term import or export profile execution in the CI/CD tool, a timeout occurred, which blocked work with the profile. Now, when a timeout occurs, it is possible to cancel the action, restart the check, or transfer the profile.
  3. TEAM-37203 In the interface designer, on the Settings > System functions tab, when selecting from the list of methods for functions, the page layout was displayed incorrectly and the field to be filled in was hidden. The layout has been corrected.
  4. TEAM-18000 Added conflict handling when field codes match in the source and contract. The user is shown an information message with details of the match. The field cannot be added to a contract with matching field codes.
  5. TEAM-26874 In the BRIX mobile application, the page layout was displayed incorrectly when creating or editing a web document in the Files workspace. The issue has been fixed, and the bottom panel with the Save and Cancel buttons has been adjusted.
  6. TEAM-28648 When you clicked on a file name in the Files field, the file editing form opened. The user could replace the page URL and gain access to editing. Issues in editing the address bar when viewing nested Files fields have been fixed.

When attempting to enter edit mode by changing the page URL, the user is redirected to the app’s main page. Fields can only be changed in the app item form edit mode.

  1. TEAM-34736 When performing bulk actions to move to the recycle bin or restore a large number of files in the Files workspace, an error occurred and the request timed out. Now the actions are performed correctly.
  2. TEAM-34816 When reassigning information or approval tasks, new executors were not recorded in the resolution sheets. When attempting to close the task, the “resolve inform list: unknown user respondent” error occurred. The behavior has been fixed. Now, reassignment in parallel mode works correctly.
  3. TEAM-35669 Fixed an issue where each time you went to the Create Package activity settings in the business process diagram, the field for selecting documents to be combined was duplicated.
  4. TEAM-36073 In the Approval activity form settings, there was no way to activate the Hide if the field is empty option. The issue has been fixed. The ability to edit field parameters on the standard activity form has been added.
  5. TEAM-36973 Fixed an issue where at the bottom of the chat page, the number of uploaded files was not reset if you first added files in the upload window and then canceled their attachment.
  6. TEAM-37020 Fixed an issue where in the BRIX mobile application, it was not possible to download a file from a Document type app item form.
  7. TEAM-37026 In the BRIX mobile application, the Upload and Preview File widget layout has been fixed.
  8. TEAM-37210 Fixed an issue when downloading a file via server scripts with file protection enabled.
  9. TEAM-31923 When creating a recurring event in the calendar and enabling the option to send a notification about it to the user’s email, the user received several notification emails instead of one. The issue has been fixed.
  10. TEAM-35859 When attempting to add a mailbox via OAuth2 in the user settings, an endless loading process occurred, blocking further actions. The issue has been fixed.
  11. TEAM-36247 Fixed an issue If the VoipParseWebhookRequest method was used in the user module for integration with IP telephony, a data type mismatch error occurred on the server when saving call data. Call information is now recorded correctly.
  12. TEAM-36708 Fixed an issue that prevented leads or deals from being moved to another status on the Kanban board if the Responsible field was removed from the board settings.
  13. TEAM-36881 Fixed an issue where while importing into another company, the Projects solution did not generate a project based on one of the created and imported user plan types. Obtaining a template project has now become dynamic.
  14. TEAM-36997 Fixed an issue where in the project plan, the end date of the milestone was set one day earlier than its start date. The end and start dates of milestones now match.
  15. TEAM-37023 Fixed an issue where while performing a project task, the Done button on the page did not change to the Reopen button.
  16. TEAM-37083 Fixed an issue where the Process type task did not start if a business process created within another project type was used. Now, the process launch does not depend on the input parameters of its context.
  17. TEAM-37320 The search bar display in the Projects workspace has been corrected. Previously, the search bar disappeared when the Project Milestones widget was located on the project form.
  18. TEAM-1443 Fixed moving a process to another folder on the Business Processes page. Previously, you had to refresh the page to see the changes in the process location.
  19. TEAM-29461 Fixed an issue where the Expand All button on the Business Processes page did not work, as folders with processes remained collapsed.
  20. TEAM-32336 Optimized the business process import process. Removed unnecessary changes to the process context metadata when transferring the configuration.
  21. TEAM-32491 Corrected the folders order on the Administration > Business Processes page. Now, the search, display, filtering, and settings on the process monitor and business process pages are synchronized.
  22. TEAM-36571 Fixed an issue where it was possible to switch to editing the process diagram when opening the page of a process instance created in a locked solution from the Business Processes page.
  23. TEAM-36766 Fixed an issue where if the task name from a business process was set using a variable and quotation marks, the task could not be reassigned to another user.
  24. TEAM-33370 The system performance has been optimized when there are a large number of user groups.
  25. TEAM-37351 Fixed an issue where the organizational chart tree is not fully formed if it contains more than 10,000 items when using the System.organisationStructure.search().all() method.

Important: the organizational chart items returned by such a query may contain deleted elements. If you further apply methods available for the object to the result, the processing will result in errors.

It is recommended to use the System.organisationStructure.search().all() method with a filter for active items (i.e., __deletedAt.neq(null)) if you plan to build a tree and process the items obtained.

  1. TEAM-36145 Fixed an issue where after activating the Sales Management solution in the system, access to creating a schedule with the Item Conversion (Sales) calculation type did not appear.
  2. TEAM-37280 When the mail client was connected, errors occurred when trying to open attachments from emails linked to app items. The behavior has been fixed.
2025_8.html 2025_6.html