search string side menu

New releases > BRIX SaaS / 2025.3

2025.3

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

After April 15, 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.

Server scripts tracing

  1. TEAM-33039 Improved the search in the recorded trace page. You can now search:
  • By name of the spans that make up the trace.
  • By names of attributes and events.

Matches are highlighted in yellow on the page. Also added navigation — you can quickly switch from one found record to another.

  1. TEAM-34471 In the module settings on the Event Handling tab, you can now view the total list of traces recorded by all enabled event handlers in the module. Previously, you could access the traces of a certain handler only on its page.
  2. TEAM-33328 In the module settings on the API Methods tab, you can now view the total list of traces recorded by all API methods created in the module. Previously, you could access traces of a certain method only on its page.

Business and work calendar

TEAM-33499 In Administration > Business Calendar, you can now export a customized calendar, as well as download a calendar from another system in .zip or .csv format.

Business processes

  1. TEAM-3206 In Administration > Process Monitor on the process page, you can now select several running instances and interrupt them.
  2. TEAM-8091 In the process instance page, the History tab now displays information about the execution of each activity on the process flow chart. You can see the executor, the date and time the activity was started, and its duration.
  3. TEAM-33962 When publishing a process, the performance indicators used in the process flow chart are checked. If an indicator is not published or created in a disabled module, users will see an error.

Modules

TEAM-30821 In the module settings on the Business Process Activities tab, the list of records now displays the unique code of the activity specified when it was created.

Widgets

TEAM-18509 In the Code widget, you can open the settings window in full-screen mode for easy scripting.

Apps

  1. TEAM-24002 Improved editing of app items. Now when saving a form, only the changed fields are updated, not the entire item. This improvement prevents situations where field values could be swapped and not saved during concurrent editing of an item.
     
    In addition, a bulk editing form for app items now includes options for each field:
  • Leave unchanged. Select to skip editing the current value in the field on item forms.
  • Clear. Select to remove the value from the field and leave it blank on the form.
  1. TEAM-10181 To display items in the form of tiles and Kanban board on the app page, the following components support line breaks: item names and fields of the Status, Category, Email, Account, and Full name types. Now in these modes, users will immediately see item names and field values.

Item search

  1. TEAM-33768 In the search-by-parameter window on the app page, you can now specify several items in the field of the Users (one, many) type.
  2. TEAM-34535 In the BRIX mobile application, added a button for canceling a request and exiting the search mode. It is available in the window for searching app items by parameters.

Substituting users

  1. TEAM-20200 Added a feature to create substitution rules for users. Now you can specify multiple substitutes and customize the conditions under which tasks will be distributed among them. This provides flexibility in managing tasks during the absence of employees. To make the feature available, enable the front_enable_substitution_rules feature flag.

Main operating principles:

  • An unlimited number of task allocation rules can be created for a single substitution.
  • A rule is assigned to a certain absent employee.
  • If a task does not match any of the rules, it is assigned to the specified substitute.
  • Rules can be edited or deleted if they are not used in active substitution.
  • If the conditions of several rules overlap, you can set the priority of selection.
  • When reassigning a task manually, the substitution rules are not taken into account.
  • In cyclic substitution setup, current tasks remain with the original executor and new tasks are reassigned through the chain of substitutions.
     
    To create a rule:
  1. Create a substitution and fill in the required fields.
  2. In the Rules field, click Create.
  3. In the window that opens, specify:
  • Rule name.
  • Conditions to filter the tasks.
  • User to whom the tasks will be reassigned.
  1. Save the rule.
  1. TEAM-31168 Improved the assignment of tasks to an employee for whom a substitute has been created. Now, if a substitute employee creates a task and specifies an absent user as the executor, the task is not reassigned, but remains assigned to the absent user.

Document management

TEAM-31041 You can now upload an .rtf file as a document template and use it in a business process in the Generate from Template activity.

Projects

TEAM-34190 Accelerated the loading of the project task view form. Optimized loading window display.

Service

  1. TEAM-28887 Added a feature on the session page to attach to the message files that are uploaded to session-related app items in fields of the Files type. For example, you can forward a file from a call to a client, and you do not need to download it to a computer beforehand. The operator can now select files:
  • From a local computer or smart phone.
  • From the Files workspace.
  • From linked items of the app.
  1. TEAM-34242 On the session page with an external user who contacted via email, the client data is now displayed better. If there are multiple recipients, one of them is marked as the primary client. This is either the first user who contacted a live chat or the user the operator started the session with.

Telephony

TEAM-31626 Added the Telephony workspace to accumulate and store data on incoming and outgoing calls. For each recorded call, an item of the Calls app is created, where the data is stored.

A Call Log widget is added. It allows you to display calls on a separate page and on viewing forms of other apps of the system. In the widget, you can customize the columns of the table with records, filters for searching, as well as the criteria for selecting items for displaying. For example, you can show only calls of the current user, incoming or outgoing, etc. When you open a call page, you can view the call data and see the contact of the call, the user who received or made the call, the start and end date of the call, its duration, listen to the call recording, etc.

In the Administration workspace, you can customize the appearance of incoming, outgoing, and missed call pages separately. You can also choose which user action buttons to display: hang up, reassign call, put on hold, create CRM task, event, or note, etc.

In addition, you can create a custom call summary page. It can be filled with widgets and opened automatically, for example, when a call comes in, or by a button in the call page.

Telephony workspace, Call Log widget, and call settings in Administration > Telephony are available if BRIX Communication Management license is enabled, as well as those licenses where communication management functionality is enabled (BRIX Sales Management, BRIX CX, and outdated BRIX CRM).

TS SDK and API

  1. TEAM-33701 When using the Web API method to create a folder in a document categorization (POST /pub/v1/nomenclature), added a check for the existence of the document registry to which the folder is created. #BreakingChangeAlert
  1. TEAM-34088 Improved the manualRegister method. Now manual registration of documents using this method is prohibited if automatic registration is set up in the folder. In scripts where the method is used, an error will be displayed under such conditions. #BreakingChangeAlert
  2. Added a feature to create instances of objects of the Role type using methods:
  • create(type: RoleType, code: string). Initializes a role by type and code.
  • createByItemRef (item: UserGroupItemRef | UserItemRef | OrganisationStructureItemRef). Initializes a role by reference object.
  1. The Node.js version for server scripts execution has been updated to v.20.

Bugs fixed

  1. TEAM-32713 If a non-existent method in Server.rpc was used in the widget script, the widget was published and then an error occurred. Now when publishing, a script is checked for validity.
  2. TEAM-33600 When working in scripts with FormData, .has() and .getAll() methods could not be processed if the request was sent from JS code. The bug has been fixed — the methods work correctly.
  3. TEAM-34265 Improved the user creation form in Administration > Users. Removed uninformative warning about work schedule changes.
  4. TEAM-34484 If the Imports constant was used in a script with an API method, errors were incorrectly detected when checking it even if no errors were displayed when publishing the method. The behavior has been fixed — the validation is performed correctly.
  5. TEAM-34555 When deleting a workspace that is used as an optional dependency (Imports) in a script created at the module level, “TypeError: Cannot read properties of null (reading ‘find’)” occurred. This caused the settings modal window to freeze. The bug has been fixed.
  6. TEAM-34564 The values of fields of the String (markdown) and String (string) types were displayed incorrectly. The bug has been fixed. The String (markdown) field allows you to enter a value in multiple lines, while String (string) is a single-line field.
  7. TEAM-31708 If a mandatory widget field was switched to Read-only mode, the mandatory field requirement failed to reactivate. The asterisk icon next to the field was missing. The bug has been fixed.
  8. TEAM-33127 When expanding the Panel with Header widget on the app view form, the window scrollbar appeared and disappeared. The widget display has been fixed.
  9. TEAM-34042 Fixed the styles of the Live Chat Messages widget. Improved widget displaying next to other components on the item view form in BRIX mobile application.
  10. TEAM-33694 Improved the system processes of approving and sending documents for information:
  • Corrected text in the process start button on the start form.
  • Added validation to the Approval due date field. It is now impossible to specify a past date.
  • Eliminated the “Error: 5” window popping up when sending a document for information.
  1. TEAM-34137 Removed the duplicate Add Version button on the file view page in the Files workspace. You can now upload a new version by clicking the plus icon.
  2. TEAM-24165 Improved editing of the project plan. The main way to change the plan is now in edit mode from the project view form. Items from other apps open correctly in edit mode. Previously, the project view form was displayed when trying to open an item.
  3. TEAM-27950 Fixed display of tasks in the My Project Tasks widget. Tasks are now displayed for users according to the configured access rights in the Project tasks app.
  4. TEAM-28588 When accessing approval sheets in scripts, the “DocflowListType is not defined” error was returned. Now the script is executed correctly.
  5. TEAM-29206 Made improvements: if access to an app is edited, access rights are not changed or inherited for the folder tree included in it.
  6. TEAM-30365 Fixed display of a folder tree on the form of another app. Now the list of records from the required folder is correctly displayed in the window of selecting an item from a field of the App type.
  7. TEAM-31826 Optimized the page with the result of searching for items by parameters in apps for which the folder tree is enabled.
  8. TEAM-33425 In the Files workspace, errors 503 and 504 occurred when deleting a large number of files from the trash. The errors have been fixed.
  9. TEAM-33525 In the Files workspace, the “Cannot read properties of null (reading ‘isFile’)” error occurred when moving several files using the Drag-and-Drop method. The error has been fixed.
  10. TEAM-33829 When uploading a file with a long name to an app form of the Document type, the buttons on the top panel were displayed incorrectly in the Upload and Preview File widget. The widget panel layout has been fixed.
  11. TEAM-33947 When opening a file after review or approval, the sidebar with properties was not displayed on the view page. The panel display has been fixed.
  12. TEAM-34011 Fixed the hasPermission and getPermissions functions for files. They now return permissions taking inheritance into account.
  13. TEAM-34361 User avatar thumbnails were displayed incorrectly if a non-square image was used. The bug has been fixed.
  14. TEAM-34423 The Project Tasks filter was not applied in the Tasks workspace. The records were displayed only after the page reloaded. The bug has been fixed.
  15. TEAM-34800 In the Signatures Archive widget, links to download a signature file looked like regular records. The display of links in the widget has been fixed.
  16. TEAM-34937 If a project file folder was deleted in the Files workspace, users could not upload documents in the project page. Now, if the project folder is deleted, it is automatically created in the Files workspace when the employee opens the project. Documents attachment works correctly.
  17. TEAM-33965 If you change the name of a published business process performance indicator and then cancel its publication, its name was not updated in the general list of indicators. Now the name is displayed correctly.
  18. TEAM-13226 Added validation to the solution export process: if an activity created at the module level is used in a business process and this module is not included in the solution, the user will see an error with a detailed description of the problem.
  19. TEAM-17188 Table column values were not passed from a child process to a parent process when variables were correctly mapped. The bug has been fixed.
  20. TEAM-19400 When publishing a business process, added check for used functions in the Script activity. Previously, if a function was deleted, the process was published without errors. Now users will not be able to publish the process.
  21. TEAM-21482 When debugging a business process, the Scripts tab did not display errors found in the compiled scripts. Now all errors are displayed correctly.
  22. TEAM-22542 An error was found when exporting a solution because of the absence of a certain group in the business process swimlane. The bug has been corrected.
  23. TEAM-31225 An error was found: if a variable was created in a business process with the same code as a variable previously removed from context, the process was not published. The bug has been fixed.
     
    Please note, starting with version 2025.3, context variables can be completely deleted via the web interface only before the business process is published. If the process version is published, assign unique codes to the variables when creating new variables.
  24. TEAM-31582 If during a business process, an app item on which the process is running was deleted using the delete() method in a script, the process execution was interrupted at that step. The bug has been fixed.
  25. TEAM-34031 Fixed the Email notification text about a new task. Users will now see a notification saying “You’ve been assigned a new task”.
  26. TEAM-34234 The customized business process start event form was not migrating to another company when exporting a process as part of a solution. The bug has been fixed.
  27. TEAM-34303 If a Chart widget is created with a data source of the Report type and specifying a measurement by app statuses, the page did not display the result and a 404 error was displayed in the log. The bug has been fixed.
  28. TEAM-34620 The API method to retrieve a list of process instances (GET /pub/v1/bpm/instance/bytemplateid/{id}/list) was not executed, and an error was displayed in the request response. The behavior has been fixed. If the query is incorrect, the user will see a detailed error.
  29. TEAM-16957 Found a bug: more than one user could be added to a group of the Role type if you specify the role in the user page. The bug has been fixed.
  30. TEAM-18975 Fixed generation of the code that is assigned to an app status when it is created. Previously, spaces were replaced with dashes, which prevented the status from being referenced in scripts.
  31. TEAM-20407 The component import process now checks whether a page, workspace, or app is locked. Previously, components could be imported but remained inaccessible due to locking. Now the user will see a user-friendly error message in the import process.
  32. TEAM-22916 Now when creating a solution, a separate field shows the generated solution code and the user can edit it.
  33. TEAM-28713 When the status of an app item was changed during a business process using a script or activity, its page did not display the new status. The bug has been fixed.
  34. TEAM-28824 Fixed the layout in the access restriction notification window. Added proper spacing to the list of users who can grant access.
  35. TEAM-29144 Fixed the display of the cross icon in the search bar at the top of the page. Previously, the icon was displayed even when the row was empty.
  36. TEAM-31841 The Allow bulk editing option could not be activated in the app form settings. The user checked the option, followed the steps for bulk editing, but the changes were not applied to the selected items. The bug has been fixed.
  37. TEAM-33308 In BRIX mobile application for IOS devices, the three dot icon for creating a new item was not displayed on the app pages. The bug has been fixed.
  38. TEAM-34177 If solutions with the same codes were imported into a company, conflicts occurred when updating the solutions. The bug has been fixed.
  39. TEAM-34262 Found a bug when attempting to copy a custom app to a system workspace. The bug has been fixed. The app is now added correctly.
  40. TEAM-34263 If the user enabled ascending or descending sorting for a field of the Date/Time type in the Kanban board settings, the sorting was not applied on the app page. The bug has been fixed.
  41. TEAM-34264 If the Create an app item action was configured in the Button widget, the item page did not open after filling out the creation form. The bug has been fixed.
360010947000.html 2025_2.html