Here is the list of changes that you can explore right now by activating the BRIX trial version.
After August 19, 2024, all changes will become available to our clients in their active companies. Please note, the list may be expanded after the release.
To enhance the update process and increase your awareness about significant changes, we are introducing the new #BreakingChangeAlert tag. This tag will be used to mark critical changes that could impact the operation of your system. Please pay special attention to any updates marked with this tag, as they may require additional actions on your part to adapt or adjust your current configuration.
ECM
1. TEAM-25768 You can now select custom providers as the default provider in the Sign business process activity.
2. TEAM-26184 Support for exporting and importing the configuration of business process triggers when a sheet is archived has been implemented. Warnings are displayed during export for processes that are not included in the exported namespaces but are specified in the archiving settings.
3. TEAM-26954 Support for exporting and importing access rights in the document categorization system has been implemented. Access rights to the registration office and folder are transferred during the export and import of apps. If the registration office or folder already exists in the target company, rights are not overwritten. User and group-level rights are preserved when transferring between companies.
4. TEAM-27497 Sample templates for approval sheets and lists of informed users have been added to the settings for download, further editing, and re-upload.
5. TEAM-27500 The Approval Settings page has been renamed to Archiving Settings, with the added ability to specify a business process when archiving a list of informed users (previously it worked only for approval).
6. TEAM-28665 Implemented inheritance of access rights from the registration office to the category and folder. Additional rights are not updated when access rights are changed and operate separately.
Projects
TEAM-23122 In Projects, a new feature has been added to filter and search tasks when requesting work completion estimates. Users can now quickly find the required tasks in the task selection window within the Gantt chart.
TS SDK
1. TEAM-28339 A new method has been added to the BRIX SDK that allows changing the registration number after a document has been registered. Previously, users faced limitations that required deleting and re-registering the document in case of errors or typos, which was inconvenient and could lead to additional issues in administration and record-keeping.
Example usage:
```typescript
async function editReg(): Promise<void> {
const item = Context.data.dokument_s_registraciei!;
const registrations = await item.docflow().getRegistrations();
if (registrations.length <= 0) {
throw new Error('something went wrong');
}
await item.docflow().changeRegistration(registrations[0].nomenclatureId, "number1");
}
```
2. TEAM-9754 The BRIX SDK now includes the ability to retrieve a comment specified by a user when signing a document using an electronic signature.
3. TEAM-27789 The TSSDK methods for retrieving system messages in live chats have been improved. Now, with the possibility of sending system messages within a session, the `getAllMessages()` and `getLastMessage()` methods have been updated: a `payload` field has been added for the message types `payload` and . This allows for separate handling of `session_reassign_message` system messages received through these methods.
CRM
1. TEAM-23170 The Hierarchy widget now includes the ability to configure the displayed fields for the selected app. This feature expands upon the previous implementation, which was limited to the fields for the Contact app, and now covers all possible app fields except for the Table type.
2. TEAM-25031 The Activity Log widget has been enhanced with customizable field display settings:
- You can now configure fields for both system and custom activities.
- The default field output for each activity has been adjusted.
- Contact display has been added if the Activity Log contains data for more than one contact.
- A new feature allows users to collapse and expand information for activity records.
- Contact data display has been included.
3. TEAM-28489 The Bar chart widget has been improved:
- New chart types have been added: horizontal bars (with dril ldown) and vertical bars (with drill down).
- A Detailed information feature has been added for charts with drill down.
- A Status display setting is now available for sources with the App with statuses type.
- A Display settings configuration has been added to manage the list of columns when building detailed information.
4. TEAM-29295 The ability to create an empty dynamic segment for later use in lead generation has been added.
Service
1. TEAM-20787 A new parameter, Allow operators to add clients to blocklist (Yes/No switch), has been added to the global live chat settings. If Yes is selected, the option to add a client to the blocklist via the session sidebar will be available to all operators. If No is selected, this feature will be hidden from operators and only available to supervisors.
2. TEAM-23473 Added the ability to retrieve contact information from Telegram. Previously, contact details were not transmitted to BRIX when using the share contact feature in a chat or via a Telegram bot.
3. TEAM-25507 Added the ability for operators to edit messages in Telegram. A new option, Enable message editing, has been added to the global live chat settings, which is disabled by default.
- Editing is only possible for messages sent by the operator and can be done within 48 hours of sending. After this period, editing is blocked with an error notification.
- Edited messages in the chat will be marked with a pencil icon, and hovering over the icon will display the date and time of the last edit.
4. TEAM-28774 Reactive updates to the session page have been implemented after executing the Send Live Chat Response block in a business process. Previously, the message was sent to the session but only displayed to the operator after refreshing the page. Now the message appears immediately without the need to refresh the page. The update is only available to the operator assigned to the session.
Number data type
TEAM-23954 Added the ability to specify the allowed number of decimal places in a Number (non-integer) field. Previously, the display of digits after the decimal point worked as follows:
- For integer numbers, the minimum required digit was 0, and the maximum was 20.
- For decimal numbers, the minimum was 2, and the maximum was 20.
We have added the ability to specify the maximum number of displayed decimal places.
For example, if the field contains the number 3.14159:
- Integer number, maximum digit not specified: Displayed as is: 3.14159
- Integer number, maximum digit = 2: Displayed as 3.14
- Integer number, maximum digit = 0: Displayed as 3
- Decimal number, maximum digit = 4: Displayed as 3.1416
- Decimal number, maximum digit = 1: Displayed as 3.1
2FA
Support for custom 2FA providers has been implemented. To do this, you need to create an interface and function in the module script:
```typescript
interface SecondFactor_sendError {
error: string;
skip2fa: boolean;
}
async function secondFactor_sendCode(userID: string, code: string): Promise<SecondFactor_sendError> {}
```
The function accepts the identifier of the incoming user and the confirmation code. After saving and publishing, the module becomes available in the security settings.
Bugs fixed
1. TEAM-25578 A problem was identified and fixed in processes where, upon opening the Settings tab, the entire version history of the process was loaded, leading to long queries and browser overload. Now, the version history is displayed page by page, with 10 items per page, loading only when the History tab is selected. This significantly speeds up performance and prevents system overload. #BreakingChangeAlert
2. TEAM-28081 Fixed the display of the task list in the Associated tasks widget. Depending on user rights, the widget now displays either the task block name (to exclude access to sensitive information) or the task name according to the template (if sufficient rights are available). Additionally, an information window appears when attempting to open a task without sufficient rights. #BreakingChangeAlert
3. TEAM-29183 Fixed the display of the checklist in the Associated tasks widget. Previously, the checklist was not displayed. #BreakingChangeAlert
4. TEAM-28083 The _project_template app has been moved to the trash, as it was removed from the workspace logic and Help Center. Functionality in scripts where the app was previously used remains unaffected until re-publication. For continued use, modifications to scripts are required or the app must be restored from the trash. #BreakingChangeAlert
5. TEAM-23320 Fixed a bug where an edited file from the task page could not be saved if it was selected from the Files workspace. Additionally, previously added files disappeared after refreshing the page.
6. TEAM-26662 Fixed a bug in business processes where the specified value for a Money-type variable was reset to zero after saving. Data is now saved correctly, and upon reopening the block settings, the set value is displayed instead of 0.00.
7. TEAM-28781 Fixed a bug where the actual receipt amount was reset after editing the estimated amount.
8. TEAM-26759 Fixed a bug related to removing permissions for an app property, where the method perms.Delete(minus permissions.Permission) incorrectly considered OrgunitField fields.
9. TEAM-26911 Fixed a bug where client scripts did not account for replacing the current timezone for the object system.timezones.current. When creating a TDatetime object, the date and time were generated with the company's timezone instead of the timezone set for the System object.
10. TEAM-27139 TS SDK: An error was found in the TS SDK documentation describing the create method for Phone and Email objects. The method was incorrectly listed as available through Context.data, which is not accurate. The create method actually exists only for the fields object. The correct usage example is: Context.data.mail = Context.fields.mail.create('user@company.com'); The documentation error has been corrected to match the actual functionality.
11. TEAM-27297 Fixed a bug where optional dependencies were not loading in widget settings, accompanied by the error "uuid: incorrect UUID length: dictionarys". The issue occurred when trying to open page settings and select available items in the builder, where the list of items did not load.
12. TEAM-28090 Fixed a bug where server-side scripts did not work if there were properties with the same code in the app context. The problem occurred when creating and calling a server script in an app where properties with the same code were linked between two apps. An error "TypeError: STRING must be a string" occurred when trying to open an app item for viewing. The fix now allows server-side scripts to work correctly even with properties with the same code, and the error no longer occurs.
13. TEAM-29178 Fixed a bug where item_permissions_update events were not displayed in the Security Audit v2 solution, although they were correctly shown in the Security Audit v1 solution. The problem occurred when changing additional access rights to an app item — the event was only displayed in the old version of the audit.
14. TEAM-18652 Fixed a bug related to incorrect validation of required fields on an app item form when the modal window content loads asynchronously. The problem was that an app item was created without filling required fields, despite validation errors being displayed under the field.
15. TEAM-25440 Fixed a bug where Page-type widgets were unavailable in the widget builder. The issue was that the set of available widgets differed depending on where they were added: in one case, the Main page widget was available, while in another case, it was missing. The widget set is now consistently available in all cases, ensuring correct operation of the widget builder.
16. TEAM-26972 Fixed a bug where context variable validation did not trigger if there was a variable with the same code in the form context. The problem manifested as follows: when creating an app item with a custom form, despite validation triggering and displaying an error under the field, the form still closed, and the item was successfully created.
17. TEAM-28073 Fixed a bug where focus on the edit form moved from the first available field to the next. The error has been fixed.
18. TEAM-11538 Fixed an error where outdated signature information was not displayed on the sidebar if the file or document attributes were changed. Previously, after signing a file and subsequently changing it, the sidebar did not show a warning about the outdated signature, and the button to view the signature archive was unavailable. The status of the signature is now correctly displayed: if the signature is outdated, it is clearly indicated, and the signature archive is available for viewing. Additionally, issues with page freezing when signing only files or attributes have been resolved.
19. TEAM-28103 Fixed a bug where it was impossible to select a provider for signing in the standard signing task. The issue occurred in the interface when providers did not load correctly and were only available when clicking on the provider's name.
20. TEAM-28264 Fixed a bug where a project type with a modified generation process was not created. The problem occurred after exporting and re-importing the Projects solution, as well as when modifying the Generate from template process for basic and custom types.
21. TEAM-28516 A bug was identified and fixed where an error occurred during automatic approval if one of the users in the group had a substitution set up. The issue was that when starting a process with automatic approval and active substitution, the process would fail with the error "rpc error: code = FailedPrecondition desc = resolve: not permitted: precondition". This error has now been resolved.
22. TEAM-28571 A bug was identified and fixed in the Document versions widget in designer mode where an error occurred if no file was added. The issue was that the widget displayed the error "TypeError: Cannot read properties of null (reading 'id')" when no file was present.
23. TEAM-28023 The functionality for customizable Gantt chart columns and the Project plan widget has been enhanced. It now supports adding, displaying, and inline editing for data types such as Date/Time, App, Arbitrary app, User, Yes/No, and Category. Design for multiple user displays and links to app items, as well as inline editing for Yes/No fields, has also been implemented.
24. TEAM-22762 Fixed an issue in Live Chats where links in WhatsApp could be formed incorrectly and duplicated.
25. TEAM-28054 Fixed an issue in Live Chats related to sending messages containing more than 4096 characters. Previously, such messages appeared in the BRIX session but did not reach the client in Telegram. Users will now see a warning, and sending such messages will be blocked. Note: In Telegram, messages with more than 4096 characters are automatically split into multiple messages.
26. TEAM-28837 Fixed an issue with routing rule display in Live Chats. Previously, when trying to change the order of a rule by dragging, it could shift sideways, causing inconvenience. The shifting problem has now been resolved.
27. TEAM-28868 Fixed a bug that allowed creating sessions with clients without a WhatsApp account. Now, when attempting to create such a session, users will see a corresponding notification, and the session will not be created.
28. TEAM-21322 A bug was identified where a 504 Gateway Timeout error occurred when trying to open user search if many users were added to the platform and a filter was used to display them. The issue occurred when specifying a large number of users for filtering, leading to a server timeout and the inability to display the user list correctly. The error has now been resolved, and user search works correctly regardless of the number of users on the platform.
29. TEAM-23731 A bug was identified where a custom widget on the homepage did not display for users without administrator rights. The issue occurred after exporting and updating the configuration, when the widget access settings were reset. The error has now been fixed.
30. TEAM-27791 A bug was identified where it was impossible to add a dependency on a solution containing system directories when using widgets from this workspace in other solutions. The issue occurred when attempting to export a solution if a widget from system directories was placed in an app from another workspace, but the dependency on the solution with system directories could not be added. The error has been fixed.
31. TEAM-28508 A bug was fixed that occurred when calculating dependencies and editing the content of a solution if it included an app for a paid solution. Now, a custom app from a system workspace can only be included in one solution. If the system workspace is added entirely to one solution and then another solution attempts to include a custom app from that same workspace, the application will be excluded from the first solution with a corresponding notification. Checks have also been added during the export and import of solutions to avoid conflicts when using the Add workspace entirely flag.