# 2026.9

> [HTML Version](2026_9.html)

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

After October 13, 2026, all changes will become available to our clients in their active BRIX SaaS companies. Please note, the list may grow after the release.

Please note that for BRIX On-Premises these changes will be included in the next major release 2026.10. For more information about the updated release cycle, see the [official documentation](version-support-elma365-on-premises.md).

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.

## Structure export and import

TEAM-43529 During the export, import, or update of system components or the entire configuration, the conflict resolution window now displays system names and codes (namespace.code) for all conflicting structures and their dependencies.

Previously, only custom component names were displayed when conflicts were detected. This made it difficult to find and identify objects with identical names or similar processes.

Now, the system code of each structure is displayed in parentheses next to its name, allowing you to accurately identify and distinguish the required structures.

## Authentication

1. TEAM-44588 The resetting of warnings for incorrectly entered data on login, registration, and password recovery forms has been adjusted. Now, when you clear the login or password fields, the error message automatically hides instead of remaining displayed.

2. TEAM-18752 A **Hint for the "Login" field** option has been added under **Administration > Company Settings**, allowing you to set custom tooltip text on the system authorization page. This is useful when login requires data in a specific format, such as domain authorization, rather than an email address or login name by default.

3. TEAM-44103 The transition to the new authorization mechanism (authv2), introduced in system version 2026.4, has been completed. The option to switch back to the legacy authorization scheme has been completely removed. **#BreakingChangeAlert** 

## Modules

TEAM-10850 You can now delete disabled custom modules. To do this, go to the module management page and click **Delete** in the top-right corner. Deleted modules are hidden from the main list under **Administration > Modules**. To view them, use parameter search and set the **Deleted** filter. You can restore the required module if necessary.

## Apps

TEAM-44105 Starting with version 2026.9, the ability to permanently delete app items without the option to restore them is available by default and no longer requires enabling a feature flag. This option is available on the view form of a pre-deleted item.

## Business processes

TEAM-44535 Error and escalation handling in the **Document Registration**, **Generate from File**, **Generate from Template**, and **Insert Watermark** activities has been standardized. Automatic transition along the first available branch when failures occur has been discontinued.

How activity execution has changed:

- **Document Registration**. If an error occurs, only the explicitly specified escalation transition is executed. If no such transition is configured, redirection along the first regular transition no longer occurs.

- **Generate from File**, **Generate from Template**, and **Insert Watermark**. If an error occurs and no escalation transition is selected, automatic transition along a random branch is stopped. Process execution stops, and the instance receives an error status on the current activity, similar to the behavior of other activities.

Please note that if escalation was not configured or had no target transition in active processes, such instances will begin to stop upon error after the update. We recommend checking the escalation settings in the specified activities. **#BreakingChangeAlert** 

## Tasks

1. TEAM-9150 In the **Tasks** workspace, search and filtering by the **Description** field have been added to the **My Tasks** and **Assigned by Me** pages.

2. TEAM-35207 Navigation to business process tasks from user interfaces has been adjusted. Now, clicking a task—from a Kanban board, an item page, the outbound tasks list, and so on—opens the task itself rather than the process instance.  
In the interface, viewing the process instance page is retained for system administrators on pages in the **Administration** workspace: **Process Monitor**, **Error Monitor**, **Bulk Operations**, and **Archiving of Process Instances**.  
For other users, navigation to the process instance remains available via a direct link, and access permissions for its data and instance actions are determined by process roles. **#BreakingChangeAlert** 

3. TEAM-44931 Data updating in the **Associated Tasks** widget has been improved. The list of associated tasks now updates automatically in real time upon any changes: creation, editing, or completion of tasks and checklist items.  
A full widget reload and abrupt visual page refresh no longer occur. Data is loaded in the background and seamlessly. **#BreakingChangeAlert** 

## Company

1. TEAM-41103 You can now customize the appearance and data composition of employee pages in the **Company > Employees** workspace.  
To do this, create a custom widget in a module and select the **User extension zone** category and the new **Employee Page in the Company workspace** zone in its settings. The created widget allows you to display any required fields from employee pages on the employee list page.  
If no special widget is connected, pages are displayed using standard logic: employee name, job title, absence status, and delegation information.

2. TEAM-43962 The display of employee pages in the **Company** workspace within the mobile app has been optimized.  
Previously, tapping a page brought up a popup window with employee information, similar to the desktop app version. Now, tapping a page immediately opens the window containing employee data.

3. TEAM-40940 Loading of schedule compliance data in the **Company** workspace has been accelerated.  
Previously, opening the page requested information for all users at once. Now, data is loaded in batches as you scroll through the list.

## Calendar

TEAM-509 You can now import events from external calendars into the BRIX calendar using an **.ics** file link. Events in the calendar are automatically created, updated, and deleted in the system when modified in an external service.

Synchronization runs every 10 minutes. The list of connected sources displays the status and last update time, and when a source is removed, its associated events are deleted from BRIX.

## Document management

1. TEAM-43568 In the **Document Categorization** workspace, you can now save folders with titles up to 1,000 characters long. Previously, specifying a name longer than 255 characters resulted in a save error.

2. TEAM-43834 When approving items via email, you can now require a mandatory comment in case of rejection.  
When a user clicks **Reject** in the email, a new tab opens with a form to enter the reason. The link is available to users authorized in BRIX via a single-use token. Once the comment is submitted, the approval task is completed.  
When clicking **Approve**, the task is still completed immediately without invoking an additional form.

3. TEAM-44915 Notifications regarding the absence of a current version have been adjusted in the item pages of **Document**-type apps and files.  
Now the warning text corresponds to the opened object: document information is displayed for app items, and file information is displayed in the **Files** workspace.

## System localization

TEAM-44894 During the installation of a new locale, validation of uploaded system resource **.po** files has been expanded.

In addition to checking the file name and type, its content is now verified. If empty values (i.e., untranslated resource strings) are found in the file, the upload is canceled and an error is displayed.

## TS SDK and API

1. TEAM-17942 You can now modify module settings via server scripts using the `Namespace.setParams()` method.  
This allows you to dynamically update any properties from the **Settings** tab without needing to manually edit parameters in the interface.

````
await Namespace.setParams(\{  
field1: value1,  
field2: value2,  
\});

2. ````
TEAM-38101 Methods for searching and retrieving a list of events from the **Calendar** workspace have been added to the public API:` GET /pub/v1/schedule/events/list` and `POST /pub/v1/schedule/events/list`. This allows you to filter and export events for integration with external services.

3. TEAM-44292 The TS SDK now allows you to retrieve and change the statuses of files and their versions:

- public `FileStatus` properties and the `FileVersionStatus` method have been added for file objects and file version objects. They allow you to query the status of a file or its version and filter objects by their relevance.

- the `setAsDraft()` method has been implemented to switch a file version to the **Draft** status with the option to specify a comment.

- when creating new versions via the addVersion and addVersionFromLink methods, specifying the version status is available.

4. TEAM-42335 The `changeLine()` method has been added to the TS SDK, allowing you to transfer a session from one live chat to another. Changing live chats is available for internal channels and live chats.

## Bugs fixed

1. TEAM-39002 When an employee opened another user's personal calendar that they were granted access to, the gear icon was incorrectly displayed on the page. Users who are not calendar owners can no longer change its settings.

2. TEAM-43674 Fixed the display of the scale on the employee schedule compliance page. Previously, it compressed vertically when the user interacted with widgets on the page.

3. TEAM-43960 Fixed spacing in user pages within the **Company** workspace when using the **V1** theme. Previously, texts containing job title or birth date information overlapped the employee name.

4. TEAM-44902 On the **Tasks** page in parameter search, fixed the operation of the filter by the **Related Object** field of type **App**, as well as the display of the delete icon.   
Previously, when the field subtype was **One**, it was still possible to specify multiple items. Now the selection is strictly limited to a single value.   
Please note that if multiple items were previously selected for a field with the **One** subtype during task search, such selection will become unavailable after the update. To work with a list of objects, we recommend ensuring that the **Many** subtype is selected for the field. **#BreakingChangeAlert** 

5. TEAM-44952 Fixed an error when calling a module-created **Script**-type action in business processes from server scripts.   
Previously, such calls duplicated request headers, resulting in a failure. Module actions now execute correctly.

6. TEAM-45335 In the **Tracing** tool from the **Administration** workspace, fixed the display of traces for business process activities and process scripts. Previously, data was not logged when selecting these objects.

7. TEAM-44962 In the resolution window during approval, the number and size of attached files were calculated incorrectly.   
When a file was deleted and re-uploaded, the counter accumulated metrics including deleted files. The indicator now displays only current data.

8. TEAM-45342 Adjusted the action menu when viewing a file attached to an app item field.   
Previously, button management was available by clicking the three dots. This capability is now hidden, as a fixed set of basic functions is used in view mode.

9. TEAM-44992 Optimized system performance during bulk file upload and deletion. Due to changes in disk space calculation logic, database load has decreased, and storage service stability has increased.

10. TEAM-45343 If a draft file from the **Files** workspace was sent for approval and then edited during the process, the approval sheet was not archived.   
The error has been fixed. When a file is modified, the approval sheet is archived, just as in **Document**-type apps.

11. TEAM-45359 Fixed an error where the timestamp was missing from the signature when using the **NUC** module.   
Now, when signing a document, the generated **.cms** file correctly contains a timestamp.

12. TEAM-45368 Eliminated the infinite loading in the signing widget that occurred when the CryptoPro provider was unavailable, for example, when the browser plugin is disabled.   
An error message is now displayed upon initialization failure, allowing you to select another provider.

13. TEAM-45436 If an attempt was made to clear a **Folder**-type field by assigning it the `undefined` value in a script, it remained populated. Resetting the value now works correctly.

14. TEAM-45400 When access to a file was denied during an API request, an incorrect response was returned, causing the downloaded file to be corrupted.   
In such cases, error code 403 is now correctly returned.

15. TEAM-37683 In the **CRM** workspace, bulk lead status changes have been adjusted:

- if automatic status change by business process is enabled for a pipeline, manual change is blocked and a warning is displayed;

- when changing statuses in bulk for multiple pipelines with an active business process, selection is limited to the first statuses of those pipelines only;

- in the **All** and **Unallocated** pipelines, the status list is sorted and grouped by pipeline.

16. TEAM-45166 Fixed an error where user actions were not displayed in the **Activity Log** widget.   
When creating or completing tasks of any type on a contact form, all events for the selected period are now correctly recorded in the activity history.

17. TEAM-43839 Previously, when switching the system language, task names and system notifications in the item feed remained in the language active when the app was created. Names and notification text now update correctly when changing the interface language.

18. TEAM-14990 Fixed an error when searching for process instances by the `\_parentID` property in client and server scripts.   
Previously, when filtering child processes via `\_parentID`, search results were incorrect or returned an empty array, for example, when comparing with the parent process ID or checking for `null`. Filtering by the `\_parentID` field in scripts now works correctly.

19. TEAM-26803 Fixed an error in filter search on the app page.   
The applied filter was reset if you opened a found item's page, navigated to the task related to the item from the **Associated Tasks** widget, and then returned to the app page by closing the item.

20. TEAM-31770 The closing order of task pages has been changed. Previously, if you sequentially opened an item page, an associated task, and its subtask, closing the topmost task automatically closed all previous modal windows as well.   
The logic is now standardized across the entire platform: clicking the close button closes only the last (current) window, while previous ones remain open—just like in all other workspaces.   
Please note that keeping previously opened pages on the screen after closing the top window is standard and consistent for all platform elements. **#BreakingChangeAlert** 

21. TEAM-43591 When launching a process or creating a new app item using a button from a form, a data format error occurred: "cannot unmarshal string into field of type REF\_ITEM", if an input parameter of the **Arbitrary App** type was mapped to the current app item in the settings.

22. TEAM-44352 When importing a solution or workspace, selection restriction settings for **Users**-type context variables were not transferred. User groups in the condition were reset.

23. TEAM-44828 In the **Tasks** workspace, the display of tasks on the **Assisting** page has been aligned with the **My Tasks** and **Assigned by Me** pages: the list is now formed from tasks rather than process instances.   
Please note that completed **CRM** tasks will no longer appear in the **Assisting** list, and returning active **CRM** tasks will require resaving them. **#BreakingChangeAlert** 

24. TEAM-43346 Fixed an error where property access settings for app items were reset when importing or updating a solution.

25. TEAM-43538 If you exported an app to an **.e365** file, deleted it from the company, and then imported the file back, the app was restored. However, it updated with errors: new items were not created, and attempting to open existing ones resulted in a 404 error.   
In this scenario, a new app is now imported without attempting to restore the deleted one.

26. TEAM-44597 When uploading **.xlsx** files with app data into the system, the **Created by** field was populated incorrectly:

- upon import into another company, the incorrect user ID from the file was inserted into the field. The user performing the upload is now automatically specified as the author;

- upon import into the current company, data for existing items was overwritten. The original field value is now preserved.

27. TEAM-44740 In workspaces with a large number of apps, when attempting to view the full list of records in group settings using the **More** button, created group names were duplicated. The data loading error has been fixed, and the list is now generated correctly without duplication.