search string side menu

New releases > BRIX SaaS / 2024.5

2024.5

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

After June 17, 2024, all changes will become available to our clients in their active companies. Please note, the list may be expanded after the release.

 

Introducing the #BreakingChangeAlert Tag

To improve the update process and enhance your awareness of significant changes, we are introducing a new tag #BreakingChangeAlert. This tag will be used to denote critical changes that may affect 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.

 

Reports

 

1. TEAM-21844 A feature has been added to select a business process in the data source for the report:

  • If the data source name is not filled, it is automatically pulled from the collection name;
  • The report columns use the business process context;
  • For filtering report columns, the Search and Sort function must be enabled in the process context;
  • Data export, usage of the report in the Table widget, and visualization of the business process report in the Chart widget are available for reports;
  • The report can be generated considering the access rights to the process context (enabled upon request).

 

2. TEAM-27568  It is now possible to merge data sources by linking them via fields:

  • App with a custom app and vice versa;
  • Identifier and custom app and vice versa.

 

Scripts

 

1. TEAM-27099 Server scripts for widgets are now sent to the queue with increased priority.

2. TEAM-27677 The version of Node.js for executing server scripts has been updated to v16.20.2 #BreakingChangeAlert

 

Document management

 

1. TEAM-26432 A Schedule in calendar tab was added for the Send document/app item actvity. o enable the tab, a time limit must be set.

 

2. TEAM-26807 To speed up the loading of the Document Categorization workspace, especially with a large number of items, a user profile setting is now available that allows disabling the count of items. This significantly reduces the waiting time when opening the workspace, as detailed item counting is not required for many users.

 

3. TEAM-26818 The process of creating a new folder in the Files workspace has been made more intuitive and convenient. Users can finish adding a folder by simply clicking anywhere in the interface after entering the name.

4. TEAM-27170 The templater now supports the currency CNY.

 

Projects

 

1. TEAM-13807 Project subscription management: users have access to an icon for managing their subscription to project events. They can subscribe to or unsubscribe from events.

Solutions for automatic subscription in specific cases are provided through business processes or modules using TS SDK methods.

 

2. TEAM-16461 Enhancement of the Project Documents widget. A button has been added to return to the project folder for easier navigation.

 

3. TEAM-25493 Automatic generation of the project plan item identifier using uuidv4 has been implemented. In previous system versions, when generating a calendar plan via script, it was necessary to additionally generate an identifier for proper rendering and functioning of the project plan.

Now, when saving and publishing the plan, a new UUID v7 is generated in the field _ganttElementId (Gantt Chart Element Identifier) for project plan items.

 

4. TEAM-26683  The graphical representation of project plan comparisons has been changed.

 

5. TEAM-26740 A search function has been added to the Project files widget, allowing for searching within files in the project folder.

 

6. TEAM-27154 Improved resilience of the mechanism for launching business processes from the calendar plan.

 

7. TEAM-27232  An await function has been added for asynchronous operations in the system process script for template generation.

 

8. TEAM-27503 The possibility of creating illogical connections between tasks has been eliminated by prohibiting the establishment of more than one connection between two tasks.

 

Users

 

1. TEAM-23566 Added the ability to filter users when adding them to system groups such as CRM, Projects, and Privileged Users, simplifying the management of users imported from Active Directory.

 

2. TEAM-27633 When a user is removed from the system, the positions they occupied are automatically freed up. This feature prevents positions from being held by inactive or former company users.

 

Apps

 

1. TEAM-26783 Now, in the list of app items in all view modes, if a field of type App (multiple) is extended, only 10 items from this field are displayed.

Previously, displaying a large volume of related items in an app took a long time to load the initial page (about 6 seconds), and there was a long load time for related items when scrolling in the column.

Now, the list of items loads instantly, and related items are loaded asynchronously..

 

Widgets

 

1. TEAM-15467 Custom widgets now allow the creation of Event type fields and the ability to subscribe to them.

 

2. TEAM-23116 Added a lock on the Save button during validation. Now, when performing validation on forms for creating or editing app items and business process tasks, the save button is locked until the validation function is completed. This prevents repeated clicks and ensures the correct execution of the operation..

 

3. TEAM-24066  In the widget builder, it is now possible to externalize nested fields for App and User types. Available from the Properties panel under the Template tab. This simplifies the work of low-coders, eliminating the need to manually fetch and map data.

 

4. TEAM-26786 Implemented event binding when changing values in widget property settings. In the property context setting window in the widget builder, it is now possible to set a function when changing values. Now, it is not necessary to externalize a property in the widget template if you need to handle an event upon change.

 

Bugs fixed

  1. TEAM-14606 Fixed an error with incorrect display of layout in the web form builder. Now, when creating a web form in any app, the layout elements are displayed correctly.
  2. TEAM-19192 It is now possible to remove or disable TelegramBot from a live chat, even if the bot itself has been deleted. Previously, this was not possible due to a 401 error. The error has been fixed, and the functionality now works correctly.
  3. TEAM-22616 Fixed an error that occurred when reassigning a task due to the absence of the end_date field. Now, when reassigning a task, the end_date field is correctly processed, and the 404 error no longer appears.
  4. TEAM-22801 Fixed the display of the task counter in the Tasks > Project Tasks workspace.
  5. TEAM-24603 Fixed a rights issuance error during full substitution in the system. The problem was that when creating a full substitution of employee "A" for employee "B," the latter did not receive the corresponding access to the app, despite the substituted employee having full rights to the app. Now, after the substitution, employee "B" correctly sees the app and has similar access rights as employee "A."
  6. TEAM-24706 Fixed an error that prevented users without administrative rights from opening business processes in the Projects workspace. Previously, when attempting to add a process to a project task, the processes were not displayed due to an error in the access settings.
    User scenarios for launching a business process from a project's calendar plan have been modified.Only business processes from the Projects section are available for selection, with connections to other sections supported through the Subprocess activity.Options for linking the context of a Project Plan Item and Project Plan are excluded from selection.
  7.  TEAM-25252 Enhanced parsing of public key attributes for digital signatures. The improvement removes unnecessary unreadable characters and increases the stability of operation.
  8. TEAM-25405 An error in form data validation was identified and resolved: an attempt to save form settings resulted in the error "validate field view data: parse error: expected string near offset 9 of 'type'", indicating incorrect handling of strings in the data. This bug has been successfully fixed, and form saving now occurs without errors.
  9. TEAM-25477 Edited the event models of the API module for connecting arbitrary messengers:

Before:

Events “messageOutcome”, “userInfo”, “markAsRead” contained an empty field “channelId”

In events “messageOutcome”, “markAsRead” the field "channelID" has been removed as unnecessary (according to documentation)

In the event “userInfo”, the field “channelID” is now filled in accordance with the documentation.

 

Before:

Events in requests from BRIX came with empty “externalMessageId”: “”, “externalUserId”: “”, “externalChatName”: “”,

After:

Empty fields “externalMessageId”, “externalUserId”, “externalChatName” have been removed from all events in requests from BRIX as unnecessary.

  1. TEAM-25673 A bug in the process designer functionality that prevented hiding the control panel was successfully fixed. Previously, pressing the Hide Panel button did not result in the expected outcome — the panel remained in place. Now the function works correctly.
  2. TEAM-26193 Now, creating workspaces with a code starting with "ext_" is prohibited in the system. This precautionary measure is due to module identification often occurring by the "ext_" prefix, and having workspaces with such a starting code could lead to data processing errors. Thus, the change is aimed at enhancing stability and security in handling sections in the system.
  3. TEAM-26467 Fixed a bug due to which the chat history with a client was not displayed until the first message was sent; now, all correspondence loads automatically when the user logs into Livechat.
  4. TEAM-26536 Fixed the display of system fields of processes for building a report on business processes.
  5. TEAM-26646 A bug in the widget designer related to the double invocation of a widget from a module when using the toolbar extension group > extension zone on a custom view form of an app was identified and eliminated. Changes in the platform over the last six months led to a widget being activated twice when opening an app item with the specified extension zone present. This bug has been corrected, and the widget now launches only once, as initially intended.
  6.  TEAM-26812 A bug related to displaying access settings when using groups with long names has been successfully eliminated. Previously, when adding a group with a long name to access settings, part of the interface was hidden off-screen, making some control options inaccessible. Now, horizontal scrolling has been implemented on the access  settings page, allowing full visibility and control of all settings regardless of the length of the group name.
  7. TEAM-26814 A bug in the system that allowed linking a deleted property in the field for linking between apps has been successfully eliminated. Previously, users encountered a situation where, when trying to establish a link between two apps in the context of a business process, a previously deleted property was displayed in the field for linking. Now the system correctly recognizes and displays only current, non-deleted properties, eliminating confusion and potential errors in setting up processes.
  8. TEAM-26855 An error that caused a form to automatically scroll down upon opening if it had certain types of fields placed above a table was corrected. Now the form remains at the initial position, making it more convenient for users and eliminating the need to manually scroll back to the top of the form after opening.
  9. TEAM-26891 An error was corrected where translations from .po files were not loaded when file protection was activated in the On-Premises version. Now, even with file protection enabled, the system correctly loads and applies translations, ensuring compliance with the user-selected locale.
  10. TEAM-27038 A new option in the Approval and Send document/app item block has been added that allows disabling the notification of the start of approval or sending.
  11. TEAM-27044 An error related to the incorrect reset of a file in a module widget was corrected. Previously, under certain conditions, the file was not completely removed from the widget context, causing data duplication when a file was re-added. Now files are correctly removed from the form through the context:

async function checkFile(): Promise<void> { if (Context.data.file) { let file =await Context.data.file.fetch() let fileName = file.data.__name if (fileName.includes(‘docx’)) { Context.data.file = undefined } } }

  1. TEAM-27219 Fixed an error in the file preview system related to adding new file versions with different extensions. Previously, the preview did not update automatically when the file type changed, requiring manual page refresh for correct display. Now, file previews update instantly without additional user actions, enhancing interaction with documents of various formats.
  2. TEAM-27308 Fixed the disappearance of the search bar in project-type apps.
  3. TEAM-27347 Fixed an error that caused report templates not to display in the template tree of the workspace.
  4. TEAM-27517 Added the ability to view the contents of a column with the Table data type in reports.
  5. TEAM-27526 Fixed an error in the interface of live chat settings in the Administration workspace, where the lower panel with the Save button overlapped part of the settings, making them inaccessible for viewing and modification. Now the panel displays correctly below all options.
  6. TEAM-27555 Corrected the callback function signature example in the Business Process Activity.

Replaced:

async function callback(req: HTTPRequest): Promise<void>;

 

with

async function callback(req: CallbackRequest): Promise<void>;

 

  1. TEAM-27559 Fixed a bug that caused the word error to be displayed instead of a list of available live chats in the Messages workspace when pressing ~. Now, the list of available live chats is displayed. If a live chat is clicked, the chat window with that live chat will open, even if there was previously communication in it.
  2. TEAM-27875 An error in the system has been resolved, allowing regular users to correctly work with files attached to widgets, even when the File Protection (Advanced Security) feature is activated. Previously, access to files through widgets was only possible for administrators, causing errors when users without administrative rights executed scripts.
  3. TEAM-28152 Fixed an error in the widget designer that prevented the Field widget from being selected for further configuration. Now users can correctly select and configure this widget.
  4. TEAM-28519 Fixed a bug that could cause Live Chat settings not to be saved.
  5. TEAM-16022 As part of improving the stability of BRIX, an issue with unsuccessfully imported or undeveloped apps has been resolved. Such apps, arising from failed imports, are now automatically excluded from the list available for linking in live chats.
  6. TEAM-26903 Previously, when sending messages to a live chat through the Send a Live Chat Message process activity, line breaks were not considered, which could lead to text formatting distortion. This issue has now been resolved: line breaks are correctly processed, and messages are displayed exactly as sent, maintaining the intended formatting.
  7. TEAM-27004 Improved the display of long text in process diagram blocks during editing. If the text exceeds the block boundaries, it is hidden and displayed when the cursor hovers over the block.
  8. TEAM-27090 Now, when selecting the Kanban or tile display for Projects, the Project type field is removed. This change is aimed at simplifying the project page interface without unnecessary information that was previously displayed by default.
  9. TEAM-27146 As part of system improvements, it is now possible to build reports on business processes taking into account access rights. For this, the system field  __subscribers, previously not available for search, has been modified for use in searches.
  10. TEAM-27191 From the initial configuration of the workspce, the Folders and Filters separator has been removed as an outdated functionality.
2024_6.html 2024_4.html