New releases > BRIX SaaS / 2025.4

2025.4

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

After May 20, 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.

Low-code CI / CD

TEAM-21573 In Administration > Developer Tools > Low‑code CI / CD, we have improved how the configuration component selection tree looks when creating or editing an exchange profile. Now, each entry has an icon showing the component type in the system.

Business and work calendar

TEAM-34383 The user page now displays the business calendar set for the user.

Business processes

  1. TEAM-8288 We have improved how the update button works on the Process Monitor page. Now, it only appears when a new process version is published and an update is available.
  2. TEAM-34867 We have added color indication of process instances on the Process Monitor and Error Monitor pages. Entries in the list are highlighted as follows:
  • Blue. The instance is in progress.
  • Crossed out blue. The instance finished.
  • Red. An error occurred in instance execution.
  • Crossed out gray. The instance terminated.
  1. TEAM-21923 In the settings of the Start Process activity, the option to open the diagram of a selected subprocess in a separate tab has been added. This won’t work for system processes or if the process is created in a locked imported solution.
  2. TEAM-12068 When modeling a process, the designer automatically saves the changes made. It is performed before opening and closing the process form designer. The option is enabled with the allowSaveProcessBeforeAndAfterWidgetForm feature flag.
     
    The option allows you to save unpublished changes on the Context, Statuses, Forms, and Scripts tabs even if you have not clicked the Save button on the settings forms.
     
    Please note, when using this option, you can save accidental changes to the draft process.

Modules

TEAM-32435 In the module settings, when creating a business process activity of the Call process type, you can now use the option to remove the custom form of mapping input and output attributes (binding).

TO-DO list

TEAM-31342 In Administration > TO‑DO List, the table display has been improved. Now, the page shows only components that use a TO-DO widget or activity.

Apps

TEAM-23153 We have improved user experience when deleting items in bulk on an app page. Now, after deleting the allowed number of items, the list is refreshed and subsequent pages with remaining items are displayed.

User groups

TEAM-34532 We have standardized how the user group selection window looks across the interface. It now works the same way when adding group members or users in the Role type field, selecting executors in the process swimlanes, in permissions settings, etc.

Access permissions

TEAM-31562 When configuring access at the app item level, it is now possible to specify additional system fields: Subscribers and Task executors.

Structure import and export

  1. TEAM-32057 When importing a solution or app with configured registration and specified document categorization, it is checked if folders are available in the company where the components are imported. If conflicts are detected, a warning will appear. The user will be able to leave the current document categorization settings or update them.
  2. TEAM-34395 When importing system components for the Table data type, columns are now merged when updating:
  • New columns are added.
  • Column codes are checked for duplicates. If matches are found, existing columns in the table will not be replaced. The user sees an error on update check.
  • Existing columns are not deleted if they are unavailable in the imported component.

Substituting users

TEAM-30567 In Administration > Company > Substitutions, when creating a substitution, you can now select which tasks to reassign to the substitute:

  • Tasks with a due date that falls within the substitution period.
  • All tasks of the absent person.

Document management

  1. TEAM-34783 In the mobile version of BRIX application, you can now perform tasks for approving and reading a file from the Files workspace when the file is sent in a process. Previously, this could be done only in the desktop version.
  2. TEAM-35021 In the mobile version of BRIX application, it is now possible to change the content of files from the Files workspace. For this purpose, an Edit button has been added to the file view page.
  3. TEAM-34784 We have improved user experience when sending a file from the Files workspace for approval and reading. The file view page now displays clear icons for these actions.
  4. TEAM-34803 In the Document Versions widget placed on the Document type app form, you can now print a file with a watermark set in the app settings.
  5. TEAM-34879 For business process tasks that require signing of items or files, you can now limit which e-signature providers are available. This works just like the settings in the Sign activity.

Projects

  1. TEAM-24738 The calculation of the actual completion date has been corrected in project tasks. Previously, when changing the completion percentage, the value did not change and coincided with the task start date specified when the task was created.
  2. TEAM-35230 We have improved user experience when linking tasks in the project schedule. Previously in complex plans, link point icons might not be displayed, hiding behind connecting lines.
  3. TEAM-35000 We have improved the process of returning a project from the archive. Now completed tasks retain their status, all other tasks are restored with the Draft status.

Service

  1. TEAM-34161 We have optimized the principle of linking messages to sessions in live chats with connected email. Previously, messages were linked to each other based on the session ID contained in the email body. This method was inconvenient, for example, if a user manually cleared the correspondence history when replying to an email, the reply would not be linked in BRIX with the original message.
     
    Now, emails are linked to each other based on metadata, which allows you to build a correct chain of correspondence without taking into account the body of the email.
  2. TEAM-34366 In live chats with connected email on the session page, we fixed the layout of attached images and added the ability to enlarge them to their original size.

Telephony

TEAM-33581 In Administration > Set Up Call, you can now export call page and call summary page settings and import them to another company.

CRM

TEAM-35339 In Tasks > CRM Tasks, you can now view only overdue tasks in a separate tab.

TS SDK and API

  1. TEAM-34103 We have implemented the toJSON() method for built-in data types. Now when the toJSON.stringify method is called in scripts for Table data type, correct serialization is performed:
  2. TEAM-30201 There is a new getStatus method for System.signs to get the signature status of an app item.

/**
 
  * @param app The link to the app item which signature status you want to get.
 
  * @param userID Optional parameter. User ID, if not specified, the result will return the current signature status of the item.
 
  * @returns A set of key-value pairs, where key is a signature type (attributes, file), value is a signature status of this type.
 
  * ```typescript
 
  * // Example of getting the current signature status
 
  * const userID = Context.data.user;
 
  * const app = Context.data.document;
 
  * const signStatus = await System.signs.getStatus(app, userID);
 
  *
 
  * const attributes_status = signStatus[SignType.Attributes] ?? SignStatus.Unknown;
 
  *
 
  * const file_status = signStatus[SignType.File] ?? SignStatus.Unknown;
 
  * ```
 
  */
 
  getStatus(app: RefItem, userID?: string): Promise<EntityStatus>;
 
*/

  1. TEAM-33717 We have corrected the parseSpreadsheet method when applied to files uploaded to S3 storage. The parseSpreadsheet method now works without the need to write the file to S3. Previous versions of custom scripts will also run and require no changes.
  2. TEAM-18028 The Translator object is revised in TS SDK. The T() method is added. It can accept the second locale argument — the locale code for translating the string.
     
    The getLanguage() method is added to the CompanyInfo object, which returns information about company locale in {code: string, name: string} format.
     
    #BreakingChangeAlert
  3. TEAM-29022 There is a new Web API method for working with arbitrary string data. The method is an external representation of already existing methods in TS SDK.
     
    Please note, the method is experimental and may be changed or removed in the future. To call the method, the user must have administrator permissions.

// access to global system data
  GET /storage/system/{key}
  POST /storage/system/{key}
  DELETE /storage/system/{key}
 
// access to workspace data
  GET /storage/{namespace}/{key}
  POST /storage/{namespace}/{key}
  DELETE /storage/{namespace}/{key}
 
// access to app data
  GET /storage/{namespace}/{code}/{key}
  POST /storage/{namespace}/{code}/{key}
  DELETE /storage/{namespace}/{code}/{key}

Bugs fixed

  1. TEAM-32883 Two-factor authentication was ignored when it was configured in the custom module for logging in to the external portal. Users could only log in using the username and password specified during registration. The bug has been fixed.
  2. TEAM-35001 If two-factor authentication was configured for registration at the external portal and then the authorization method was changed to the standard one, an error of server request processing 500 occurred at login. The bug has been fixed. When you change the authentication option, registration is successful.
  3. TEAM-34752 Messages sent to a user when their network was disconnected did not arrive in the active chat after the connection was restored. The bug has been fixed.
  4. TEAM-19905 After customizing the business calendar, set weekends were not displayed correctly when selecting a date on app forms. The bug has been fixed.
  5. TEAM-26063 A custom form created was not visible on the main module settings page. The bug has been fixed.
  6. TEAM-30221 On the Low-code CI / CD page in the configuration components selection window for sharing, the list of widgets and pages is renamed to Interfaces to match the name of this component group in the Administration workspace.
  7. TEAM-31696 When the time zone on the local computer and in the company settings differed, the Date/Time type fields displayed an incorrect value if it was set using a script. The bug has been fixed. Now, the time is specified according to the company settings.
  8. TEAM-32791 The settings set on the main module page were not saved even if the user saw a notification about successful change of values. The bug has been fixed.
  9. TEAM-32897 Error codes in responses when calling API methods have been fixed:
  • If the user is not authorized:

Response code: 401
Response message: Unauthorized

  • If the user has insufficient permissions to execute the method:

Response code: 403
Response message: Forbidden 

#BreakingChangeAlert

  1. TEAM-33051 Fixed a bug that caused an Arbitrary App type field to be displayed incorrectly in the following cases:
  • On the item edit form if the Hide if the field is empty option is enabled for the field.
  • On the item view and edit forms if the field does not contain a value.
  1. TEAM-34542 The lte method in the script to restrict the selection of a value in a Date/Time type field did not work. The bug has been fixed.
  2. TEAM-34979 Script changes were not saved in an API method created at the module level. The bug has been fixed.
  3. TEAM-35140 In app item level access settings, it was possible to add permission restrictions on the Author field multiple times. The bug has been fixed. The author can now be specified only once.
  4. TEAM-35555 Server script execution data was not shown in the performance report results. The bug has been fixed.
  5. TEAM-28117 We have added background loading of file version and updating of version list on the form of Document type app. The list is now updated if a version is added by another user or changed during the process.
  6. TEAM-28949 Deletion of big files from the trash is optimized. Previously, a user might see an error that the trash could not be cleared.
  7. TEAM-32198 For Approval and Send Document/App Item activities, the specified settings for forming the task name using parameters were not applied. The bug has been fixed.
  8. TEAM-33689 An error occurred in the mobile version of BRIX application when clicking the Print button on the item page of the Document type app. The user could not exit the print mode. The print button is hidden from the app form as this feature is not available in the mobile application.
  9. TEAM-34024 The project view form supports hotkeys when copying and pasting a file from the Project Files widget.
  10. TEAM-34552 On the project page, the layout in the line indicating the version and status of the project plan is fixed.
  11. TEAM-34782 In the mobile version of BRIX application, in the Files workspace, the layout of the file list and available actions icons is fixed.
  12. TEAM-35077 The option to assign permissions is hidden for the Files type fields in apps. Permissions are inherited from the app access settings.
  13. TEAM-35330 When the Generate from Template activity was running, the name of the output file was incorrectly set if the option to convert to .pdf format was enabled. The bug has been fixed.
  14. TEAM-35515 The action confirmation text when deleting links between project tasks in the project plan is revised.
  15. TEAM-35603 The search for tasks by responsible person in the project plan was not applied. The bug has been fixed.
  16. TEAM-34541 Behavior in the Contract component is fixed. Previously, displaying items on the contract page duplicated the default settings set in the source app. You can now set custom item display settings for the contract.
  17. TEAM-34665 If a user hid the display of project tasks in the Tasks workspace in their profile settings, they continued to be counted in the total assigned tasks counter. The behavior has been fixed and the counter shows the correct value.
  18. TEAM-34781 In the mobile version of BRIX application, the button layout in the Upload and Preview File widget is fixed.
  19. TEAM-34827 Loading of the Administration > Project Settings page is optimized. Content is now updated at the same time, without delay.
  20. TEAM-7694 On the Process Monitor page, the Current filter search was not applied. The bug has been fixed.
  21. TEAM-28901 If an Email Notification activity was used in a process, instances could not be interrupted before that activity was executed. The bug has been fixed.
  22. TEAM-34812 When importing a solution that includes a module with business process actions added to it, custom action forms were not loaded into another company. The bug has been fixed.
  23. TEAM-34978 In the Deals app, access rights to related CRM tasks were incorrectly granted to the person responsible for the deal. The user could not open the task from the deal page. The bug has been fixed. Now the access, configured using the app context properties, is granted correctly.
  24. TEAM-31853 When configuring component visibility and access, groups created at the app level were not displayed. The user could only select workspace groups. The bug has been fixed.
  25. TEAM-34385 Localization of widget names on external portal template pages did not work. The bug has been fixed. The language changes depending on the workspace language, added mechanism for localization depending on the current user.
  26. TEAM-35222 When configuring the mail service in Administration > Mail > Service Settings, the selected SMTP connection security type was reset. The bug has been fixed.
  27. TEAM-35143 A script compilation error was detected when working with SOAPO integration service. Support for WSS authentication with username and password for SOAP services is added.
     
    Example of use in TS SDK:

// Create a client to SOAP service s1 with WSS authentication settings by password and username
const c = Namespace.ws.s1({
  auth: {
  kind: 'wss-username',
  password: 'pwd',
  username: 'username',
  }
})

  1. An error was detected when trying to access system workspace app via the Imports constant in a widget created at the module level. The bug has been fixed.
  2. TEAM-35555 Fixed a bug that prevent loading of information on server script requests on the Performance Report page.
  3. TEAM-34259 When using multiple Button: Download and Edit widgets, file download errors were detected. Behavior is fixed. Now the widget always displays the file that was specified in the widget settings.
  4. TEAM-35004 The process of password recovery on an external portal has been improved. If the company uses several portals, when restoring access to one of them, the link with the password will be sent to the domain from which the request was sent.