search string side menu

2026.1

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

After February 12, 2026, 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.

Workstation system requirements

TEAM-40726 In accordance with BRIX workstation requirements, system requirements for browser versions have been updated starting with release 2026.1:

  • Google Chrome (including mobile) — 111
  • Microsoft Edge — 111
  • Firefox — 114
  • Opera — 97
  • Yandex Browser — 23.5
  • Safari for macOS and iOS — 16.4

#BreakingChangeAlert

Business processes

  1. TEAM-39746 Added notification delivery about task assignment during substitution to the associated activity stream of the process or task instance.
  2. TEAM-40700 Added notification delivery about task reassignment from a blocked user to the associated activity stream of the process or task instance.
  3. TEAM-39975 Improved user experience: in the business processes list, users can now right-click a record to open its context menu and select Open in Designer in New Tab.
  4. TEAM-40021 Starting with release 2026.1, the Error Monitor page includes enhanced capabilities by default (no need to enable the enableUpdatedErrorListMonitor feature flag):
  • Search for a specific process instance by its parameters using the search bar
  • View error text and occurrence date per instance in separate table columns
  • Customize table appearance
  • Refresh error monitor data
  • Sort instances by any column

Widgets

  1. TEAM-39947 Interface Designer: widget positioning inside modal windows is now more intuitive. A dedicated icon appears next to the component. Click and hold the left mouse button on the icon to drag the widget across the form.
  2. TEAM-40226 Custom widgets now support dynamic context—a set of properties whose quantity and types are unknown at widget creation/publication time.

When creating such a widget:

  • The list of dynamic properties is defined via script in a property of the Arbitrary type.
  • The Dynamic Binding widget displays dynamic properties in the widget settings window, allowing mapping between dynamic context properties and the current context.
  • Similarly, variable binding is performed in business processes for Script actions created in a custom module.

Example: A Calculator widget can execute specific accounting operations. The available operations, their data, and calculation formulas are not predefined.

When placing the widget on a page and opening its settings, a script automatically generates the current set of operations. After selecting an operation, its input and output parameters appear for mapping.

Thus, all configuration data for executing the accounting operation is loaded into the widget via script at configuration time.

New table version

TEAM-40880 Starting with version 2026.1, the new version of the Table data type is enabled by default for field creation. The front_enable_vtable feature flag has been removed. The legacy table display version is deprecated.

EQL search

TEAM-39595 Enhanced EQL search for the Arbitrary App data type. It is now possible to formulate a query returning app items whose fields reference any record from another app.

This is achieved using an undefined item ID in UUID format (00000000-0000-0000-0000-000000000000) within the Refitem() collection item retrieval function. Previously, only exact item IDs could be specified. Example:

[contract] = Refitem('clients', 'contracts', '00000000-0000-0000-0000-000000000000') — searches for items where the contract field is populated with any record from the Clients > Contracts workspace.

Note: Previously, queries using an undefined ID returned an empty list, as exact ID matches were required. If your filters use such queries, they will now return all items containing a value in the specified field.

Company workspace

  1. TEAM-40205 Enhanced user experience and visual design across all Company workspace pages:
  • Updated layout and display of employee pages.
  • Improved alphabetical grouping. On the Birthdays page, grouping is now by blocks: today, current month, followed by each subsequent month for the next year.
  • Optimized search by name and position.
  1. TEAM-14694 For user convenience, navigating to the Company workspace now opens the first menu page—Employees. Previously, it opened the New Employees page.

Calendar

TEAM-41157 Enhanced validation for start and end date/time values when adding calendar events. Users can now create events with identical start and end date/time.

Portable services in modules

TEAM-15027 In portable services of custom modules, configuration of microservices now supports handling encrypted sensitive data—Kubernetes secrets.

Enable ConfigMap usage in values-elma365.yaml. If the portable service requires sensitive information (e.g., login and password), it is stored in Kubernetes secrets. ConfigMap then defines rules for passing these secrets to the portable service.

Developer tools

  1. TEAM-36944 To improve readability and analysis of diagnostic system data from the Performance Report tool, an Overview tab has been added to the .xlsx export file. It includes key system information and executed requests: reporting period, installed version, delivery package, system edition, user license count, and summary statistics for web and SQL requests.
  2. TEAM-40056 Enhanced user experience when configuring the Tracing tool (used for analytics of executed server scripts). Validation has been added for the retention policy and error trace retention policy fields. Incorrect values now trigger a human-readable error message, and invalid settings cannot be saved.

Structure Versioning

TEAM-40003 If structure versioning is enabled in the company via the allowVersionsSnapshots feature flag, document template version management becomes available.

Access version history by clicking the three-dot icon:

  • In Administration > Document Templates.
  • In workspace settings under Document Templates.
  • In app settings under Document Templates.

Available actions mirror other BRIX structures: compare previous and current versions, download a version file, delete or restore a previous version.

Document Management

  1. TEAM-40185 Tasks assigned to users via predefined approval/information routes now appear in the Associated Tasks widget within the file or app item page.
  2. TEAM-25799 Links to external sources in .pdf files uploaded to the Files workspace are now clickable.
  3. TEAM-39065 Attachments can now be added to automatic approval tasks created via the Approval block in a business process. The file appears next to the user’s resolution.
  4. TEAM-39091 Enhanced sending documents/files via predefined information routes:
  • Select information type in the send window: with confirmation (generating a list of informed users) or notification only (no sheet).
  • Improved clarity of confirmation-mode launch notification; initiator name is now included.
  • Notification for non-confirmation information follows the system’s standard format.
  • Completion notification added to the #Activity stream; message format adapts based on the number of users who completed the task.
  1. TEAM-40424 Expand All/Collapse All button added to the Source Settings window for managing the visibility of the added sources tree (collapsed by default).
  2. TEAM-40474 Stability and performance improvements for the WOPI module (integration with document servers via WOPI protocol).
  3. TEAM-40500 When launching a predefined approval route, the system checks for a comment. If the comment field is empty, it is excluded from the approval start notification (previously displayed even when blank).
  4. TEAM-40303 The Manage Access option for files is now hidden in the context menu when the file is open for viewing (e.g., files attached in the #Activity stream or chat).
  5. TEAM-40594 Tooltip corrected for the Exclude system fields by default option in the approval sheet archiving settings for Document-type apps.
  6. TEAM-40772 Visual alignment of file approval tasks with app item approval tasks: adjusted resolution button placement and fixed spacing in task titles.
  7. TEAM-41118 Video playback experience improved in the Files workspace: playback controls are now visible without scrolling down the preview page.
  8. TEAM-2811 Show signatures of deleted versions option added to the Signature Archive widget. If disabled, signatures of deleted signed file versions no longer appear. If enabled, signatures remain visible (downloading the .cms file is unavailable).

Table approval routes

  1. TEAM-37793 In the Approval Routes and View Approval Routes widgets, long stage names now display correctly. Additionally, stage names can be quickly selected using Ctrl+A.
  2. TEAM-38000 First Response approval mode can now be configured for table routes.

The approval task is assigned to all specified performers simultaneously. Once one user makes a decision, the task is automatically removed from others, and their status shows as Canceled in the View Approval Routes widget.

As with parallel and sequential approvals, approvers may be users, user groups, or organizational chart elements.

Projects

  1. TEAM-39145 Enhanced project plan editing experience: unsaved changes trigger a warning if the user clicks outside the edit form.

To enable in existing companies: Open the Projects app view form in Interface Designer, access the Project Plan widget settings, and click Save without changing parameters.

  1. TEAM-40783 The project page’s task list table can now display a column showing the numeric time buffer between tasks as defined on the Gantt chart.

Live Chats Workspace

  1. TEAM-36764 Event handler domain implemented: Live Chats > New Message. The handler captures:
  • Outgoing message sent in a session.
  • Incoming message received in a session.

System messages (visible in session chat but not sent to the client) are not registered. Event details include session name, message text, and type.

  1. In the Live Chats Messages widget, the By account linking method now supports displaying sessions linked to multiple app items.

Example: A company page now shows conversations with all contacts listed within it (previously limited to sessions from a single contact).

  1. TEAM-41282 A warning has been added to the Messengers and Inbox tab in live chat settings regarding potential connection instability for certain channels due to regional restrictions.

Email Workspace

TEAM-34636 Automatic spelling and punctuation check added when composing new emails. Errors are underlined in the message body.

Important: Ensure browser settings enable spelling check for text entered on web pages.

CRM

  1. TEAM-37085 Incoming Payments widget: totals can now be displayed for custom fields. In widget settings, add fields to show summed values in the Total block at the table bottom. By default, totals are calculated for Estimated payment and Received payment fields.
  2. TEAM-40476 Sales department activity history tracking can now be configured per contact referenced in a task.

Navigate to Administration > CRM > Activity Log, open the task type settings, and select the Activity Creation Rules tab. If custom properties storing multiple contacts are added to the task context, select which contacts’ interactions to track. Add App-type fields containing contacts on the task settings tab. User activities related to these app items will be saved.

Example: The Meeting task includes Lead Manager and Additional Participants properties. Enable both in activity creation rules to track interactions with each contact.

TS SDK and API

  1. TEAM-39736 On Web API pages (apps, processes, reports, etc.), the Parameters section now includes:
  • Copy example request
  • Reset custom test request and restore default example

Actions are triggered via icons to the right of the request body input field.

  1. TEAM-40439 TS SDK methods implemented for reading process metadata: System.scheme.process.
  2. TEAM-40697 TS SDK methods implemented for reading solution metadata: System.scheme.solution.
  3. TEAM-41132 TS SDK methods implemented for reading module metadata: System.scheme.module.
  4. TEAM-39367 Template functions now supported in Templater.generateText().

Watermarks can now be generated in scripts using an HTML template containing functions to process app item variables (previously only variables were supported, not functions).

Example: Pass an HTML watermark template to generateText(), where GenerateBarcode() creates a barcode from an app item variable. The resulting watermark template can be used as a parameter in applyToFile() to apply the watermark to a file.

  1. TEAM-39628 Web API methods for task operations implemented:
  • Get user-accessible task list.
  • Get incoming/outgoing/participant tasks.
  • Get subordinate user tasks.
  • Get task by ID.
  • Get available transitions.
  • Complete, reassign, update completion percentage, or modify dates.
  1. TEAM-39377 Web API and TS SDK methods for #Activity stream operations:
  • Create message.
  • Add comment to message.
  • Retrieve message or its comments.
  1. TEAM-39383 Web API methods for channel operations:
  • Get channel list.
  • Get channel messages and comments.

Full method list available in BRIX Public API documentation.

  1. TEAM-19947 SubmitTask method behavior updated:
  • If the task originates from another process instance or the script runs outside a process, the method completes only after the task is actually closed; closure errors affect script execution.
  • If the task belongs to the current process instance, the method does not wait for actual task completion (prevents deadlocks where script execution required task completion, but the task could not complete).

The enableScriptSubmitTaskDeadlock feature flag restores the previous behavior.

 

Bugs fixed

  1. TEAM-37742 When moving calendar events via drag-and-drop, warnings about detected event overlaps were not displayed. Fixed.
  2. TEAM-40411 The row deletion button was unavailable in tables on forms when the first column displayed an App-type field. Fixed.
  3. TEAM-40877 A custom widget containing a Table-type field failed to display the table on an app form when linked to an app context variable; table binding configuration was not applied. Fixed.
  4. TEAM-15013 The Administration > TO-DO List page displayed TO-DO tools from blocked paid solutions. Tools with read-only access rights are now excluded from the list.
  5. TEAM-18802 Timer-triggered business process launches incorrectly created two instances instead of one at the scheduled time. Fixed.
  6. TEAM-31346 The task completion percentage editing window in executive discipline displayed incorrectly, with the task form overlaying the percentage form. Fixed.
  7. TEAM-31571 The list of completed tasks opened from the executive discipline page displayed incorrectly: after task closure, the counter failed to update and showed an empty page. Fixed.
  8. TEAM-36765 API method context from custom modules displayed incorrectly in Interface Designer—extraneous variables appeared during script writing. Fixed.
  9. TEAM-39756 Search by parameters failed on the Administration > TO-DO List page, returning a 400 error: "Http failure response". Search now functions correctly.
  10. TEAM-40189 The Participants field mandatory status notification was missing on the Event-type app item creation form. Although validation prevented saving items without participants, the field was not visually marked as required. Fixed.
  11. TEAM-40255 The Avatar field in active external user profiles failed to display assigned values; re-saving the profile was required to populate the field. Fixed.
  12. TEAM-40256 Users could successfully authenticate on external portals with two-factor authentication enabled even when the corresponding module (e.g., SMS provider or Telegram integration) was disabled in Administration > Modules. Module deactivation did not affect 2FA availability. Fixed.
  13. TEAM-40768 Enabled custom SMS modules could not be selected in portal settings for two-factor authentication. Fixed.
  14. TEAM-36350 Debugging functions in scripts with optional dependencies added via the Imports constant triggered the error: "Property 'app' does not exist on type 'NamespaceBase<Readonly<any>> | NamespaceExtensionBase'". Fixed; script function debugging now works correctly.
  15. TEAM-40109 After installing the Security Audit module, the report table failed to display in widgets placed on pages. Fixed.
  16. TEAM-40388 Visual appearance of Phone-type fields corrected on app pages using table layout for items.
  17. TEAM-40574 Developer console incorrectly displayed multiple messages for a single app item data edit action. Fixed.
  18. TEAM-38633 After company configuration updates, some module-created widgets were incorrectly marked as deleted (not appearing in module settings lists). Manually setting __deletedAt to null temporarily restored visibility, but re-exporting configuration re-flagged them as deleted. Fixed.
  19. TEAM-39185 Redirection to the external support portal contact page corrected when clicking the button on the BRIX homepage.
  20. TEAM-40099 In some cases, the App-type field change event incorrectly triggered after server script execution. Fixed.
  21. TEAM-40912 Configuration export between companies triggered the error: "rpc error: code = AlreadyExists desc = Error importing widget system.main._header: collision". Fixed.
  22. TEAM-40916 When editing a Yes/No Switch field and then executing a configured script, the form scrolled downward unexpectedly. Fixed; form elements now maintain correct positioning during actions.
  23. TEAM-40722 Access rights for system folders in the Files workspace corrected:
  • Non-admin users' access restricted to subfolders within system folders.
  • Access management restricted for files/folders within system folders.
  • Access management restricted for app-associated files within system folders.

Users without permissions see a notification when attempting direct file access or access management.

  1. TEAM-41020 File workspace search now respects user access rights: inaccessible files are excluded from results. If a user lacks folder access, "Unavailable" appears instead of the folder name in search results.
  2. TEAM-41627 Approval sheets for Document-type apps with archiving rules failed to archive when a new property was added to the app form. Fixed.
  3. TEAM-16984 Signature provider list in Sign button and Sign block settings corrected: provider names reordered—default providers first, followed by custom providers.
  4. TEAM-32194 Validation added for Document Versions widget linkage with files from Document-type app items. When displaying versions of a custom user-uploaded file from app context, the widget shows in Read-only mode with the Make Current button disabled in the versions list.
  5. TEAM-38262 Document approval sheet archiving process launch mechanism improved when document versions are updated.
  6. TEAM-40043 Performance degradation during bulk file deletion eliminated.
  7. TEAM-40076 Form and page naming in the Contract component corrected for user convenience:
  • Initial contract setup: [Contract Name] / Form Settings
  • Field settings page after creation: Contract Fields
  • Configuration page: [Contract Name] / Contract Settings
  1. TEAM-40225 File editing attempts triggered access permission errors. File database saving mechanism corrected; issue resolved.
  2. TEAM-40289 File List widget: available file actions now correctly reflect widget settings. Example: with View Only enabled and a file filter applied, users can only open files.
  3. TEAM-40386 Excessive internal system requests for loading related contract data eliminated; performance improved.
  4. TEAM-40395 System document approval process from the Files workspace failed to launch. Fixed.
  5. TEAM-40400 Messages failed to be sent to associated activity streams for files and file versions. Fixed.
  6. TEAM-40425 Button layout on contract field settings pages corrected.
  7. TEAM-40448 When navigating from a file's activity stream to an embedded file and closing it, the original file's view form failed to reappear. Behavior corrected.
  8. TEAM-40522 File Preview widget: document layout and display corrected.
  9. TEAM-40868 Comparing the current file version via the file menu triggered an error after adding a version using the All Versions widget. Data synchronization during new version addition corrected; a file edit flag is now stored in the browser. Fixed.
  10. TEAM-40548 Folder access permissions did not grant access to nested files. File access provisioning corrected when folder-level permissions are restricted. Issue resolved.
  11. TEAM-40568 Files could not be moved between folders in the Files workspace. Folder tree construction corrected; issue fixed.
  12. TEAM-40592 Executing getDownloadUrl() to retrieve a file download link triggered the console error: "incorrect UUID length 9 in string 'undefined'". Method execution corrected.
  13. TEAM-40625 Non-admin users encountered errors when restoring files from Trash to the My Files folder. Fixed.
  14. TEAM-40681 Editing items in Document-type apps failed to save after adding or modifying files. Fixed.
  15. TEAM-40720 The file edit button was missing on Document-type app item forms in fullscreen mode. File and app item access rights validation improved; the button now displays when edit permissions exist.
  16. TEAM-40826 With the allowAddVersionFileFields feature flag enabled (tracking versioning for documents in Files-type fields), adding files to fields triggered errors. Fixed.
  17. TEAM-40891 Copying folders via the CopyDirWithChilds gRPC method incorrectly created system folders. New folders now retain non-system status.
  18. TEAM-41000 Activity stream notifications for automatic approval results failed to send. The Add a notification to the object activity stream with approval results option for automatic approval corrected. When automatic approval is selected, the Notify about each decision option is now disabled; a single completion notification is sent.
  19. TEAM-41015 When adding multiple documents to a Files-type field, users could edit the item form before file uploads completed, causing files to fail to appear in the field. A loading indicator now displays on view/edit forms, preventing changes to the file list until all uploads complete.
  20. TEAM-41030 Files added via script to item forms failed to save. Fixed.
  21. TEAM-41045 Files without format extensions in their names could not be downloaded from app item cards. Fixed.
  22. TEAM-41091 Debugging widgets with folders added via the Files tab in Interface Designer triggered errors. Folder creation logic for widgets with nested folders corrected; duplicate folder checks added with user warnings instead of errors.
  23. TEAM-41234 After adding a file version to a Document-type app item, page refresh was required to see user changes in the version. Fixed; refresh no longer required.
  24. TEAM-41252 Access rights modification failed for added folders using the Manage Access option. Fixed.
  25. TEAM-39045 Project plan approval errors occurred: the Approver field from plan context failed to display the selected user, and plans could not be approved via custom business processes. The Approve Project Plan block in custom processes now executes correctly, with approvers visible in the project plan widget.
  26. TEAM-39613 Summary tasks imported incorrectly from MS Project. Fixed; such tasks now import as stage tasks in BRIX.
  27. TEAM-39919 Project plans displayed incorrectly after exiting fullscreen mode. Fixed; Gantt chart content no longer shifts when restoring window size.
  28. TEAM-40547 Bulk actions were unavailable for project plan tasks. Selecting multiple tasks left action icons grayed out. Fixed; bulk copy, delete, and move actions restored.
  29. TEAM-40830 Deleting a task in a project plan disrupted numbering for remaining tasks. Fixed.
  30. TEAM-40931 The Create button for adding project folders was missing from project cards. Fixed; folders and files now create correctly for current and previous project versions.
  31. TEAM-34398 In Administration > Email Settings, testing connection with Other service type and Send from Reply-to address enabled triggered an empty modal window. Fixed; connection testing now functions correctly.
  32. TEAM-36969 Performance optimized for sending messages to app item-associated activity streams..
  33. TEAM-38014 In Administration > Live Chats Settings, editing New session notification and New message notification fields triggered "File not found or deleted" errors; previewing selected notification sounds was impossible. Fixed; audio player now appears after sound selection for playback.
  34. TEAM-39639 Business process context binding with app properties corrected. App-type process context properties can now accept input variables of types: App, Arbitrary App, Files, User. Important: Reverse binding (App < Arbitrary app) remains unavailable and is considered invalid.
  35. TEAM-40354 CRM workspace export failed when App-type fields were added to task form settings in Administration > CRM > Types of CRM Tasks. Fixed.
  36. TEAM-40869 Call pages failed to display above other open windows on the page. Fixed.
  37. TEAM-41076 App item retrieval failed when creating subscriber segment filters. Reproduction steps:
  • Set pre-filtering conditions for an App-type field in the Contacts app.
  • In Marketing > Segments of subscriber emails, select Contacts as filter source.
  • Add condition and select the App-type field in App field column.
  • Click <Not defined> → Enter value → magnifying glass icon.

Fixed; app items with pre-filtering conditions now correctly display in the value selection window.

  1. TEAM-20951 Multiple notifications arrived in the #Activity stream after task reassignment from a multi-type swimlane during a process. Fixed.
  2. TEAM-32539 Script access in Business Process Designer was denied to users assigned as workspace administrators at the level where the process was created. Fixed.
  3. TEAM-38148 Changing a business process context variable type from One to Many triggered errors during solution updates containing the process. Import validation corrected: if process changes are permissible, solution import is allowed.
  4. TEAM-38294 Human-readable error added when attempting to copy system business processes from blocked CRM workspaces (Call, Webinar, Meeting, Email).
  5. TEAM-39747 Editing business process names in the workspace list prevented space entry; pressing arrow keys closed the edit window. Fixed.
  6. TEAM-39943 Timer-assigned approval tasks generated email notifications with incorrect links; users could not open tasks via these links. Fixed; task links now incorporate the company's human-readable address (alias). Correctly generated links appear in notifications. Important: Alias-based link generation requires the browser URL to contain the company alias, not an arbitrary name.
  7. TEAM-40334 Business processes from modules failed to terminate when launched via Call process actions also created within the module. Fixed.
  8. TEAM-40484 Notification added when report generation is restricted due to access limitations on app fields used in the Report component.
  9. TEAM-40539 Process instances failing to resume after timer expiration entered a locked state, preventing manual or automatic (via RabbitMQ queue message processing) resumption. Fixed.
  10. TEAM-40588 Script-type business process actions in custom modules with Result Request execution model corrected. Previously, when check() returned false during execution, process flow halted. Result validation now functions correctly; processes proceed to the next step upon receiving true.
  11. TEAM-40604 Custom variable values failed to pass to business processes when calling the run() method from scripts. Fixed.
  12. TEAM-40615 Documents edited during approval/information processes failed to cancel the current sheet or terminate the process. Fixed.
  13. TEAM-40659 Ability to open system business processes from blocked workspaces removed from the Error Monitor.
  14. TEAM-40802 Asynchronously launched subprocess instances triggered the error upon completion when the parent process terminated earlier: "ContinueParent: continue parent instance: load and iterate: instance is terminated instance is terminated and Task Id dont recognized: precondition". Fixed; asynchronously launched child process instances now terminate correctly.
  15. TEAM-41021 Related Item widget: long item names now display within the bounds of the open form.
360010947000.html 2025_11.html