update help elma

This commit is contained in:
2025-05-27 21:32:35 +04:00
parent a6b05d6789
commit 898b22bf32
4500 changed files with 89372 additions and 120699 deletions

414
platform/2024_6.html Normal file
View File

@ -0,0 +1,414 @@
<!DOCTYPE html>
<html lang="en">
<head>
<title>2024.6</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="Introduction of the #BreakingChangeAlert tag &nbsp;To enhance the update process and increase your awareness about significant changes, we are introducing the new..." />
<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 &gt; BRIX SaaS / 2024.6</p>
</div>
</div>
<div class="topic__title"><h1 class="p_Heading1"><span class="f_Heading1">2024.6</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="font-weight: bold;">Introduction of the</span> <span style="font-weight: bold; color: #800000;">#BreakingChangeAlert</span> <span style="font-weight: bold;">tag</span></p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">To enhance the update process and increase your awareness about significant changes, we are introducing the new <span style="font-weight: bold; color: #800000;">#BreakingChangeAlert</span> 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.</p>
<p class="p_Normal">&nbsp;</p>
<h2 class="p_Heading2"><span class="f_Heading2">Processes</span></h2>
<p class="p_Normal">TEAM-12541 A new &quot;read-only&quot; mode for administrators has been added in the process designer. It allows them to view the settings and layout of the process without the ability to edit it. This mode is activated upon request and prevents accidental modifications in critical processes. <span style="font-weight: bold; color: #800000;">#BreakingChangeAlert</span></p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">TEAM-26232 In this platform update, a feature has been added that allows for enlarging the process map window in the monitor or on the task page. Users can now open the map in full-screen mode, which greatly simplifies the analysis and navigation of complex business processes. <span style="font-weight: bold; color: #800000;">#BreakingChangeAlert</span></p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">TEAM-10589 Improved readability of business process maps. Now, the background of connector names in process diagrams is semi-transparent, which facilitates visual perception of the map.</p>
<p class="p_Normal">&nbsp;</p>
<h2 class="p_Heading2"><span class="f_Heading2">Reports</span></h2>
<p class="p_Normal">TEAM-27874 A new feature has been added to the <span style="font-weight: bold;">Report</span> app type that allows users to flexibly configure the display of columns and filters. A <span style="font-weight: bold;">Settings</span> button has been added to the report page, with the option to select <span style="font-weight: bold;">Table Settings</span>. Users can specify which columns to display, which to use for filtering, and which field to use for sorting. The list of available columns is set by the administrator when creating the report, and users can adapt their display according to their own needs. <span style="font-weight: bold; color: #800000;">#BreakingChangeAlert</span></p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">TEAM-28134 Reports now have the option to add columns with links to app items. Users can activate this feature by checking the <span style="font-weight: bold;">Link to app item</span> box when creating or editing a report. This allows each column associated with the <code><b>__name</b></code> field to display a clickable link to directly access the app item from the report. This feature is only available for reports whose data sources are of the App type. <span style="font-weight: bold; color: #800000;">#BreakingChangeAlert</span></p>
<p class="p_Normal">&nbsp;</p>
<h2 class="p_Heading2"><span class="f_Heading2">CRM</span></h2>
<p class="p_Normal">TEAM-25985 Added the ability to hide Kanban statuses in the sales pipeline depending on the user's role. Now it is possible to:</p>
<ul style="list-style-type:disc">
<li class="p_Normal">designate statuses visible only to managers, for example, for distributing tasks among performers.</li><li class="p_Normal">manage several types of sales within the same pipeine with both common and individual statuses. This allows all users to see a fully populated Kanban board without gaps, enhancing visual perception and ease of use.</li></ul>
<p class="p_Normal">&nbsp;</p>
<h2 class="p_Heading2"><span class="f_Heading2">Scripts</span></h2>
<p class="p_Normal">TEAM-12807 The error handling of the <code><b>getWorkingTime()</b></code> method has been improved. Now, if parameters are passed to the method where <code><b>from</b></code> is later than <code><b>to</b></code>, the script does not crash with an error. Instead, the difference between the dates is calculated regardless of the order. If <code><b>from</b></code> is greater than <code><b>to</b></code>, the method correctly returns the difference from the greater to the lesser.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">TEAM-16205 The script editor has added the <code><b>Blob</b></code> interface and the <code><b>blob()</b></code> method.</p>
<ul style="list-style-type:disc">
<li class="p_Normal">The Blob interface is a universal wrapper for the standard type <a href="https://developer.mozilla.org/ru/docs/Web/API/Blob" target="_blank" class="weblink">https://developer.mozilla.org/ru/docs/Web/API/Blob</a> on both client and server;</li><li class="p_Normal">The <code><b>blob()</b></code> method in <code><b>FetchResponse</b></code> for obtaining a response in the form of binary data.</li></ul>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">TEAM-26574 The <code><b>OrgunitField</b></code> in the <code><b>Permission</b></code> structure no longer has to be present in the <code><b>json item</b></code>. This avoids SQL query errors when the field is absent in the <code><b>json</b></code>.</p>
<p class="p_Normal">For example, previously, when adding access fields to process instances such as <code><b>"__createdBy", "__currentPerformers", "__subscribers"</b></code>, and the new field <code><b>"__viewers"</b></code> (with the <code><b>"omitempty"</b></code> flag), the system required all these fields to be present. Now, fields that may not be in each instance do not cause a query error.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">TEAM-27334 Added the <code><b>body</b></code> field in the <code><b>fetch</b></code> request response that contains the result stream of the request.</p>
<p class="p_Normal">Example of stream handling:</p>
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">async&nbsp;function&nbsp;test()&nbsp;{</span><br />
<span class="f_CodeExample" style="color: #ffffff;">&nbsp;&nbsp;&nbsp;&nbsp;</span><span class="f_CodeExample" style="font-weight: bold;">const&nbsp;</span><span class="f_CodeExample">res&nbsp;=&nbsp;await&nbsp;fetch(&quot;http://my-api.com/list&quot;);</span><br />
<span class="f_CodeExample" style="color: #ffffff;">&nbsp;&nbsp;&nbsp;&nbsp;</span><span class="f_CodeExample" style="font-weight: bold;">const&nbsp;</span><span class="f_CodeExample">reader&nbsp;=&nbsp;res.body.getReader();</span><br />
<span class="f_CodeExample" style="color: #ffffff;">&nbsp;&nbsp;&nbsp;&nbsp;</span><span class="f_CodeExample">Context.data.debug&nbsp;=&nbsp;'';</span><br />
<span class="f_CodeExample">&nbsp;</span><br />
<span class="f_CodeExample" style="color: #ffffff;">&nbsp;&nbsp;&nbsp;&nbsp;</span><span class="f_CodeExample" style="font-style: italic;">//&nbsp;Read&nbsp;the&nbsp;stream</span><br />
<span class="f_CodeExample" style="color: #ffffff;">&nbsp;&nbsp;&nbsp;&nbsp;</span><span class="f_CodeExample" style="font-weight: bold;">while&nbsp;</span><span class="f_CodeExample">(</span><span class="f_CodeExample" style="font-weight: bold;">true</span><span class="f_CodeExample">)&nbsp;{</span><br />
<span class="f_CodeExample" style="color: #ffffff;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span class="f_CodeExample" style="font-weight: bold;">const&nbsp;</span><span class="f_CodeExample">{&nbsp;done,&nbsp;value&nbsp;}&nbsp;=&nbsp;await&nbsp;reader.read();</span><br />
<span class="f_CodeExample">&nbsp;</span><br />
<span class="f_CodeExample" style="color: #ffffff;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span class="f_CodeExample" style="font-weight: bold;">if&nbsp;</span><span class="f_CodeExample">(done)&nbsp;{</span><br />
<span class="f_CodeExample" style="color: #ffffff;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span class="f_CodeExample" style="font-weight: bold;">break</span><span class="f_CodeExample">;</span><br />
<span class="f_CodeExample" style="color: #ffffff;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span class="f_CodeExample">}</span><br />
<span class="f_CodeExample" style="color: #ffffff;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span class="f_CodeExample">Context.data.debug&nbsp;+=&nbsp;value</span><br />
<span class="f_CodeExample" style="color: #ffffff;">&nbsp;&nbsp;&nbsp;&nbsp;</span><span class="f_CodeExample">}</span><br />
<span class="f_CodeExample">}</span></p>
<p class="p_Normal">The new field is available in both client and server scripts.</p>
<p class="p_Normal">&nbsp;</p>
<h2 class="p_Heading2"><span class="f_Heading2">Mobile app</span></h2>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">TEAM-3204 Added the ability to share files from mobile devices to the BRIX mobile app, starting with version 1.4.8. Users can now send files from messengers such as Telegram directly into the BRIX app.</p>
<p class="p_Normal">&nbsp;</p>
<h2 class="p_Heading2"><span class="f_Heading2">Widgets</span></h2>
<p class="p_Normal">TEAM-24615 In the widget builder settings, you can now configure how to display the widget when it is added to the template of another widget. The following display modes are available:</p>
<ul style="list-style-type:disc">
<li class="p_Normal">fully (default);</li><li class="p_Normal">fully, but without calling the initialization function;</li><li class="p_Normal">display only the title;</li><li class="p_Normal">a separate widget for the builder mode.</li></ul>
<p class="p_Normal">This feature is useful for reusable widgets, especially those distributed in BRIX Store solutions. Developers can now more flexibly manage widget display in builder mode, avoiding rendering and initialization issues.</p>
<p class="p_Normal">&nbsp;</p>
<h2 class="p_Heading2"><span class="f_Heading2">EQL</span></h2>
<p class="p_Normal">TEAM-26240 In the EQL control, it is now possible to set parameters using the &quot;@&quot; symbol.</p>
<p class="p_Normal">Example: <code><b>[__createdBy]=@Author</b></code>. When setting such a query, additional fields for filtering appear. This feature can be useful for use in saved filters.</p>
<p class="p_Normal">&nbsp;</p>
<h2 class="p_Heading2"><span class="f_Heading2">Contracts</span></h2>
<p class="p_Normal">TEAM-18302 Improvements &nbsp;to <span style="font-weight: bold;">Contracts</span>:</p>
<ol style="list-style-type:decimal">
<li value="1" class="p_Normal">The title in the source settings window has been changed from <span style="font-weight: bold;">Contract Settings</span> to <span style="font-weight: bold;">Source Settings</span>.</li><li value="2" class="p_Normal">When all sources are deleted, the correct label <span style="font-weight: bold;">No sources for the contract</span> is displayed.</li><li value="3" class="p_Normal">If there is an incomplete mapping of source fields to the contract fields and the recovery form is closed, a confirmation window is displayed with a message about the incomplete mapping.</li><li value="4" class="p_Normal">Sources with incomplete field mapping are saved and displayed in source settings with an error.</li></ol>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">TEAM-27251 In the field mapping window of source and contract, to the titles of the <span style="font-weight: bold;">Contract</span> and <span style="font-weight: bold;">App</span> columns, the names of the contract and the app have been added respectively, separated by a dash.</p>
<p class="p_Normal">&nbsp;</p>
<h2 class="p_Heading2"><span class="f_Heading2">Projects</span></h2>
<p class="p_Normal">TEAM-24489 Now, when changing the responsible party in a project task, a notification is sent to the task activity stream.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">TEAM-27157 Added color indicators for unstarted processes in the Gantt chart.</p>
<p class="p_Normal">&nbsp;</p>
<h2 class="p_Heading2"><span class="f_Heading2">ECM</span></h2>
<p class="p_Normal">TEAM-25769 New access settings have been added to the hierarchical directory, allowing non-administrators to edit folders. It is now possible to separately configure rights for creating, viewing, and editing folders for specified employees.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">TEAM-25835 Added the ability to change the names of standard buttons in the signing activity. Works similarly to changing button names in the <span style="font-weight: bold;">Task</span> block in the process designer. If names are set for connectors in the diagram, they are used as button texts on the page. Otherwise, default values are used.</p>
<p class="p_Normal">&nbsp;</p>
<h2 class="p_Heading2"><span class="f_Heading2">Service</span></h2>
<p class="p_Normal">TEAM-26374 Changed system behavior when opening the <span style="font-weight: bold;">Live Chats</span> workspace. Now, when navigating to the workspace, the top app or page automatically opens.</p>
<p class="p_Normal">&nbsp;</p>
<h2 class="p_Heading2"><span class="f_Heading2">Users</span></h2>
<p class="p_Normal">TEAM-4548 Added the ability to view and clear occupied positions before sending invitations or saving changes.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">TEAM-6705 Implemented the ability to customize the menu for users, saving time searching for the needed workspace. The administrator enables the <span style="font-weight: bold;">Allow users to configure the menu</span> feature in <span style="font-weight: bold;">Administration &gt; Company Settings</span>. Users can customize their menu by clicking the wrench icon in the sidebar, changing the order of workspaces, and managing their visibility. The <span style="font-weight: bold;">Default</span> setting allows resetting individual settings and applying global administrator settings.</p>
<p class="p_Normal">Activation of the feature flag <code><b>enableCustomMenu</b></code> is required.</p>
<h2 class="p_Heading2"><span class="f_Heading2">&nbsp;</span></h2>
<h2 class="p_Heading2"><span class="f_Heading2">Data management</span></h2>
<p class="p_Normal">TEAM-20611 Implemented the ability to work with deleted context variables in apps, business processes, and widgets. Administrators can view, restore, or delete these variables using the <span style="font-weight: bold;">Show deleted variables</span> flag. This enhances data control and helps maintain data integrity, preventing errors due to incorrect deletion.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal"><span style="font-weight: bold;">Activity stream</span></p>
<p class="p_Normal">TEAM-27260 Pinned the tabs <span style="font-weight: bold;">Chats</span>, <span style="font-weight: bold;">Activity Stream</span>, <span style="font-weight: bold;">Favorites</span> in the <span style="font-weight: bold;">Messages</span> workspace, so they remain visible when scrolling through the list of chats or objects.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">TEAM-27263 The context menu item <span style="font-weight: bold;">Show in the activity stream list</span> has been renamed to <span style="font-weight: bold;">Show in object list</span> to more accurately reflect the action's purpose.</p>
<p class="p_Normal">&nbsp;</p>
<h2 class="p_Heading2"><span class="f_Heading2">Bugs fixed</span></h2>
<p class="p_Normal">1. TEAM-22473 Fixed the names of chart types in the <span style="font-weight: bold;">Chart</span> widget. Previously, the types <span style="font-weight: bold;">Advanced Pie</span> and <span style="font-weight: bold;">Multiple Pies</span> did not accurately reflect their actual appearance. They are now correctly labeled as <span style="font-weight: bold;">Advanced Doughnut</span> and <span style="font-weight: bold;">Multiple Doughnuts</span>, accurately reflecting their structure. <span style="font-weight: bold; color: #800000;">#BreakingChangeAlert</span></p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">2. TEAM-24382 Fixed action logging for tasks in the <span style="font-weight: bold;">Security Audit</span> widget. Previously, the creation, updating, and completion of tasks were not recorded. Now, all actions with tasks are correctly displayed in the widget, ensuring full transparency of operations. <span style="font-weight: bold; color: #800000;">#BreakingChangeAlert</span></p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">3. TEAM-27793 Fixed an error with transferring a temporary file in a process initiated via API. Previously, despite successful process execution, the <span style="font-weight: bold;">File</span> type variable appeared visually empty and displayed as &quot;00000000-0000-0000-0000-000000000000&quot; in the API. Now, files are correctly passed into the context of the launched process, ensuring their availability and use within the process. <span style="font-weight: bold; color: #800000;">#BreakingChangeAlert</span></p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">4. TEAM-27573 A bug was identified related to the <code><b>json()</b></code> method for new unsaved app items. If you used the undocumented <code><b>json()</b></code> method for app items in scripts, as shown below, note that the behavior for the <code><b>__createdBy</b></code> field has changed.</p>
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample" style="font-weight: bold;">const&nbsp;</span><span class="f_CodeExample">item&nbsp;=&nbsp;Namespace.app.my_app_1.create();</span><br />
<span class="f_CodeExample">Context.data.test&nbsp;=&nbsp;JSON.stringify((&lt;any&gt;item).json());</span></p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">Previously, an empty value in this field was an empty array [], but this is incorrect as the field is singular. Now the empty value will be null. <span style="font-weight: bold; color: #800000;">#BreakingChangeAlert</span></p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">5. TEAM-27358 When sending a large body in an API Method, its content will never be encoded in base64. This behavior was unstable and led to development issues. Now, when working with the body of a request in the API Method script, you can always treat it as the original request. <span style="font-weight: bold; color: #800000;">#BreakingChangeAlert</span></p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">6. TEAM-10053 Fixed an error in the app with incorrect display of nested properties on the process transition button. Previously, fields intended for editing nested properties were concatenated with a delimiter. Now, they are displayed correctly.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">7. TEAM-18105 Fixed an issue with displaying the name of a form after copying in processes. Previously, instead of the user-specified name, the form's identifier was displayed. Now the name correctly reflects the user's choice.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">8. TEAM-19258 Fixed a debugging issue in processes that prevented adding multiple items. Previously, when selecting an item with a long name, the input field expanded, hiding the magnifying glass icon and blocking the addition of more items. Now, the magnifying glass icon remains accessible, and users can add multiple items without restrictions.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">9. TEAM-23951 Fixed an issue in the <span style="font-weight: bold;">Tasks</span> workspace where, despite the <span style="font-weight: bold;">Not required</span> setting in the <span style="font-weight: bold;">Control</span> field, users received control tasks for subtasks.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">10. TEAM-24474 Fixed an error in the <code><b>changeDueDate</b></code> method, where the comment specified when changing the task completion date was not displayed in the process activity stream.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">11. TEAM-25013 Fixed an error in the <code><b>count()</b></code> method when using the<code><b>_searchInstances</b></code> function. Previously, the count() method incorrectly returned a number of process instances that differed from the actual count calculated through <code><b>.all().length</b></code>.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">12. TEAM-25258 Fixed an issue with transmitting values to a table from custom activities in business processes. Previously, when using activities in business processes, data was not correctly transmitted to tables despite the proper filling of the context and identical table fields.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">13. TEAM-26329 Fixed an issue with incorrect attribution of changes in items after using the <span style="font-weight: bold;">Edit app Item</span> activity in business processes. Now, the user is correctly displayed as the author of the changes, not the system.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">14. TEAM-26933 Previously, clicking the Help button on the process diagram would navigate on the current browser tab, now the help opens in a new tab.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">15. TEAM-27230 Fixed an issue that allowed setting the task completion deadline to a past date. Now, the <span style="font-weight: bold;">Complete by</span> field includes a restriction: it is not possible to select a date earlier than the current day.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">16. TEAM-27547 Fixed an error in report imports when data sources depend on other solutions. Previously, attempting to import reports without pre-installing dependent solutions resulted in a &quot;collections for datasources: not found&quot; error. Now, the system correctly handles dependencies between solutions, preventing such errors and ensuring successful report imports in any configuration.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">17. TEAM-27931 Fixed an error in exporting business process maps in PNG format. Previously, the shapes representing elements on the process map did not appear in the final image. Now, the export is performed correctly, and all elements are visualized as expected.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">18. TEAM-28131 Fixed an error that made deleted context variables accessible in business process reports. Now, when creating a report, it is not possible to select deleted context properties as columns, ensuring the accuracy and relevance of the displayed data.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">19. TEAM-28466 Fixed an error in reports when using a column aggregated by a Money type field, which led to failures when accessing data through scripts. Previously, attempts to use aggregated money data in scripts resulted in errors related to data format handling.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">20. TEAM-28469 Fixed an error in filtering report data in scripts. Previously, attempts to apply a filter to report data through a script resulted in internal errors, hindering the correct filling of the table.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">21. TEAM-28005 Fixed an issue where operators were receiving a missed call notification even if one of the operators had already answered the call. Now, if an operator picks up, other operators will not see a missed call notification.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">22. TEAM-24838 Added event handling for enabling/disabling a module.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">23. TEAM-26340 Previously, methods for obtaining a process template schema did not return the code and namespace of variables of the <span style="font-weight: bold;">App</span> type. Now the response includes additional schema data: <a href="https://api.brix.com/en/public-api/guides/FieldData/" target="_blank" class="weblink">https://api.brix.com/en/public-api/guides/FieldData/</a></p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">24. TEAM-26527 A bug was identified where after exporting and importing workspaces, the <code><b>Imports</b></code> dependencies in the widget stopped working if the workspace code was changed during import. This led to errors indicating the absence of a workspace with the required code. The problem has been resolved.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">25. TEAM-27560 A bug was identified related to passing links to app items in business process action methods via <code><b>Imports</b></code>. When passing an array of users as a parameter, a <code><b>TypeError</b></code> occurred, indicating an attempt to convert a cyclic structure to JSON. The problem has been fixed.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">26. TEAM-27999 A bug was identified and fixed that occurred when creating an external portal from a template. The error manifested as &quot;TypeError: Cannot read properties of undefined (reading 'portal')&quot; both during initialization and at runtime of the portal's main page designer.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">27. TEAM-20729 A bug related to the <span style="font-weight: bold;">Show on condition</span> setting for <span style="font-weight: bold;">Yes/No</span> <span style="font-weight: bold;">Switch</span> &nbsp;variables in widget builder was identified and fixed. When creating an app item and applying this setting, the <span style="font-weight: bold;">Yes/No</span> <span style="font-weight: bold;">Switch</span> variable was automatically set to <span style="font-weight: bold;">No</span>, which did not match the expected behavior. This led to the variable visually appearing as selected, although it remained empty in the app context.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">28. TEAM-26261 A bug was identified and fixed related to the display of <span style="font-weight: bold;">Input/Output</span> columns in the context of a widget after enabling options to display the widget in the header with buttons on forms or in the sidebar in the low-code widget builder. Upon reopening the widget on the context tab, the <span style="font-weight: bold;">Input/Output</span> columns were not displayed, and the options for displaying the widget in the header and sidebar appeared as disabled and inactive, not allowing any changes.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">29. TEAM-27514 A bug related to the display of restricted dates on <span style="font-weight: bold;">Date</span> fields was identified and fixed. Previously, restricted dates were not marked on the calendar, which could lead users to misunderstand which dates were available for selection.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">30. TEAM-27670 A bug related to widget settings in the builder was identified and fixed. The problem was that after creating and binding a system function on the <span style="font-weight: bold;">Settings</span> tab, saving changes did not retain the selected method after exiting and re-entering the builder.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">31. TEAM-27959 A bug related to ignoring validation errors when the flag<span style="font-weight: bold;"> Do not display widget with validation errors</span> was enabled has been fixed. If the form setting was enabled, the app item was saved even when validation errors were present.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">32. TEAM-25975 An error was identified when adding the library <code><b>tabulator.min.js</b></code> to the <span style="font-weight: bold;">Code</span> widget, where a problem occurred due to the incorrect MIME type (application/octet-stream), leading to an execution error due to the activated strict MIME type checking.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">33. TEAM-27372 An error was identified related to the incorrect update of the <span style="font-weight: bold;">File Preview</span> widget's content when changing the selected file. When selecting a new app item and clicking the file preview button, the widget displayed the previously selected file, not considering the new data. A redraw of the view widget has been implemented upon changes in the widget's input data.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">34. TEAM-27780 A problem was identified with excessive buttons on the page with a document packet after completing the approval process and their placement on the task form. Users noticed the presence of the <span style="font-weight: bold;">Form Settings</span> button, which should not be displayed on this page. An error occurs when attempting to click <span style="font-weight: bold;">Form Settings</span>.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">35. TEAM-27783 A problem with narrowing the version comparison window after refreshing the page in the <span style="font-weight: bold;">Document</span> type app was identified. The error has been fixed.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">36. TEAM-27979 In the application for creating a signature in the Kontur provider for identification by SMS, a request for operation confirmation has been added to Kontur. Now, the SMS code for confirmation, which can be transmitted to the Kontur using tssdk, will be sent to the number specified in the <span style="font-weight: bold;">Advanced non-qualified e-signature request</span> block. </p>
<p class="p_Normal">&nbsp;</p>
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">```javascript</span><br />
<span class="f_CodeExample" style="font-weight: bold;">const&nbsp;</span><span class="f_CodeExample">result&nbsp;=&nbsp;await&nbsp;signRequest.confirm(smsCode);</span><br />
<span class="f_CodeExample">```</span><br />
<span class="f_CodeExample">where:</span><br />
<span class="f_CodeExample">-&nbsp;`smsCode`&nbsp;-&nbsp;SMS&nbsp;code&nbsp;as</span><span class="f_CodeExample" style="font-weight: bold;">&nbsp;string</span><br />
<span class="f_CodeExample">-&nbsp;`signRequest`&nbsp;-&nbsp;request&nbsp;</span><span class="f_CodeExample" style="font-weight: bold;">for&nbsp;</span><span class="f_CodeExample">issuing&nbsp;the&nbsp;signature</span></p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">After which the signature can be issued.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">37. TEAM-28071 A bug was identified and fixed in the <span style="font-weight: bold;">Approval</span> block related to changing the type of swimlane from dynamic to static during process setup. The error appeared after a user modified the settings of the second swimlane and selected a user group.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">38. TEAM-28145 The display of the <span style="font-weight: bold;">Sign</span> button on the user form has been corrected after it was removed in the designer and re-added.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">39. TEAM-28354 File deletion handling has been added to the system file viewer widget linked to the widget's field.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">40. TEAM-23251 The <span style="font-weight: bold;">Plan archive</span> field has been hidden from the user interface as it has been removed from the business logic of the workspace.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">41. TEAM-24435 If the <span style="font-weight: bold;">End date</span> falls on a non-working day, the date is adjusted to the next working day inclusive. This behavior is consistent for both drag-and-drop and inline editing. The duration of the task in days is kept according to the working days within the range. This check only works in the Gantt chart widget; it is not present on the task creation and editing forms.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">42. TEAM-26275 The milestone is considered in the overall progress of a stage task. If the milestone is not closed, the stage task will not be completed.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">43. TEAM-26344 Previously, notifications about the completion of project tasks were not sent to the manager. This error has been corrected.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">44. TEAM-26405 The <span style="font-weight: bold;">Project tasks</span> widget now functions correctly, filter values are applied to the widget and are saved; upon reopening the project view form, the saved filter is applied.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">45. TEAM-27725 Errors in solution import on various platform versions have been corrected.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">46. TEAM-27905 Errors in displaying individual interface elements in the Gantt chart have been corrected.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">47. TEAM-27947 A bug was identified and fixed related to missing fields in electronic signature details. Users encountered issues where fields such as <code><b>certSerialNumber</b></code>, <code><b>commonName</b></code>, and <code><b>organization</b></code> were not displayed correctly.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">48. TEAM-28497 An error related to the execution of linked tasks in the <span style="font-weight: bold;">Projects</span> system workspace was identified and fixed. The error occurred after setting end-to-start task dependencies and then trying to complete one of the linked tasks. When the <span style="font-weight: bold;">Done</span> button was pressed on the task form, an error notification appeared, although the task was marked as completed.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">49. TEAM-28798 An issue with increased load on MongoDB due to frequent queries to the <code><b>feature_flags</b></code> collection in the <code><b>elma365commerceVahter</b></code> database was identified. These queries, performed every 15 minutes, led to significant CPU load, impacting overall system performance. The error has been resolved.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">50. TEAM-28807 An error was identified and corrected during the retrieval of signature data from an external e-signature provider. The problem occurred when calling the <code><b>getDetails</b></code> method for the signed item <code><b>internalCorrespondence</b></code>, despite the item being correctly signed.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">51. TEAM-25233 An issue with missing notifications about the creation of events in the calendar was identified and corrected. Sometimes event participants did not receive notifications.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">52. TEAM-25388 An error causing duplication of business process instances upon multiple click on the <span style="font-weight: bold;">Start Process</span> button was identified and eliminated. This issue was evident when using the process start form, which reopened with each button press, allowing the same process to be launched multiple times without proper control. To resolve this issue, the start button is now locked until the previous start request is completed and a notification of successful process start appears.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">53. TEAM-26333 An error related to the incorrect saving of items in dependent apps was resolved. When attempting to create an item in one app through another app's form, the dependent item was saved even if the main item failed. Now, if the main item is not saved, the related items will also not be created, ensuring compliance with the logic of dependent fields and improving system stability.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">54. TEAM-26867 An error related to the incorrect setting of access rights when creating new companies for the <span style="font-weight: bold;">Projects</span> app was corrected. The issue occurred during data migration, where access rights were not properly applied. Now, access rights are correctly set, and access to app items is restricted according to settings, ensuring proper access control and data protection.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">55. TEAM-27162 An error was identified and corrected where messages from muted channels were not displayed in <span style="font-weight: bold;">Favorites</span>.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">56. TEAM-27323 An issue was identified and corrected where the module icon was not displayed after importing a solution. The problem manifested as follows: after importing the solution and navigating to the module administration workspace, the module icon was replaced with a placeholder. To resolve the issue in existing Store solutions using .svg icons, it is necessary to manually re-upload the icon, re-export the module, or specify the icon format through editing the package using <code><b>elma365pm</b></code>.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">57. TEAM-27733 A problem with synchronizing group members from AD was identified when dealing with a large number of users and groups. When attempting to synchronize with an OU containing over 10,000 users and a large number of groups with more than 2,000 members, the list of group members remained empty, despite logs indicating successful synchronization. This issue has been resolved.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">58. TEAM-27949 A bug was detected where an app with a button on the form that launches a process from another app could be exported without errors, despite warnings. This issue has been corrected.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">59. TEAM-28018 An error was identified and corrected where email sending for password change and recovery was not working when a periodic password change policy was active. The problem led to users not receiving password change notifications and being unable to reset their password through the &quot;forgot password&quot; function, causing errors. Now, emails are sent correctly.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">60. TEAM-28136 A bug was identified and corrected that caused the &quot;get page: not found&quot; error during configuration import. The issue occurred during the application import stage if the configuration contained a removed workspace.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">61. TEAM-28308 A bug was identified and corrected related to the lack of access to a new page for users and incorrect determination of the executor after updating the workspace or solution. The problem occurred when adding a new page and an access group in the workspace, then updating the workspace in another instance of the system. Users added to the group after the update did not have access to the new page, and re-saving access settings did not help. The error has now been corrected.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">62. TEAM-28552 An error was identified and corrected where solution updates were failing with the &quot;forbidden without check&quot; error. The problem occurred when attempting to update the solution after its initial import, where the first import status request led to an error. Following the correction, solution updates now proceed successfully without the error.</p>
<p class="p_Normal">&nbsp;</p>
<div class="bottom-nav">
<a id="prev-link" class="topic__navi_prev" href="2024_7.html">
<span class="bottom-nav__arrow bottom-nav__arrow--prev"></span> <span
class="bottom-nav__link">2024_7.html</span>
</a>
<a id="next-link" class="topic__navi_next" href="2024_5.html">
<span class="bottom-nav__link">2024_5.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">&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>