278 lines
47 KiB
HTML
278 lines
47 KiB
HTML
<!DOCTYPE html>
|
||
<html lang="en">
|
||
|
||
<head>
|
||
<title>2024.5</title>
|
||
<meta name="generator" content="Help+Manual" />
|
||
<meta name="keywords" content="" />
|
||
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
|
||
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
|
||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||
<meta name="description" content="Here is the list of changes that you can explore right now by activating the BRIX demo version." />
|
||
<meta name="picture" content="" />
|
||
<meta property="og:type" content="website" />
|
||
<meta property="og:title" content="Full documentation for BRIX365 platform. Low-code developer guide. User guide. Admin guide. Developer guide." />
|
||
<meta property="og:url" content="https://brix365.com/en/help" />
|
||
<meta property="og:image" content="" />
|
||
<link rel="icon" href="favicon.png" type="image/png" />
|
||
|
||
<link href="https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700&display=swap" rel="stylesheet" />
|
||
<link rel="stylesheet" href="./jquery-ui.min.css" />
|
||
<link rel="stylesheet" href="default.css" />
|
||
<link rel="stylesheet" href="./search-yandex.css" />
|
||
<link rel="stylesheet" href="./article.css" />
|
||
<link rel="stylesheet" href="./glossary.css" />
|
||
<link rel="stylesheet" href="./theme.css" />
|
||
<script type="text/javascript" src="jquery.js"></script>
|
||
<script type="text/javascript" src="helpman_settings.js"></script>
|
||
<script type="text/javascript" src="helpman_topicinit.js"></script>
|
||
|
||
<script type="text/javascript" src="highlight.js"></script>
|
||
<script type="text/javascript">
|
||
$(document).ready(function(){highlight();});
|
||
</script>
|
||
</head>
|
||
|
||
<body>
|
||
|
||
<script>!function(e,t,c,n,r,a,m){e.ym=e.ym||function(){(e.ym.a=e.ym.a||[]).push(arguments)},e.ym.l=1*new Date;for(var s=0;s<document.scripts.length;s++)if(document.scripts[s].src===n)return;a=t.createElement(c),m=t.getElementsByTagName(c)[0],a.async=1,a.src=n,m.parentNode.insertBefore(a,m)}(window,document,"script","https://mc.yandex.ru/metrika/tag.js"),ym(83179930,"init",{clickmap:!0,trackLinks:!0,accurateTrackBounce:!0,webvisor:!0})</script><noscript><div><img alt=""src=https://mc.yandex.ru/watch/83179930 style=position:absolute;left:-9999px></div></noscript>
|
||
|
||
<header class="header elma-365">
|
||
<div class="container">
|
||
<a class="header__logo" href="https://brix365.com/en/help">
|
||
<img src="./logo-en.svg" alt="header logo">
|
||
</a>
|
||
<!-- <div class="hero__search-form" id="search-panel">
|
||
<form class="search-form" onsubmit="ym(83180416,'reachGoal','poisk')">
|
||
<label class="search-form__label">
|
||
<span id="reset-search" class="search__icon"></span>
|
||
<input class="search-form__input" type="text">
|
||
</label>
|
||
<input class="search-form__submit" type="submit" value="Submit">
|
||
</form>
|
||
</div> -->
|
||
|
||
<div class="hero__search-form" id="search-panel"> <form class="search-form"> <label class="search-form__label"> <span id="reset-search" class="search__icon"></span> <input class="search-form__input" type="text"> </label> <input class="search-form__submit" type="submit" value="Submit"> </form> </div>
|
||
<div class="hero__search">
|
||
<a href="#" id="search-icon" class="hero__search-icon">
|
||
<img src="search-icon-white.svg" alt="search string">
|
||
</a>
|
||
<a href="#" id="side-menu-icon" class="hero__side-icon">
|
||
<img src="side_menu.svg" alt="side menu">
|
||
</a>
|
||
</div>
|
||
<div class="header__navi">
|
||
|
||
<ul class="header__list"><li><span class="solution-select"><span class="solution-select__selected"></span><svg width="7" height="4" viewBox="0 0 7 4" fill="none" xmlns="http://www.w3.org/2000/svg"><path d="M1 1L3.5 3.5L6 1" stroke="white" stroke-linecap="round" stroke-linejoin="round"/></svg><ul class="solution-select__list"><li><a class="project-link" href="https://brix365.com/en/help/platform/get-trial.html">Platform</a></li><li><a class="project-link" href="https://brix365.com/en/help/ecm/ecm-functions.html">ECM</a></li><li><a class="project-link" href="https://brix365.com/en/help/crm/crm_overview.html">CRM</a></li><li><a class="project-link" href="https://brix365.com/en/help/service/service-functions.html">Service</a></li><li><a class="project-link" href="https://brix365.com/en/help/projects/projects-functions.html">Projects</a></li><li><a class="project-link" href="https://brix365.com/en/help/business_solutions/-elma365-store.html">Business Solutions</a></li></ul></span></li><li><a href="https://api.brix365.com/en/" target="_blank">API</a></li><li><a href="https://tssdk.brix365.com/" target="_blank">SDK</a></li></ul>
|
||
|
||
|
||
</div>
|
||
</div>
|
||
|
||
</header>
|
||
|
||
|
||
|
||
|
||
<main class="main container">
|
||
|
||
<aside class="sidebar" id="sidebar">
|
||
<div class="sidebar__header">
|
||
<a class="header__logo" href="https://brix365.com/en/help">
|
||
<img src="./logo-light-en.svg">
|
||
</a>
|
||
<span class="sidebar__close elma-365-close" id="close"></span>
|
||
</div>
|
||
<div class="sidebar__wrapper" id="side-menu">
|
||
|
||
</div>
|
||
</aside>
|
||
|
||
<article class="article" id="article">
|
||
<div class="article-inner">
|
||
<div class="content">
|
||
<header class="article__header">
|
||
<div class="article__bread" style="display:flex; gap:10px;">
|
||
<span id="subcategory" class="search-res__item-category search-res__item-category_subcategory subcategory article__badge"></span>
|
||
|
||
<div class="topic__breadcrumbs">
|
||
<p>New releases > BRIX SaaS / 2024.5</p>
|
||
</div>
|
||
|
||
</div>
|
||
<div class="topic__title"><h1 class="p_Heading1"><span class="f_Heading1">2024.5</span></h1>
|
||
</div>
|
||
|
||
</header>
|
||
<section class="article__content">
|
||
<div class="scroll-top-inner">
|
||
<a href="#h1-article" class="scroll-top"></a>
|
||
</div>
|
||
<!-- Placeholder for topic body. -->
|
||
<p class="p_Normal"><span style="color: #394149; background-color: #ffffff;">Here is the list of changes that you can explore right now by activating the BRIX demo version.</span></p>
|
||
<p class="p_Normal"><span style="color: #394149; background-color: #ffffff;">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.</span></p>
|
||
<p class="p_Normal"> </p>
|
||
<p class="p_Normal"><span style="font-weight: bold; color: #394149; background-color: #ffffff;">Introducing the #BreakingChangeAlert Tag</span></p>
|
||
<p class="p_Normal"><span style="color: #394149; background-color: #ffffff;">To improve the update process and enhance your awareness of significant changes, we are introducing a new tag </span><span style="font-weight: bold; color: #394149; background-color: #ffffff;">#BreakingChangeAlert</span><span style="color: #394149; background-color: #ffffff;">. This tag will be used to denote critical changes that may affect the operation of your system.</span></p>
|
||
<p class="p_Normal"><span style="color: #394149; background-color: #ffffff;">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.</span></p>
|
||
<p class="p_Normal"> </p>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Reports</span></h2>
|
||
<p class="p_Normal"> </p>
|
||
<p class="p_Normal"><span style="color: #394149; background-color: #ffffff;">1. </span><span style="font-family: 'Times New Roman',Times,Georgia,serif;">TEAM-21844 A feature has been added to select a business process in the data source for the report:</span></p>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal"><span style="font-family: 'Times New Roman',Times,Georgia,serif;">If the data source name is not filled, it is automatically pulled from the collection name;</span></li><li class="p_Normal"><span style="font-family: 'Times New Roman',Times,Georgia,serif;">The report columns use the business process context;</span></li><li class="p_Normal"><span style="font-family: 'Times New Roman',Times,Georgia,serif;">For filtering report columns, the </span><span style="font-family: 'Times New Roman',Times,Georgia,serif; font-weight: bold;">Search and Sort</span><span style="font-family: 'Times New Roman',Times,Georgia,serif;"> function must be enabled in the process context;</span></li><li class="p_Normal"><span style="font-family: 'Times New Roman',Times,Georgia,serif;">Data export, usage of the report in the </span><span style="font-family: 'Times New Roman',Times,Georgia,serif; font-weight: bold;">Table</span><span style="font-family: 'Times New Roman',Times,Georgia,serif;"> widget, and visualization of the business process report in the </span><span style="font-family: 'Times New Roman',Times,Georgia,serif; font-weight: bold;">Chart</span><span style="font-family: 'Times New Roman',Times,Georgia,serif;"> widget are available for reports;</span></li><li class="p_Normal"><span style="font-family: 'Times New Roman',Times,Georgia,serif;">The report can be generated considering the access rights to the process context (enabled upon request).</span></li></ul>
|
||
<p class="p_Normal"> </p>
|
||
<p class="p_Normal"><span style="color: #394149; background-color: #ffffff;">2. TEAM-27568 </span><span style="font-family: 'Times New Roman',Times,Georgia,serif;"> It is now possible to merge data sources by linking them via fields:</span></p>
|
||
<ul style="list-style-type:disc">
|
||
<li style="line-height: 1.20; margin-top: 0; margin-right: 0; margin-bottom: 0;"><span style="font-family: 'Times New Roman',Times,Georgia,serif;">App with a custom app and vice versa;</span></li><li style="line-height: 1.20; margin-top: 0; margin-right: 0; margin-bottom: 0;"><span style="font-family: 'Times New Roman',Times,Georgia,serif;">Identifier and custom app and vice versa.</span></li></ul>
|
||
<p class="p_Normal"> </p>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Scripts</span></h2>
|
||
<p class="p_Normal"> </p>
|
||
<p class="p_Normal"><span style="color: #394149; background-color: #ffffff;">1. TEAM-27099 Server scripts for widgets are now sent to the queue with increased priority.</span></p>
|
||
<p class="p_Normal"><span style="color: #394149; background-color: #ffffff;">2. TEAM-27677 The version of Node.js for executing server scripts has been updated to v16.20.2 </span><span style="color: #b30000; background-color: #ffffff;">#BreakingChangeAlert</span></p>
|
||
<p class="p_Normal"> </p>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Document management</span></h2>
|
||
<p class="p_Normal"> </p>
|
||
<p class="p_Normal"><span style="color: #394149; background-color: #ffffff;">1. TEAM-26432 A </span><span style="font-weight: bold; color: #394149; background-color: #ffffff;">Schedule in calendar</span><span style="color: #394149; background-color: #ffffff;"> tab was added for the </span><span style="font-weight: bold; color: #394149; background-color: #ffffff;">Send document/app item</span><span style="color: #394149; background-color: #ffffff;"> actvity. o enable the tab, a time limit must be set.</span></p>
|
||
<p class="p_Normal"> </p>
|
||
<p class="p_Normal"><span style="color: #394149; background-color: #ffffff;">2. TEAM-26807 To speed up the loading of the </span><span style="font-weight: bold; color: #394149; background-color: #ffffff;">Document Categorization</span><span style="color: #394149; background-color: #ffffff;"> 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.</span></p>
|
||
<p class="p_Normal"> </p>
|
||
<p class="p_Normal"><span style="color: #394149; background-color: #ffffff;">3. TEAM-26818 The process of creating a new folder in the </span><span style="font-weight: bold; color: #394149; background-color: #ffffff;">Files</span><span style="color: #394149; background-color: #ffffff;"> 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.</span></p>
|
||
<p class="p_Normal"><span style="color: #394149; background-color: #ffffff;">4. TEAM-27170 The templater now supports the currency CNY.</span></p>
|
||
<p class="p_Normal"> </p>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Projects</span></h2>
|
||
<p class="p_Normal"> </p>
|
||
<p class="p_Normal"><span style="color: #394149; background-color: #ffffff;">1. TEAM-13807 </span><span style="font-weight: bold; color: #394149; background-color: #ffffff;">Project subscription management</span><span style="color: #394149; background-color: #ffffff;">: users have access to an icon for managing their subscription to project events. They can subscribe to or unsubscribe from events.</span></p>
|
||
<p class="p_Normal"><span style="color: #394149; background-color: #ffffff;">Solutions for automatic subscription in specific cases are provided through business processes or modules using TS SDK methods.</span></p>
|
||
<p class="p_Normal"> </p>
|
||
<p class="p_Normal"><span style="color: #394149; background-color: #ffffff;">2. TEAM-16461 </span><span style="font-weight: bold; color: #394149; background-color: #ffffff;">Enhancement of the Project Documents widget</span><span style="color: #394149; background-color: #ffffff;">. A button has been added to return to the project folder for easier navigation.</span></p>
|
||
<p class="p_Normal"> </p>
|
||
<p class="p_Normal"><span style="color: #394149; background-color: #ffffff;">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.</span></p>
|
||
<p class="p_Normal"><span style="color: #394149; background-color: #ffffff;">Now, when saving and publishing the plan, a new UUID v7 is generated in the field </span><code><b>_ganttElementId</b></code><span style="color: #394149; background-color: #ffffff;"> (Gantt Chart Element Identifier) for project plan items.</span></p>
|
||
<p class="p_Normal"> </p>
|
||
<p class="p_Normal"><span style="color: #394149; background-color: #ffffff;">4. TEAM-26683 The graphical representation of project plan comparisons has been changed.</span></p>
|
||
<p class="p_Normal"> </p>
|
||
<p class="p_Normal"><span style="color: #394149; background-color: #ffffff;">5. TEAM-26740 A search function has been added to the </span><span style="font-weight: bold; color: #394149; background-color: #ffffff;">Project files</span><span style="color: #394149; background-color: #ffffff;"> widget, allowing for searching within files in the project folder.</span></p>
|
||
<p class="p_Normal"> </p>
|
||
<p class="p_Normal"><span style="color: #394149; background-color: #ffffff;">6. TEAM-27154 Improved resilience of the mechanism for launching business processes from the calendar plan.</span></p>
|
||
<p class="p_Normal"> </p>
|
||
<p class="p_Normal"><span style="color: #394149; background-color: #ffffff;">7. TEAM-27232 An </span><code><b>await</b></code><span style="color: #394149; background-color: #ffffff;"> function has been added for asynchronous operations in the system process script for template generation.</span></p>
|
||
<p class="p_Normal"> </p>
|
||
<p class="p_Normal"><span style="color: #394149; background-color: #ffffff;">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.</span></p>
|
||
<p class="p_Normal"> </p>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Users</span></h2>
|
||
<p class="p_Normal"> </p>
|
||
<p class="p_Normal"><span style="color: #394149; background-color: #ffffff;">1. TEAM-23566 Added the ability to filter users when adding them to system groups such as </span><span style="font-weight: bold; color: #394149; background-color: #ffffff;">CRM</span><span style="color: #394149; background-color: #ffffff;">, </span><span style="font-weight: bold; color: #394149; background-color: #ffffff;">Projects</span><span style="color: #394149; background-color: #ffffff;">, and </span><span style="font-weight: bold; color: #394149; background-color: #ffffff;">Privileged Users</span><span style="color: #394149; background-color: #ffffff;">, simplifying the management of users imported from </span><span style="font-weight: bold; color: #394149; background-color: #ffffff;">Active Directory</span><span style="color: #394149; background-color: #ffffff;">.</span></p>
|
||
<p class="p_Normal"> </p>
|
||
<p class="p_Normal"><span style="color: #394149; background-color: #ffffff;">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.</span></p>
|
||
<p class="p_Normal"> </p>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Apps</span></h2>
|
||
<p class="p_Normal"> </p>
|
||
<p class="p_Normal"><span style="color: #394149; background-color: #ffffff;">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.</span></p>
|
||
<p class="p_Normal"><span style="color: #394149; background-color: #ffffff;">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.</span></p>
|
||
<p class="p_Normal"><span style="color: #394149; background-color: #ffffff;">Now, the list of items loads instantly, and related items are loaded asynchronously..</span></p>
|
||
<p class="p_Normal"> </p>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Widgets</span></h2>
|
||
<p class="p_Normal"> </p>
|
||
<p class="p_Normal"><span style="color: #394149; background-color: #ffffff;">1. TEAM-15467 Custom widgets now allow the creation of </span><span style="font-weight: bold; color: #394149; background-color: #ffffff;">Event</span><span style="color: #394149; background-color: #ffffff;"> type fields and the ability to subscribe to them.</span></p>
|
||
<p class="p_Normal"> </p>
|
||
<p class="p_Normal"><span style="color: #394149; background-color: #ffffff;">2. TEAM-23116 </span><span style="font-weight: bold; color: #394149; background-color: #ffffff;">Added a lock on the Save button during validation</span><span style="color: #394149; background-color: #ffffff;">. 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..</span></p>
|
||
<p class="p_Normal"> </p>
|
||
<p class="p_Normal"><span style="color: #394149; background-color: #ffffff;">3. TEAM-24066 In the widget builder, it is now possible to externalize nested fields for </span><span style="font-weight: bold; color: #394149; background-color: #ffffff;">App</span><span style="color: #394149; background-color: #ffffff;"> and </span><span style="font-weight: bold; color: #394149; background-color: #ffffff;">User</span><span style="color: #394149; background-color: #ffffff;"> types. Available from the </span><span style="font-weight: bold; color: #394149; background-color: #ffffff;">Properties</span><span style="color: #394149; background-color: #ffffff;"> panel under the </span><span style="font-weight: bold; color: #394149; background-color: #ffffff;">Template</span><span style="color: #394149; background-color: #ffffff;"> tab. This simplifies the work of low-coders, eliminating the need to manually fetch and map data.</span></p>
|
||
<p class="p_Normal"> </p>
|
||
<p class="p_Normal"><span style="color: #394149; background-color: #ffffff;">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.</span></p>
|
||
<p class="p_Normal"> </p>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Bugs fixed</span></h2>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="1" class="p_Normal"><span style="color: #394149; background-color: #ffffff;">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.</span></li><li value="2" class="p_Normal"><span style="color: #394149; background-color: #ffffff;">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.</span></li><li value="3" class="p_Normal"><span style="color: #394149; background-color: #ffffff;">TEAM-22616 Fixed an error that occurred when reassigning a task due to the absence of the </span><code><b>end_date</b></code><span style="color: #394149; background-color: #ffffff;"> field. Now, when reassigning a task, the </span><code><b>end_date</b></code><span style="color: #394149; background-color: #ffffff;"> field is correctly processed, and the 404 error no longer appears.</span></li><li value="4" class="p_Normal"><span style="color: #394149; background-color: #ffffff;">TEAM-22801 Fixed the display of the task counter in the </span><span style="font-weight: bold; color: #394149; background-color: #ffffff;">Tasks</span><span style="color: #394149; background-color: #ffffff;"> > </span><span style="font-weight: bold; color: #394149; background-color: #ffffff;">Project Tasks</span><span style="color: #394149; background-color: #ffffff;"> workspace.</span></li><li value="5" class="p_Normal"><span style="color: #394149; background-color: #ffffff;">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."</span></li><li value="6" class="p_Normal"><span style="color: #394149; background-color: #ffffff;">TEAM-24706 Fixed an error that prevented users without administrative rights from opening business processes in the </span><span style="font-weight: bold; color: #394149; background-color: #ffffff;">Projects</span><span style="color: #394149; background-color: #ffffff;"> 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.</span><br />
|
||
<span style="color: #394149; background-color: #ffffff;">User scenarios for launching a business process from a project's calendar plan have been modified.Only business processes from the </span><span style="font-weight: bold; color: #394149; background-color: #ffffff;">Projects</span><span style="color: #394149; background-color: #ffffff;"> section are available for selection, with connections to other sections supported through the </span><span style="font-weight: bold; color: #394149; background-color: #ffffff;">Subprocess</span><span style="color: #394149; background-color: #ffffff;"> activity.Options for linking the context of a </span><span style="font-weight: bold; color: #394149; background-color: #ffffff;">Project Plan Item</span><span style="color: #394149; background-color: #ffffff;"> and </span><span style="font-weight: bold; color: #394149; background-color: #ffffff;">Project Plan</span><span style="color: #394149; background-color: #ffffff;"> are excluded from selection.</span></li><li value="7" class="p_Normal"><span style="color: #394149; background-color: #ffffff;"> TEAM-25252 Enhanced parsing of public key attributes for digital signatures. The improvement removes unnecessary unreadable characters and increases the stability of operation.</span></li><li value="8" class="p_Normal"><span style="color: #394149; background-color: #ffffff;">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.</span></li><li value="9" class="p_Normal"><span style="color: #394149; background-color: #ffffff;">TEAM-25477 Edited the event models of the API module for connecting arbitrary messengers:</span></li></ol>
|
||
<p class="p_Normal"><span style="font-weight: bold; color: #394149; background-color: #ffffff;">Before:</span></p>
|
||
<p class="p_Normal"><span style="color: #394149; background-color: #ffffff;">Events </span><code><b>“messageOutcome”, “userInfo”, “markAsRead”</b></code><span style="color: #394149; background-color: #ffffff;"> contained an empty field </span><code><b>“channelId”</b></code></p>
|
||
<p class="p_Normal"><span style="color: #394149; background-color: #ffffff;">In events </span><code><b>“messageOutcome”, “markAsRead”</b></code><span style="color: #394149; background-color: #ffffff;"> the field </span><code><b>"channelID"</b></code><span style="color: #394149; background-color: #ffffff;"> has been removed as unnecessary (according to documentation)</span></p>
|
||
<p class="p_Normal"><span style="color: #394149; background-color: #ffffff;">In the event </span><code><b>“userInfo”</b></code><span style="color: #394149; background-color: #ffffff;">, the field </span><code><b>“channelID”</b></code><span style="color: #394149; background-color: #ffffff;"> is now filled in accordance with the documentation.</span></p>
|
||
<p class="p_Normal"> </p>
|
||
<p class="p_Normal"><span style="font-weight: bold; color: #394149; background-color: #ffffff;">Before:</span></p>
|
||
<p class="p_Normal"><span style="color: #394149; background-color: #ffffff;">Events in requests from BRIX came with empty </span><code><b>“externalMessageId”: “”, “externalUserId”: “”, “externalChatName”: “”,</b></code></p>
|
||
<p class="p_Normal"><span style="font-weight: bold; color: #394149; background-color: #ffffff;">After:</span></p>
|
||
<p class="p_Normal"><span style="color: #394149; background-color: #ffffff;">Empty fields </span><code><b>“externalMessageId”, “externalUserId”, “externalChatName”</b></code><span style="color: #394149; background-color: #ffffff;"> have been removed from all events in requests from BRIX as unnecessary.</span></p>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="10" class="p_Normal"><span style="color: #394149; background-color: #ffffff;">TEAM-25673 A bug in the process designer functionality that prevented hiding the control panel was successfully fixed. Previously, pressing the </span><span style="font-weight: bold; color: #394149; background-color: #ffffff;">Hide Panel</span><span style="color: #394149; background-color: #ffffff;"> button did not result in the expected outcome — the panel remained in place. Now the function works correctly.</span></li><li value="11" class="p_Normal"><span style="color: #394149; background-color: #ffffff;">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.</span></li><li value="12" class="p_Normal"><span style="color: #394149; background-color: #ffffff;">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.</span></li><li value="13" class="p_Normal"><span style="color: #394149; background-color: #ffffff;">TEAM-26536 Fixed the display of system fields of processes for building a report on business processes.</span></li><li value="14" class="p_Normal"><span style="color: #394149; background-color: #ffffff;">TEAM-26646 A bug in the widget designer related to the double invocation of a widget from a module when using the </span><span style="font-weight: bold; color: #394149; background-color: #ffffff;">toolbar extension group > extension zone</span><span style="color: #394149; background-color: #ffffff;"> 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.</span></li><li value="15" class="p_Normal"><span style="color: #394149; background-color: #ffffff;"> 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.</span></li><li value="16" class="p_Normal"><span style="color: #394149; background-color: #ffffff;">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.</span></li><li value="17" class="p_Normal"><span style="color: #394149; background-color: #ffffff;">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.</span></li><li value="18" class="p_Normal"><span style="color: #394149; background-color: #ffffff;">TEAM-26891 An error was corrected where translations from </span><span style="font-weight: bold; color: #394149; background-color: #ffffff;">.po</span><span style="color: #394149; background-color: #ffffff;"> 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.</span></li><li value="19" class="p_Normal"><span style="color: #394149; background-color: #ffffff;">TEAM-27038 A new option in the </span><span style="font-weight: bold; color: #394149; background-color: #ffffff;">Approval</span><span style="color: #394149; background-color: #ffffff;"> and </span><span style="font-weight: bold; color: #394149; background-color: #ffffff;">Send document/app item</span><span style="color: #394149; background-color: #ffffff;"> block has been added that allows disabling the notification of the start of approval or sending.</span></li><li value="20" class="p_Normal"><span style="color: #394149; background-color: #ffffff;">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:</span></li></ol>
|
||
<p class="p_CodeExample" style="white-space: normal; page-break-inside: auto;"><span class="f_CodeExample">async function checkFile(): Promise<</span><span class="f_CodeExample" style="font-weight: bold;">void</span><span class="f_CodeExample">> { </span><span class="f_CodeExample" style="font-weight: bold;">if </span><span class="f_CodeExample">(Context.data.file) { let file =await Context.data.file.fetch() let fileName = file.data.__name </span><span class="f_CodeExample" style="font-weight: bold;">if </span><span class="f_CodeExample">(fileName.includes(‘docx’)) { Context.data.file = undefined } } }</span></p>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="21" class="p_Normal"><span style="color: #394149; background-color: #ffffff;">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.</span></li><li value="22" class="p_Normal"><span style="color: #394149; background-color: #ffffff;">TEAM-27308 Fixed the disappearance of the search bar in project-type apps.</span></li><li value="23" class="p_Normal"><span style="color: #394149; background-color: #ffffff;">TEAM-27347 Fixed an error that caused report templates not to display in the template tree of the workspace.</span></li><li value="24" class="p_Normal"><span style="color: #394149; background-color: #ffffff;">TEAM-27517 Added the ability to view the contents of a column with the </span><span style="font-weight: bold; color: #394149; background-color: #ffffff;">Table</span><span style="color: #394149; background-color: #ffffff;"> data type in reports.</span></li><li value="25" class="p_Normal"><span style="color: #394149; background-color: #ffffff;">TEAM-27526 Fixed an error in the interface of live chat settings in the </span><span style="font-weight: bold; color: #394149; background-color: #ffffff;">Administration</span><span style="color: #394149; background-color: #ffffff;"> workspace, where the lower panel with the </span><span style="font-weight: bold; color: #394149; background-color: #ffffff;">Save</span><span style="color: #394149; background-color: #ffffff;"> button overlapped part of the settings, making them inaccessible for viewing and modification. Now the panel displays correctly below all options.</span></li><li value="26" class="p_Normal"><span style="color: #394149; background-color: #ffffff;">TEAM-27555 Corrected the callback function signature example in the </span><span style="font-weight: bold; color: #394149; background-color: #ffffff;">Business Process Activity</span><span style="color: #394149; background-color: #ffffff;">.</span></li></ol>
|
||
<p class="p_Normal"><span style="font-weight: bold; color: #394149; background-color: #ffffff;">Replaced:</span></p>
|
||
<p class="p_CodeExample" style="page-break-inside: auto;"><span class="f_CodeExample">async function callback(req: HTTPRequest): Promise<</span><span class="f_CodeExample" style="font-weight: bold;">void</span><span class="f_CodeExample">>;</span></p>
|
||
<p class="p_Normal"> </p>
|
||
<p class="p_Normal"><span style="font-weight: bold; color: #394149; background-color: #ffffff;">with</span></p>
|
||
<p class="p_CodeExample" style="page-break-inside: auto;"><span class="f_CodeExample">async function callback(req: CallbackRequest): Promise<void>;</span></p>
|
||
<p class="p_Normal"> </p>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="27" class="p_Normal"><span style="color: #394149; background-color: #ffffff;">TEAM-27559 Fixed a bug that caused the word </span><code><b>error</b></code><span style="color: #394149; background-color: #ffffff;"> to be displayed instead of a list of available live chats in the </span><span style="font-weight: bold; color: #394149; background-color: #ffffff;">Messages</span><span style="color: #394149; background-color: #ffffff;"> workspace when pressing </span><span style="font-weight: bold; color: #394149; background-color: #ffffff;">~</span><span style="color: #394149; background-color: #ffffff;">. 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.</span></li><li value="28" class="p_Normal"><span style="color: #394149; background-color: #ffffff;">TEAM-27875 An error in the system has been resolved, allowing regular users to correctly work with files attached to widgets, even when the </span><span style="font-weight: bold; color: #394149; background-color: #ffffff;">File Protection</span><span style="color: #394149; background-color: #ffffff;"> (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.</span></li><li value="29" class="p_Normal"><span style="color: #394149; background-color: #ffffff;">TEAM-28152 Fixed an error in the widget designer that prevented the </span><span style="font-weight: bold; color: #394149; background-color: #ffffff;">Field</span><span style="color: #394149; background-color: #ffffff;"> widget from being selected for further configuration. Now users can correctly select and configure this widget.</span></li><li value="30" class="p_Normal"><span style="color: #394149; background-color: #ffffff;">TEAM-28519 Fixed a bug that could cause Live Chat settings not to be saved.</span></li><li value="31" class="p_Normal"><span style="color: #394149; background-color: #ffffff;">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.</span></li><li value="32" class="p_Normal"><span style="color: #394149; background-color: #ffffff;">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.</span></li><li value="33" class="p_Normal"><span style="color: #394149; background-color: #ffffff;">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.</span></li><li value="34" class="p_Normal"><span style="color: #394149; background-color: #ffffff;">TEAM-27090 Now, when selecting the Kanban or tile display for </span><span style="font-weight: bold; color: #394149; background-color: #ffffff;">Projects</span><span style="color: #394149; background-color: #ffffff;">, the </span><span style="font-weight: bold; color: #394149; background-color: #ffffff;">Project type</span><span style="color: #394149; background-color: #ffffff;"> field is removed. This change is aimed at simplifying the project page interface without unnecessary information that was previously displayed by default.</span></li><li value="35" class="p_Normal"><span style="color: #394149; background-color: #ffffff;">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 </span><code><b> __subscribers</b></code><span style="color: #394149; background-color: #ffffff;">, previously not available for search, has been modified for use in searches.</span></li><li value="36" class="p_Normal"><span style="color: #394149; background-color: #ffffff;">TEAM-27191 From the initial configuration of the workspce, the </span><span style="font-weight: bold; color: #394149; background-color: #ffffff;">Folders and Filters</span><span style="color: #394149; background-color: #ffffff;"> separator has been removed as an outdated functionality.</span></li></ol>
|
||
|
||
<div class="bottom-nav">
|
||
|
||
<a id="prev-link" class="topic__navi_prev" href="2024_6.html">
|
||
<span class="bottom-nav__arrow bottom-nav__arrow--prev"></span> <span
|
||
class="bottom-nav__link">2024_6.html</span>
|
||
</a>
|
||
|
||
|
||
<a id="next-link" class="topic__navi_next" href="2024_4.html">
|
||
<span class="bottom-nav__link">2024_4.html</span> <span
|
||
class="bottom-nav__arrow bottom-nav__arrow--next"></span>
|
||
</a>
|
||
|
||
</div>
|
||
<!-- добавляет на страницу строку блок Была ли статья полезной? -->
|
||
<div class="feedback" id="feedback"><div class="feedback-help"><span><b>Was this helpful?</b></span><form action="" method="POST" class="feedback-form" id="feedback-form"><div class="feedback__popup feedback__popup-response" id="feedback__popup_thx" style="display: none;">Thanks for your feedback!</div><div class="feedback__popup" id="feedback__popup_why" style="display: none;"><div class="feedback__popup-header">Please specify why:</div><input type="radio" name="category" id="bad_recommendation" value="bad_recommendation"><label for="bad_recommendation">Recommendations did not help me</label><input type="radio" name="category" id="difficult_text" value="difficult_text"><label for="difficult_text">Article is hard to understand</label><input type="radio" name="category" id="no_answer" value="no_answer"><label for="no_answer">Didn`t answer my question</label><input type="radio" name="category" id="bad_header" value="bad_header"><label for="bad_header">Content does not match the topic</label><input type="radio" name="category" id="other_reason" value="other_reason"><label for="other_reason">Other</label></div><div class="feedback__popup" id="feedback__popup-other" style="display: none;"><div class="feedback__popup-header">How we can improve it?</div><textarea class="feedback__textarea" name="other" id=""></textarea><input type="submit" class="feedback__other-btn" value="Submit"></div><div class="feedback-form__btn-group"><input type="radio" name="useful" id="feedback__useful_yes" value="true"><label for="feedback__useful_yes"><img src="like.svg" class="small-img" alt="like"><spanclass="feedback-form__btn-group_yes-btn">Yes</spanclass="feedback-form__btn-group_yes-btn"></label><input type="radio" name="useful" id="feedback__useful_no" value="false"><label for="feedback__useful_no"><img src="dislike.svg" class="small-img" alt="dislike"><spanclass="feedback-form__btn-group_no-btn">No</spanclass="feedback-form__btn-group_no-btn"></label></div><select name="category"><option disabled="">Please specify why</option><option value="bad_recommendation" selected="">Recommendations did not help me</option><option value="difficult_text">Article is hard to understand</option><option value="no_answer">Didn`t answer my question</option><option value="bad_header">Content does not match the topic</option><option value="other_reason">Other</option></select><input type="submit"></form></div><div class="found_typo"><p style="margin: 0px; margin-top: 16px !important;"><span><b>Found a typo?</b></span> Select it and press <i>Ctrl+Enter</i> to send us feedback</p></div></div>
|
||
|
||
</section>
|
||
</div>
|
||
<aside class="article__sidebar" style="display:none">
|
||
<input type="checkbox" />
|
||
<div class="article__arrow"></div>
|
||
<div class="table-of-contents elma365-right" id="toc2Content">
|
||
<h3 class="h3-toc">In this topic</h3>
|
||
<nav id="toc2"></nav>
|
||
</div>
|
||
</aside>
|
||
</div>
|
||
</article>
|
||
</main>
|
||
<footer class="footer">
|
||
<div class="footer-container">
|
||
<div class="footer-mobile">
|
||
|
||
<ul class="footer-mobile__list"><li><a href="https://brix365.com/en/" target="_blank">BRIX</a></li><li><a href="https://tssdk.brix365.com/en/latest/" target="_blank">SDK</a></li><li><a href="https://api.brix365.com/en/" target="_blank">API</a></li></ul><ul class="footer-mobile__list"><li><a href="https://brix365.com/en/help/platform/get-trial.html">Platform</a></li><li><a href="https://brix365.com/en/help/ecm/ecm-functions.html">ECM</a></li><li><a href="https://brix365.com/en/help/service/service-functions.html">Service</a></li><li><a href="https://brix365.com/en/help/projects/projects-functions.html">Projects</a></li></ul>
|
||
|
||
|
||
</div>
|
||
<div class="footer-wrap">
|
||
|
||
<div><span class="mobile-question-popup">Send feedback</span><form method="POST" action class="question__popup question-xs" id="question__popup"><div class="question-wrap"><span class="close"></span><span class="title">Ask a question</span><label for="help_question" style="display: none;"></label><textarea name="help_question" id="help_question"></textarea><input type="submit" value="Send"></div></form><div class="hidden fade-in question-success-xs">Sent</div></div>
|
||
|
||
<div class="footer-flex-b">
|
||
<span class="footer-copy">© 2025 BRIX</span>
|
||
<ul class="footer-list">
|
||
|
||
<li class="footer-item">
|
||
<a href="#" class="arrow-top" style="display: block;"></a>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
</footer>
|
||
<iframe name="hmnavigation" style="display:none!important"></iframe>
|
||
<script src="./jquery-ui.js"></script>
|
||
<!--script src="//cdn.jsdelivr.net/npm/featherlight@1.7.14/release/featherlight.min.js" type="text/javascript" charset="utf-8"></script-->
|
||
<script src="./jquery.tocify.min.js"></script>
|
||
<script src="./TypoReporter.min.js"></script>
|
||
<script src="./google-search.js"></script>
|
||
<script src="./main.js"></script>
|
||
</body>
|
||
|
||
</html>
|