levis/help365
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
production
help365/platform/2025_3.html
koziavin 00717a92fb
All checks were successful
Deploy Static Site / deploy (push) Successful in 6m6s
Details
update
2025-05-29 16:42:45 +04:00

262 lines
39 KiB
HTML
Raw Permalink Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

<!DOCTYPE html>
<html lang="en">
<head>
<title>2025.3</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 trial 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 &gt; BRIX SaaS / 2025.3</p>
</div>
</div>
<div class="topic__title"><h1 class="p_Heading1"><span class="f_Heading1">2025.3</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">Here is the list of changes that you can explore right now by activating the BRIX trial version.</p>
<p class="p_Normal">After April 15, 2025, all changes will become available to our clients in their active companies. Please note, the list may grow after the release.</p>
<p class="p_Normal">Please pay special attention to any updates with the <span style="color: #ff0000;">#BreakingChangeAlert</span> tag. They might require you to take extra steps to adapt or adjust your current configuration.</p>
<h2 class="p_Heading2"><span class="f_Heading2">Server scripts tracing</span></h2>
<ol style="list-style-type:decimal">
<li value="1" class="p_Normal">TEAM-33039 Improved the search in the recorded trace page. You can now search:</li></ol>
<ul style="list-style-type:disc">
<li class="p_Normal">By name of the spans that make up the trace.</li><li class="p_Normal">By names of attributes and events.</li></ul>
<p class="p_Normal" style="margin: 0 0 0 30px;">Matches are highlighted in yellow on the page. Also added navigation — you can quickly switch from one found record to another.</p>
<ol style="list-style-type:decimal" start="2">
<li value="2" class="p_Normal">TEAM-34471 In the module settings on the <span style="font-weight: bold;">Event Handling</span> tab, you can now view the total list of traces recorded by all enabled event handlers in the module. Previously, you could access the traces of a certain handler only on its page.</li><li value="3" class="p_Normal">TEAM-33328 In the module settings on the <span style="font-weight: bold;">API Methods</span> tab, you can now view the total list of traces recorded by all API methods created in the module. Previously, you could access traces of a certain method only on its page.</li></ol>
<h2 class="p_Heading2"><span class="f_Heading2">Business and work calendar</span></h2>
<p class="p_Normal">TEAM-33499 In <span style="font-weight: bold;">Administration &gt; Business Calendar</span>, you can now export a customized calendar, as well as download a calendar from another system in <span style="font-weight: bold;">.zip</span> or <span style="font-weight: bold;">.csv</span> format.</p>
<h2 class="p_Heading2"><span class="f_Heading2">Business processes</span></h2>
<ol style="list-style-type:decimal">
<li value="1" class="p_Normal">TEAM-3206 In <span style="font-weight: bold;">Administration &gt; Process Monitor</span> on the process page, you can now select several running instances and interrupt them.</li><li value="2" class="p_Normal">TEAM-8091 In the process instance page, the <span style="font-weight: bold;">History</span> tab now displays information about the execution of each activity on the process flow chart. You can see the executor, the date and time the activity was started, and its duration.</li><li value="3" class="p_Normal">TEAM-33962 When publishing a process, the performance indicators used in the process flow chart are checked. If an indicator is not published or created in a disabled module, users will see an error.</li></ol>
<h2 class="p_Heading2"><span class="f_Heading2">Modules</span></h2>
<p class="p_Normal">TEAM-30821 In the module settings on the <span style="font-weight: bold;">Business Process Activities</span> tab, the list of records now displays the unique code of the activity specified when it was created.</p>
<h2 class="p_Heading2"><span class="f_Heading2">Widgets</span></h2>
<p class="p_Normal">TEAM-18509 In the <span style="font-weight: bold;">Code</span> widget, you can open the settings window in full-screen mode for easy scripting.</p>
<h2 class="p_Heading2"><span class="f_Heading2">Apps</span></h2>
<ol style="list-style-type:decimal">
<li value="1" class="p_Normal">TEAM-24002 Improved editing of app items. Now when saving a form, only the changed fields are updated, not the entire item. This improvement prevents situations where field values could be swapped and not saved during concurrent editing of an item.<br />
&nbsp;<br />
In addition, a bulk editing form for app items now includes options for each field:</li></ol>
<ul style="list-style-type:disc">
<li class="p_Normal"><span style="font-weight: bold;">Leave unchanged</span>. Select to skip editing the current value in the field on item forms.</li><li class="p_Normal"><span style="font-weight: bold;">Clear</span>. Select to remove the value from the field and leave it blank on the form.</li></ul>
<ol style="list-style-type:decimal" start="2">
<li value="2" class="p_Normal">TEAM-10181 To display items in the form of tiles and Kanban board on the app page, the following components support line breaks: item names and fields of the <span style="font-weight: bold;">Status</span>, <span style="font-weight: bold;">Category</span>, <span style="font-weight: bold;">Email</span>, <span style="font-weight: bold;">Account</span>, and <span style="font-weight: bold;">Full name</span> types. Now in these modes, users will immediately see item names and field values.</li></ol>
<h2 class="p_Heading2"><span class="f_Heading2">Item search</span></h2>
<ol style="list-style-type:decimal">
<li value="1" class="p_Normal">TEAM-33768 In the search-by-parameter window on the app page, you can now specify several items in the field of the <span style="font-weight: bold;">Users (one, many)</span> type.</li><li value="2" class="p_Normal">TEAM-34535 In the BRIX mobile application, added a button for canceling a request and exiting the search mode. It is available in the window for searching app items by parameters.</li></ol>
<h2 class="p_Heading2"><span class="f_Heading2">Substituting users</span></h2>
<ol style="list-style-type:decimal">
<li value="1" class="p_Normal">TEAM-20200 Added a feature to create substitution rules for users. Now you can specify multiple substitutes and customize the conditions under which tasks will be distributed among them. This provides flexibility in managing tasks during the absence of employees. To make the feature available, enable the <code><b>front_enable_substitution_rules</b></code> feature flag.</li></ol>
<p class="p_Normal" style="margin: 0 0 0 31px;">Main operating principles:</p>
<ul style="list-style-type:disc">
<li class="p_Normal">An unlimited number of task allocation rules can be created for a single substitution.</li><li class="p_Normal">A rule is assigned to a certain absent employee.</li><li class="p_Normal">If a task does not match any of the rules, it is assigned to the specified substitute.</li><li class="p_Normal">Rules can be edited or deleted if they are not used in active substitution.</li><li class="p_Normal">If the conditions of several rules overlap, you can set the priority of selection.</li><li class="p_Normal">When reassigning a task manually, the substitution rules are not taken into account.</li><li class="p_Normal">In cyclic substitution setup, current tasks remain with the original executor and new tasks are reassigned through the chain of substitutions.<br />
&nbsp;<br />
To create a rule:</li></ul>
<ol style="list-style-type:upper-roman">
<li value="1" class="p_Normal">Create a substitution and fill in the required fields.</li><li value="2" class="p_Normal">In the <span style="font-weight: bold;">Rules</span> field, click <span style="font-weight: bold;">Create</span>.</li><li value="3" class="p_Normal">In the window that opens, specify:</li></ol>
<ul style="list-style-type:disc">
<li class="p_Normal">Rule name.</li><li class="p_Normal">Conditions to filter the tasks.</li><li class="p_Normal">User to whom the tasks will be reassigned.</li></ul>
<ol style="list-style-type:upper-roman" start="4">
<li value="4" class="p_Normal">Save the rule.</li></ol>
<ol style="list-style-type:decimal" start="2">
<li value="2" class="p_Normal">TEAM-31168 Improved the assignment of tasks to an employee for whom a substitute has been created. Now, if a substitute employee creates a task and specifies an absent user as the executor, the task is not reassigned, but remains assigned to the absent user.</li></ol>
<h2 class="p_Heading2"><span class="f_Heading2">Document management</span></h2>
<p class="p_Normal">TEAM-31041 You can now upload an <span style="font-weight: bold;">.rtf</span> file as a document template and use it in a business process in the <span style="font-weight: bold;">Generate from Template</span> activity.</p>
<h2 class="p_Heading2"><span class="f_Heading2">Projects</span></h2>
<p class="p_Normal">TEAM-34190 Accelerated the loading of the project task view form. Optimized loading window display.</p>
<h2 class="p_Heading2"><span class="f_Heading2">Service</span></h2>
<ol style="list-style-type:decimal">
<li value="1" class="p_Normal">TEAM-28887 Added a feature on the session page to attach to the message files that are uploaded to session-related app items in fields of the <span style="font-weight: bold;">Files</span> type. For example, you can forward a file from a call to a client, and you do not need to download it to a computer beforehand. The operator can now select files:</li></ol>
<ul style="list-style-type:disc">
<li class="p_Normal">From a local computer or smart phone.</li><li class="p_Normal">From the <span style="font-weight: bold;">Files</span> workspace.</li><li class="p_Normal">From linked items of the app.</li></ul>
<ol style="list-style-type:decimal" start="2">
<li value="2" class="p_Normal">TEAM-34242 On the session page with an external user who contacted via email, the client data is now displayed better. If there are multiple recipients, one of them is marked as the primary client. This is either the first user who contacted a live chat or the user the operator started the session with.</li></ol>
<h2 class="p_Heading2"><span class="f_Heading2">Telephony</span></h2>
<p class="p_Normal">TEAM-31626 Added the <span style="font-weight: bold;">Telephony</span> workspace to accumulate and store data on incoming and outgoing calls. For each recorded call, an item of the <span style="font-weight: bold;">Calls</span> app is created, where the data is stored.</p>
<p class="p_Normal">A <span style="font-weight: bold;">Call Log</span> widget is added. It allows you to display calls on a separate page and on viewing forms of other apps of the system. In the widget, you can customize the columns of the table with records, filters for searching, as well as the criteria for selecting items for displaying. For example, you can show only calls of the current user, incoming or outgoing, etc. When you open a call page, you can view the call data and see the contact of the call, the user who received or made the call, the start and end date of the call, its duration, listen to the call recording, etc.</p>
<p class="p_Normal">In the <span style="font-weight: bold;">Administration</span> workspace, you can customize the appearance of incoming, outgoing, and missed call pages separately. You can also choose which user action buttons to display: hang up, reassign call, put on hold, create CRM task, event, or note, etc.</p>
<p class="p_Normal">In addition, you can create a custom call summary page. It can be filled with widgets and opened automatically, for example, when a call comes in, or by a button in the call page.</p>
<p class="p_Normal"><span style="font-weight: bold;">Telephony</span> workspace, <span style="font-weight: bold;">Call Log</span> widget, and call settings in <span style="font-weight: bold;">Administration &gt; Telephony</span> are available if <span style="font-weight: bold;">BRIX Communication Management</span> license is enabled, as well as those licenses where communication management functionality is enabled (<span style="font-weight: bold;">BRIX Sales Management</span>, <span style="font-weight: bold;">BRIX CX</span>, and outdated <span style="font-weight: bold;">BRIX CRM</span>).</p>
<h2 class="p_Heading2"><span class="f_Heading2">TS SDK and API</span></h2>
<ol style="list-style-type:decimal">
<li value="1" class="p_Normal">TEAM-33701 When using the Web API method to create a folder in a document categorization (<code><b>POST /pub/v1/nomenclature</b></code>), added a check for the existence of the document registry to which the folder is created. <span style="color: #ff0000;">#BreakingChangeAlert</span></li></ol>
<ol style="list-style-type:decimal" start="2">
<li value="2" class="p_Normal">TEAM-34088 Improved the <code><b>manualRegister</b></code> method. Now manual registration of documents using this method is prohibited if automatic registration is set up in the folder. In scripts where the method is used, an error will be displayed under such conditions. <span style="color: #ff0000;">#BreakingChangeAlert</span></li><li value="3" class="p_Normal">Added a feature to create instances of objects of the <code><b>Role</b></code> type using methods:</li></ol>
<ul style="list-style-type:disc">
<li class="p_Normal"><code><b>create(type: RoleType, code: string)</b></code>. Initializes a role by type and code.</li><li class="p_Normal"><code><b>createByItemRef (item: UserGroupItemRef | UserItemRef | OrganisationStructureItemRef)</b></code>. Initializes a role by reference object.</li></ul>
<ol style="list-style-type:decimal" start="4">
<li value="4" class="p_Normal">The <span style="font-weight: bold;">Node.js</span> version for server scripts execution has been updated to v.20.</li></ol>
<h2 class="p_Heading2"><span class="f_Heading2">Bugs fixed</span></h2>
<ol style="list-style-type:decimal">
<li value="1" class="p_Normal">TEAM-32713 If a non-existent method in <code><b>Server.rpc</b></code> was used in the widget script, the widget was published and then an error occurred. Now when publishing, a script is checked for validity.</li><li value="2" class="p_Normal">TEAM-33600 When working in scripts with <code><b>FormData</b></code>, <code><b>.has()</b></code> and <code><b>.getAll()</b></code> methods could not be processed if the request was sent from JS code. The bug has been fixed — the methods work correctly.</li><li value="3" class="p_Normal">TEAM-34265 Improved the user creation form in <span style="font-weight: bold;">Administration &gt; Users</span>. Removed uninformative warning about work schedule changes.</li><li value="4" class="p_Normal">TEAM-34484 If the <code><b>Imports</b></code> constant was used in a script with an API method, errors were incorrectly detected when checking it even if no errors were displayed when publishing the method. The behavior has been fixed — the validation is performed correctly.</li><li value="5" class="p_Normal">TEAM-34555 When deleting a workspace that is used as an optional dependency (<code><b>Imports</b></code>) in a script created at the module level, “TypeError: Cannot read properties of null (reading ‘find’)” occurred. This caused the settings modal window to freeze. The bug has been fixed.</li><li value="6" class="p_Normal">TEAM-34564 The values of fields of the <span style="font-weight: bold;">String (markdown)</span> and <span style="font-weight: bold;">String (string)</span> types were displayed incorrectly. The bug has been fixed. The <span style="font-weight: bold;">String (markdown)</span> field allows you to enter a value in multiple lines, while <span style="font-weight: bold;">String (string) </span>is a single-line field.</li><li value="7" class="p_Normal">TEAM-31708 If a mandatory widget field was switched to <span style="font-weight: bold;">Read-only</span> mode, the mandatory field requirement failed to reactivate. The asterisk icon next to the field was missing. The bug has been fixed.</li><li value="8" class="p_Normal">TEAM-33127 When expanding the <span style="font-weight: bold;">Panel with Header</span> widget on the app view form, the window scrollbar appeared and disappeared. The widget display has been fixed.</li><li value="9" class="p_Normal">TEAM-34042 Fixed the styles of the <span style="font-weight: bold;">Live Chat Messages</span> widget. Improved widget displaying next to other components on the item view form in BRIX mobile application.</li><li value="10" class="p_Normal">TEAM-33694 Improved the system processes of approving and sending documents for information:</li></ol>
<ul style="list-style-type:disc">
<li class="p_Normal">Corrected text in the process start button on the start form.</li><li class="p_Normal">Added validation to the <span style="font-weight: bold;">Approval due date</span> field. It is now impossible to specify a past date.</li><li class="p_Normal">Eliminated the “Error: 5” window popping up when sending a document for information.</li></ul>
<ol style="list-style-type:decimal" start="11">
<li value="11" class="p_Normal">TEAM-34137 Removed the duplicate <span style="font-weight: bold;">Add Version</span> button on the file view page in the <span style="font-weight: bold;">Files</span> workspace. You can now upload a new version by clicking the plus icon.</li><li value="12" class="p_Normal">TEAM-24165 Improved editing of the project plan. The main way to change the plan is now in edit mode from the project view form. Items from other apps open correctly in edit mode. Previously, the project view form was displayed when trying to open an item.</li><li value="13" class="p_Normal">TEAM-27950 Fixed display of tasks in the <span style="font-weight: bold;">My Project Tasks</span> widget. Tasks are now displayed for users according to the configured access rights in the <span style="font-weight: bold;">Project tasks</span> app.</li><li value="14" class="p_Normal">TEAM-28588 When accessing approval sheets in scripts, the “DocflowListType is not defined” error was returned. Now the script is executed correctly.</li><li value="15" class="p_Normal">TEAM-29206 Made improvements: if access to an app is edited, access rights are not changed or inherited for the folder tree included in it.</li><li value="16" class="p_Normal">TEAM-30365 Fixed display of a folder tree on the form of another app. Now the list of records from the required folder is correctly displayed in the window of selecting an item from a field of the <span style="font-weight: bold;">App</span> type.</li><li value="17" class="p_Normal">TEAM-31826 Optimized the page with the result of searching for items by parameters in apps for which the folder tree is enabled.</li><li value="18" class="p_Normal">TEAM-33425 In the <span style="font-weight: bold;">Files</span> workspace, errors 503 and 504 occurred when deleting a large number of files from the trash. The errors have been fixed.</li><li value="19" class="p_Normal">TEAM-33525 In the <span style="font-weight: bold;">Files</span> workspace, the “Cannot read properties of null (reading ‘isFile’)” error occurred when moving several files using the Drag-and-Drop method. The error has been fixed.</li><li value="20" class="p_Normal">TEAM-33829 When uploading a file with a long name to an app form of the <span style="font-weight: bold;">Document</span> type, the buttons on the top panel were displayed incorrectly in the <span style="font-weight: bold;">Upload and Preview File</span> widget. The widget panel layout has been fixed.</li><li value="21" class="p_Normal">TEAM-33947 When opening a file after review or approval, the sidebar with properties was not displayed on the view page. The panel display has been fixed.</li><li value="22" class="p_Normal">TEAM-34011 Fixed the <code><b>hasPermission</b></code> and <code><b>getPermissions</b></code> functions for files. They now return permissions taking inheritance into account.</li><li value="23" class="p_Normal">TEAM-34361 User avatar thumbnails were displayed incorrectly if a non-square image was used. The bug has been fixed.</li><li value="24" class="p_Normal">TEAM-34423 The <span style="font-weight: bold;">Project Tasks</span> filter was not applied in the <span style="font-weight: bold;">Tasks</span> workspace. The records were displayed only after the page reloaded. The bug has been fixed.</li><li value="25" class="p_Normal">TEAM-34800 In the <span style="font-weight: bold;">Signatures Archive</span> widget, links to download a signature file looked like regular records. The display of links in the widget has been fixed.</li><li value="26" class="p_Normal">TEAM-34937 If a project file folder was deleted in the <span style="font-weight: bold;">Files</span> workspace, users could not upload documents in the project page. Now, if the project folder is deleted, it is automatically created in the <span style="font-weight: bold;">Files</span> workspace when the employee opens the project. Documents attachment works correctly.</li><li value="27" class="p_Normal">TEAM-33965 If you change the name of a published business process performance indicator and then cancel its publication, its name was not updated in the general list of indicators. Now the name is displayed correctly.</li><li value="28" class="p_Normal">TEAM-13226 Added validation to the solution export process: if an activity created at the module level is used in a business process and this module is not included in the solution, the user will see an error with a detailed description of the problem.</li><li value="29" class="p_Normal">TEAM-17188 Table column values were not passed from a child process to a parent process when variables were correctly mapped. The bug has been fixed.</li><li value="30" class="p_Normal">TEAM-19400 When publishing a business process, added check for used functions in the <span style="font-weight: bold;">Script</span> activity. Previously, if a function was deleted, the process was published without errors. Now users will not be able to publish the process.</li><li value="31" class="p_Normal">TEAM-21482 When debugging a business process, the <span style="font-weight: bold;">Scripts</span> tab did not display errors found in the compiled scripts. Now all errors are displayed correctly.</li><li value="32" class="p_Normal">TEAM-22542 An error was found when exporting a solution because of the absence of a certain group in the business process swimlane. The bug has been corrected.</li><li value="33" class="p_Normal">TEAM-31225 An error was found: if a variable was created in a business process with the same code as a variable previously removed from context, the process was not published. The bug has been fixed.<br />
&nbsp;<br />
Please note, starting with version <span style="font-weight: bold;">2025.3</span>, context variables can be completely deleted via the web interface <span style="font-weight: bold;">only before the business process is published</span>. If the process version is published, assign unique codes to the variables when creating new variables.</li><li value="34" class="p_Normal">TEAM-31582 If during a business process, an app item on which the process is running was deleted using the <code><b>delete()</b></code> method in a script, the process execution was interrupted at that step. The bug has been fixed.</li><li value="35" class="p_Normal">TEAM-34031 Fixed the Email notification text about a new task. Users will now see a notification saying “You’ve been assigned a new task”.</li><li value="36" class="p_Normal">TEAM-34234 The customized business process start event form was not migrating to another company when exporting a process as part of a solution. The bug has been fixed.</li><li value="37" class="p_Normal">TEAM-34303 If a <span style="font-weight: bold;">Chart</span> widget is created with a data source of the <span style="font-weight: bold;">Report</span> type and specifying a measurement by app statuses, the page did not display the result and a 404 error was displayed in the log. The bug has been fixed.</li><li value="38" class="p_Normal">TEAM-34620 The API method to retrieve a list of process instances (<code><b>GET /pub/v1/bpm/instance/bytemplateid/{id}/list</b></code>) was not executed, and an error was displayed in the request response. The behavior has been fixed. If the query is incorrect, the user will see a detailed error.</li><li value="39" class="p_Normal">TEAM-16957 Found a bug: more than one user could be added to a group of the <span style="font-weight: bold;">Role</span> type if you specify the role in the user page. The bug has been fixed.</li><li value="40" class="p_Normal">TEAM-18975 Fixed generation of the code that is assigned to an app status when it is created. Previously, spaces were replaced with dashes, which prevented the status from being referenced in scripts.</li><li value="41" class="p_Normal">TEAM-20407 The component import process now checks whether a page, workspace, or app is locked. Previously, components could be imported but remained inaccessible due to locking. Now the user will see a user-friendly error message in the import process.</li><li value="42" class="p_Normal">TEAM-22916 Now when creating a solution, a separate field shows the generated solution code and the user can edit it.</li><li value="43" class="p_Normal">TEAM-28713 When the status of an app item was changed during a business process using a script or activity, its page did not display the new status. The bug has been fixed.</li><li value="44" class="p_Normal">TEAM-28824 Fixed the layout in the access restriction notification window. Added proper spacing to the list of users who can grant access.</li><li value="45" class="p_Normal">TEAM-29144 Fixed the display of the cross icon in the search bar at the top of the page. Previously, the icon was displayed even when the row was empty.</li><li value="46" class="p_Normal">TEAM-31841 The <span style="font-weight: bold;">Allow bulk editing</span> option could not be activated in the app form settings. The user checked the option, followed the steps for bulk editing, but the changes were not applied to the selected items. The bug has been fixed.</li><li value="47" class="p_Normal">TEAM-33308 In BRIX mobile application for IOS devices, the three dot icon for creating a new item was not displayed on the app pages. The bug has been fixed.</li><li value="48" class="p_Normal">TEAM-34177 If solutions with the same codes were imported into a company, conflicts occurred when updating the solutions. The bug has been fixed.</li><li value="49" class="p_Normal">TEAM-34262 Found a bug when attempting to copy a custom app to a system workspace. The bug has been fixed. The app is now added correctly.</li><li value="50" class="p_Normal">TEAM-34263 If the user enabled ascending or descending sorting for a field of the <span style="font-weight: bold;">Date/Time</span> type in the Kanban board settings, the sorting was not applied on the app page. The bug has been fixed.</li><li value="51" class="p_Normal">TEAM-34264 If the <span style="font-weight: bold;">Create an app item</span> action was configured in the <span style="font-weight: bold;">Button</span> widget, the item page did not open after filling out the creation form. The bug has been fixed.</li></ol>
<div class="bottom-nav">
<a id="prev-link" class="topic__navi_prev" href="360010947000.html">
<span class="bottom-nav__arrow bottom-nav__arrow--prev"></span> <span
class="bottom-nav__link">360010947000.html</span>
</a>
<a id="next-link" class="topic__navi_next" href="2025_2.html">
<span class="bottom-nav__link">2025_2.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>
Reference in New Issue View Git Blame Copy Permalink