371 lines
71 KiB
HTML
371 lines
71 KiB
HTML
<!DOCTYPE html>
|
||
<html lang="en">
|
||
|
||
<head>
|
||
<title>2025.1</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 > BRIX SaaS / 2025.1</p>
|
||
</div>
|
||
|
||
</div>
|
||
<div class="topic__title"><h1 class="p_Heading1"><span class="f_Heading1">2025.1</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="background-color: #ffffff;">Here is the list of changes that you can explore right now by activating the BRIX trial version.</span></p>
|
||
<p class="p_Normal"><span style="background-color: #ffffff;">After February 13, 2025, 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">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>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Server scripts tracing</span></h2>
|
||
<p class="p_Normal">TEAM-23708 Added <span style="font-weight: bold;">Tracing</span>,<span style="font-weight: bold;"> </span>a new tool for Low-code developers.</p>
|
||
<p class="p_Normal">The tool allows you to analyze the execution of server scripts, find causes of errors, optimize solutions and view changes made.</p>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal">Unknown error: it is necessary to find out the details of what happened.</li><li class="p_Normal">Solution work slowdown: it is important to determine the cause of performance decrease.</li><li class="p_Normal">Solution enhancement: it is needed to evaluate the effectiveness of the changes made.</li></ul>
|
||
<p class="p_Normal">Tool features:</p>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal">Detailed view of traces, attributes and events.</li><li class="p_Normal">Analyzing internal invocations (<code><b>save</b></code>, <code><b>search</b></code>, etc.) as well as external invocations (<code><b>fetch</b></code>).</li><li class="p_Normal">Viewing information about occurring errors.</li><li class="p_Normal">Filtering by system objects, execution time and trace duration.</li><li class="p_Normal">Ability to specify for which configuration objects traces should be saved.</li><li class="p_Normal">Export of traces to a <span style="font-weight: bold;">.json</span> file for easy exchange.</li><li class="p_Normal">Quick transition to trace from business process instances and event handlers.</li><li class="p_Normal">Automatic saved traces cleanup. In the On-Premises edition, you can set the storage period.</li></ul>
|
||
<p class="p_Normal">The <span style="font-weight: bold;">Trace</span> tool frees Low-code specialists from having to use:</p>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal">Third-party apps (Webhook, POSTMAN).</li><li class="p_Normal">Internal custom tools for logging.</li><li class="p_Normal">Additional functions in scripts for debugging.</li></ul>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Low-code CI/CD</span></h2>
|
||
<p class="p_Normal">TEAM-31527 When exporting and importing solutions containing extensions to system directories, the<span style="font-weight: bold;"> Low-code CI / CD</span> tool now displays the changes made within the solution itself.</p>
|
||
<p class="p_Normal">New features:</p>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal">Changes to system directories are visualized in the CI/CD difference tree.</li><li class="p_Normal">The same directory with different metadata is now displayed wherever it is used, with the corresponding parameters.</li></ul>
|
||
<p class="p_Normal">This allows you to track changes to system directories when exporting and importing solutions and makes it easier to monitor whether they have been updated correctly.</p>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Business process efficiency indicators</span></h2>
|
||
<p class="p_Normal">TEAM-15436 Added <span style="font-weight: bold;">Indicators</span>, a<span style="font-weight: bold;"> </span>new Low-code development tool. It is intended for collecting and analyzing data about the progress of business processes in the system.</p>
|
||
<p class="p_Normal">With this tool you can display the statistics of performing certain steps in the process on a chart. For example, you can calculate how many times the sales rep had to revise the contract after its approval was denied or how much the final amount of the deal changed from the planned one.</p>
|
||
<p class="p_Normal">The principle of working with the tool is as follows:</p>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="1" class="p_Normal">You create an indicator within the company or a workspace, customize its type and context variables. The type depends on what data you want to get:</li></ol>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal"><span style="font-weight: bold;">Counter</span>: it captures the passage of certain points on the process diagram. According to the configured process logic, you can count the increase or decrease of the counter value.</li><li class="p_Normal"><span style="font-weight: bold;">Value</span>: it records a certain numerical (calculable) value.</li><li class="p_Normal"><span style="font-weight: bold;">Time interval</span>: it fixes the time interval between two actions in the process with the possibility to calculate it with the business calendar.</li></ul>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="2" class="p_Normal">After creation, a draft of the indicator appears. To use the indicator, publish it.</li><li value="3" class="p_Normal">Then on the business process diagram you add the indicator before the step whose execution statistics you want to record. To do this, you use the<span style="font-weight: bold;"> Set indicator’s value</span> graphical element.</li><li value="4" class="p_Normal">To visualize the collected data, create a separate monitoring page and configure the <span style="font-weight: bold;">Chart</span> widget. When displaying, you can use filtering to analyze the data in detail.</li></ol>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">External portal</span></h2>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="1" class="p_Normal">TEAM-14743 Added page with notification about the external portal inactivity. Now instead of a 404 error, the user sees the following message: “The portal is currently inactive” and account activation is not performed.</li><li value="2" class="p_Normal">TEAM-32064 Added the <span style="font-weight: bold;">My Portals</span> button to the <span style="font-weight: bold;">Page header</span> <span style="font-weight: bold;">widget</span>, which allows the user to quickly switch between available portals without re-authorization. The button is only displayed if the user has access to two or more portals.</li></ol>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Discontinued support for Windows 7, 8/8.1 and legacy browser versions</span></h2>
|
||
<p class="p_Normal">TEAM-31947 Since the <span style="font-weight: bold;">2025.1</span> release, support for legacy <span style="font-weight: bold;">Windows 7, 8/8.1</span> operating systems and older browser versions in <span style="font-weight: bold;">BRIX</span> is no longer supported. <span style="font-weight: bold; color: #800000;">#BreakingChangeAlert</span></p>
|
||
<p class="p_Normal">Reasons for change:</p>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal"><span style="font-weight: bold;">Microsoft</span> ended support for <span style="font-weight: bold;">Windows 8.1</span> in January 2023 (<a href="https://learn.microsoft.com/en-us/lifecycle/products/windows-81" target="_blank" class="weblink">read more</a>), and <span style="font-weight: bold;">Windows 7</span> and <span style="font-weight: bold;">8</span> even earlier.</li><li class="p_Normal"><span style="font-weight: bold;">Google Chrome </span>and<span style="font-weight: bold;"> Chromium</span>, the base of many modern browsers, also ended support for Windows 7 and 8/8.1 in January 2023 (<a href="https://support.google.com/chrome/a/answer/7100626?hl=en&sjid=4473093071386497095-EU" target="_blank" class="weblink">read more</a>).</li><li class="p_Normal"><span style="font-weight: bold;">BRIX</span> workstation requirements (<a href="end-user-requirements.html" class="topiclink">read more</a>) are updated to meet today’s security and performance standards.</li></ul>
|
||
<p class="p_Normal">Updated minimum browser versions since the 2025.1 release:</p>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal"><span style="font-weight: bold;">Google Chrome</span> (including mobile): <span style="font-weight: bold;">version 110</span> and above.</li><li class="p_Normal"><span style="font-weight: bold;">Microsoft Edge</span>: <span style="font-weight: bold;">version 110</span> and above.</li><li class="p_Normal"><span style="font-weight: bold;">Firefox</span>: <span style="font-weight: bold;">version 110</span> and above.</li><li class="p_Normal"><span style="font-weight: bold;">Opera</span>: <span style="font-weight: bold;">version 96</span> and above.</li><li class="p_Normal"><span style="font-weight: bold;">Yandex Browser</span>: <span style="font-weight: bold;">version 23</span> and above.</li><li class="p_Normal"><span style="font-weight: bold;">Safari for macOS and iOS</span>: <span style="font-weight: bold;">version 15</span> and above.</li></ul>
|
||
<p class="p_Normal"><span style="font-weight: bold;">What will change for Windows 7 and 8/8.1 users:</span></p>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal">In mid-February 2025, <span style="font-weight: bold;">an update of BRIX for Desktop will be released</span> will be released that will no longer support Windows 7 and 8/8.1.</li><li class="p_Normal">You will only be able to work with <span style="font-weight: bold;">BRIX 2025.1 and above</span> on these systems through browsers that still support them:</li></ul>
|
||
<ul style="list-style-type:disc"><ul style="list-style-type:circle">
|
||
<li style="text-align: justify; line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;"><span style="font-weight: bold;">Yandex Browser</span>.</li><li style="text-align: justify; line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;"><span style="font-weight: bold;">Firefox (versions 110-115)</span>.</li></ul></li></ul>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Marketing</span></h2>
|
||
<p class="p_Normal">TEAM-30770 An <span style="font-weight: bold;">A/B test</span> gateway is implemented in the <span style="font-weight: bold;">Customer journey map designer</span>. It divides the scenario into branches. When the gateway is activated, a scenario branch is defined for each subscriber according to the specified settings. Several <span style="font-weight: bold;">A/B test</span> gateways can be used in a customer journey map.</p>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Product catalog</span></h2>
|
||
<p class="p_Normal">TEAM-28121 Added <span style="font-weight: bold;">BRIX Product catalog</span> system solution. It allows you to create a hierarchical catalog of simple and configurable products. You can group products and their characteristics by subject, set constant values for characteristics, value ranges and dependence on each other.</p>
|
||
<p class="p_Normal">The solution consists of the <span style="font-weight: bold;">Product catalog</span> workspace and the <span style="font-weight: bold;">Select product</span> widget, which is placed on the app item page, for example, in a lead and a deal. Using the widget, you can add a product of interest to the page of a lead or a deal and fill its configurable characteristics with specific values according to specified ranges and rules.</p>
|
||
<p class="p_Normal"><span style="font-weight: bold;">BRIX Product catalog</span> is included in <span style="font-weight: bold;">BRIX Sales Management</span> and <span style="font-weight: bold;">ELMA365 CX</span> solutions and can be activated separately.</p>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Document management</span></h2>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="1" class="p_Normal">TEAM-7489 Added the option to rename created registration offices and categories for storing registered documents in the <span style="font-weight: bold;">Document categorization</span> workspace.</li><li value="2" class="p_Normal">TEAM-9417 In the <span style="font-weight: bold;">Files </span>workspace, the ability to add files in bulk has been implemented. You can now drag-n-drop multiple files from your computer or use the <span style="font-weight: bold;">Create > Upload File</span> button.</li><li value="3" class="p_Normal">TEAM-22508 Added the <span style="font-weight: bold;">Parameters</span> tab where you can set the settings for generating the certificate name using a template in the <span style="font-weight: bold;">Advanced non-qualified e-signature</span> activity of a business process.</li><li value="4" class="p_Normal">TEAM-27904 Added the ability to move item links between folders in the <span style="font-weight: bold;">Files</span> workspace. The <span style="font-weight: bold;">Move</span> action is available for links in both single and bulk modes and works similarly to moving files.</li><li value="5" class="p_Normal">TEAM-29643 In the <span style="font-weight: bold;">Buttons: Download and Edit</span> widget, added the ability to control the <span style="font-weight: bold;">Share</span> button, when clicked on which copied a link to a file. Now the button display in the widget can be enabled similarly to the <span style="font-weight: bold;">Download </span>and<span style="font-weight: bold;"> Edit</span> buttons. If the user does not have the appropriate permissions, the button is hidden, which prevents viewing and downloading the file using the generated link.</li><li value="6" class="p_Normal">TEAM-29917 You can now specify an arbitrary app as an approval object in the settings of the <span style="font-weight: bold;">Approval Sheets</span> widget.</li></ol>
|
||
<p class="p_Normal" style="margin: 0 0 0 34px;">Previously, if an arbitrary app was used in a business process and sent for approval, you could not display the resolution in the <span style="font-weight: bold;">Approval Sheets</span> widget. Now, when placing the widget, for example, on a task form, you can specify that an arbitrary app is sent for approval.</p>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="7" class="p_Normal">TEAM-30768 Added an option to reset the counter in the app and workspace settings. You can now automatically reset the numbering, for example, at the beginning of a new year.</li><li value="8" class="p_Normal">TEAM-30817 Added an option to restrict users from selecting providers in the <span style="font-weight: bold;">Signing</span> activity settings in a business process. You can now enable the <span style="font-weight: bold;">Restrict Providers</span> setting and select from the list only the providers that will be available for signing.</li><li value="9" class="p_Normal">TEAM-31041 An <span style="font-weight: bold;">.rtf</span> file is now allowed to be uploaded to the document templates. It can be selected in the <span style="font-weight: bold;">Generate from Template</span> business process activity.</li><li value="10" class="p_Normal">TEAM-31043 Added support for <span style="font-weight: bold;">.rtf</span> format in the <span style="font-weight: bold;">Insert Watermark</span> business process activity. You can now insert watermarks to documents in this format with subsequent conversion to <span style="font-weight: bold;">.pdf</span>.</li></ol>
|
||
<p class="p_Normal" style="margin: 0 0 0 34px;">Additionally, removed unnecessary output file<span style="font-weight: bold;"> </span>formats, leaving only <span style="font-weight: bold;">.pdf</span> generation.</p>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="11" class="p_Normal">TEAM-31568 Local offline editing is now available for documents added to app items in the BRIX application for desktop.</li></ol>
|
||
<p class="p_Normal" style="margin: 0 0 0 34px;">On the document page, the user can click the <span style="font-weight: bold;">Edit Locally</span> button. Then the file is saved in a special list in the BRIX app and opened in an appropriate office program, e.g. Word. Them the user edits and saves it. When the internet connection is restored, a new version of the document is added to BRIX.</p>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="12" class="p_Normal">TEAM-31429 If the user does not have a module for working with files installed, the<span style="font-weight: bold;"> Edit Locally</span> button is displayed in the file view mode in BRIX. By clicking on it, the user can download <span style="font-weight: bold;">.doc</span>, <span style="font-weight: bold;">.docx</span>, <span style="font-weight: bold;">.xls</span>, and <span style="font-weight: bold;">.xlsx</span> files for local editing.</li></ol>
|
||
<p class="p_Normal" style="margin: 0 0 0 34px;">It is available in the BRIX desktop application.</p>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="13" class="p_Normal">TEAM-31553 Removed the ability to export to <span style="font-weight: bold;">.pdf</span> in the standard approval and approval sheet templates because the template does not transfer correctly and breaks into multiple pages.</li></ol>
|
||
<p class="p_Normal">Implementation details:</p>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal">For custom templates, export to <span style="font-weight: bold;">.pdf</span> is not removed.</li><li class="p_Normal">Export for <span style="font-weight: bold;">.docx</span> templates works correctly.</li><li class="p_Normal">For <span style="font-weight: bold;">.xlsx</span> it is important to set up the mapping table correctly to avoid page splitting.</li></ul>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="14" class="p_Normal">TEAM-31584 In the <span style="font-weight: bold;">Administration > Font Settings</span> workspace, the process for applying downloaded <span style="font-weight: bold;">.ttf</span> fonts has been changed. Now after downloading a font, simply click <span style="font-weight: bold;">Save</span> and the font will automatically update within 5 minutes.</li></ol>
|
||
<p class="p_Normal" style="margin: 0 0 0 34px;">Previously, manual reloading of the service by the administrator was required to apply the changes. Now the update is performed automatically without additional actions.</p>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="15" class="p_Normal">TEAM-32263 Added display of the reserved number on the <span style="font-weight: bold;">Register document</span> task form.</li></ol>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Contracts</span></h2>
|
||
<p class="p_Normal">TEAM-32671 Added the ability to export contract items.</p>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Projects</span></h2>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="1" class="p_Normal">TEAM-29799 When performing a search in the <span style="font-weight: bold;">Project Folder</span> widget, subfolder files are now taken into account.</li><li value="2" class="p_Normal">TEAM-22922 Added <span style="font-weight: bold;">Undo </span>and<span style="font-weight: bold;"> Redo</span> buttons to the calendar editing mode.</li><li value="3" class="p_Normal">TEAM-28084 Added the <span style="font-weight: bold;">Start Work</span> button to the project view form. Now from the project view form you can move a project from draft to work and actually change its status.</li></ol>
|
||
<p class="p_Normal" style="margin: 0 0 0 34px;">The button settings can be changed by the system administrator within the configuration.</p>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="4" class="p_Normal">TEAM-30688 Now it is possible to save the last customized Gantt chart view on the project page. Also added the option to save the status of deployed task branches on the plan.</li><li value="5" class="p_Normal">TEAM-31167 Added logic for calculating forecast dates of task completion to the project plan creation by template.</li><li value="6" class="p_Normal">TEAM-31569 The <span style="font-weight: bold;">Done</span> button is hidden if the progress of a project task is modified via a <span style="font-weight: bold;">widget</span>. Now the status and controls always correspond to the current state of the task.</li><li value="7" class="p_Normal">TEAM-31901 The project schedule import now supports custom fields. Supported data includes the following: string, fractional and integer numbers, yes/no selection, date/time, category, money, reference, phone, email, user, full name, account, and role.</li><li value="8" class="p_Normal">TEAM-31980 Removed unnecessary action confirmation box on the project page when performing a project task from the Gantt chart.</li><li value="9" class="p_Normal">TEAM-32615 Added the <span style="font-weight: bold;">Edit in modal window</span> option to the Gantt Chart widget settings. If the option is <span style="font-weight: bold;">disabled</span>, editing of the schedule is performed <span style="font-weight: bold;">directly on the project view form</span>.</li></ol>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Service</span></h2>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="1" class="p_Normal">TEAM-26119 System supervisor permission assignment has been changed. Before, the <span style="font-weight: bold;">System supervisor</span> was automatically added to all live chats supervisors and given the corresponding permissions.</li></ol>
|
||
<p class="p_Normal" style="margin: 0 0 0 34px;">Now the system supervisor is not a live chat supervisor by default. The <span style="font-weight: bold;">Live Chats</span> workspace is hidden for them, and they do not receive pop-up notifications about new sessions. If necessary, the system supervisor can add themselves to the desired live chat via the <span style="font-weight: bold;">Administration</span> workspace.</p>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="2" class="p_Normal">TEAM-26538 Added the ability to change the positioning of the LiveChat button on the website page for the desktop and mobile versions. When setting up a live chat in the <span style="font-weight: bold;">Administration</span> workspace on the <span style="font-weight: bold;">LiveChat</span> tab, you can set indents in pixels (from 0 to 1000).</li></ol>
|
||
<ol style="list-style-type:decimal" start="3">
|
||
<li value="3" class="p_Normal">TEAM-29905 Added error handling of Telegram integration when trying to create a session ("429 Too Many Requests"), which occurred when the number of requests exceeded the allowed number of requests. Now a notification containing an explanation of the error 429 is displayed to the user.</li></ol>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="4" class="p_Normal">TEAM-31170 The error notifications for the <span style="font-weight: bold;">Assign an operator</span> and <span style="font-weight: bold;">Assign to the “last” operator</span> actions now display a link to the profile of a user who could not be assigned as an operator due to their inactivity.</li><li value="5" class="p_Normal">TEAM-31952 The <span style="font-weight: bold;">Live Chat Messages</span> widget is adapted for BRIX mobile version.</li><li value="6" class="p_Normal">TEAM-31968 Added image preview in LiveChat with resize function using plus and minus icons, mouse wheel or slider.</li></ol>
|
||
<p class="p_Normal" style="margin: 0 0 0 34px;">The preview is available for the following:</p>
|
||
<ul style="list-style-type:disc">
|
||
<li style="line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;">Images sent by an operator.</li><li style="line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;">Images uploaded by a client.</li><li style="line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;">Before the image is sent.</li></ul>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="7" class="p_Normal">TEAM-32672 In the <span style="font-weight: bold;">Live Chat Messages</span> widget settings, the <span style="font-weight: bold;">Events </span>and<span style="font-weight: bold;"> System</span> tabs have been added. These tabs specify system settings that allow you to control the widget<span style="color: #202122; background-color: #ffffff;">’</span>s visibility and access, customize its behavior when hovering over the cursor and when other events occur.</li></ol>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">User experience</span></h2>
|
||
<p class="p_Normal">TEAM-7315 In the search form on the app page, the <span style="font-weight: bold;">Search </span>and<span style="font-weight: bold;"> Save as Filter</span> buttons are now always visible and are not hidden when scrolling. When you enter a query in the search bar, the search form opens. If there are many fields, the buttons remain fixed at the bottom of the screen. This allows you to launch a search without scrolling to the end of the form.</p>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Authorization and user management</span></h2>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="1" class="p_Normal">TEAM-11483 Now when changing password or locking a user, their active sessions are canceled and the user is forcibly logged out.</li><li value="2" class="p_Normal">TEAM-29015 An external remote or locked user will now not receive a password reset email.</li></ol>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Export and import packages</span></h2>
|
||
<p class="p_Normal">TEAM-24570 The improvements significantly optimized the generation of <span style="font-weight: bold;">.e365</span> export packages, making them easier to work with in version control systems and reducing conflicts in parallel development.</p>
|
||
<p class="p_Normal">The main changes:</p>
|
||
<ul style="list-style-type:disc">
|
||
<li style="line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;">Unnecessary system data (author, editor, creation, modification, deletion dates) has been excluded.</li><li style="line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;">Keys in data arrays have been organized (for example, lists of context variables).</li><li style="line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;">Process, widget, and document templates are not updated unless they have changed, which eliminates unnecessary versions.</li><li style="line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;">All IDs that are generated during import have been removed from the export.</li></ul>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Feature flags</span></h2>
|
||
<p class="p_Normal">The restrictions caused by feature flags have been removed. The following features are now available by default and are not controlled by feature flags:</p>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="1" class="p_Normal">TEAM-31671 The <code><b>enableFeedByTargets</b></code> feature flag: the <span style="font-weight: bold;">Object-based activity stream</span> mode displays messages in three tabs: chats, objects, and favorites. This is convenient if employees often have discussions in the object activity streams, for example, when they work with requests or applications.</li><li value="2" class="p_Normal">TEAM-32006 The <code><b>allowAlwaysShowUserFullName</b></code> feature flag: the <span style="font-weight: bold;">Always display full names</span> option so that when searching in the <span style="font-weight: bold;">Users</span> type field, the first, last and middle names of employees are displayed. This will allow you to distinguish employees with the same initials.</li></ol>
|
||
<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-32308 Made changes to the order of functions in the <code><b>search()</b></code> chain to speed up script execution. <span style="font-weight: bold; color: #800000;">#BreakingChangeAlert</span></li></ol>
|
||
<p class="p_Normal" style="margin: 0 0 0 34px;">Now the content passed to the <code><b>where</b></code> chain is not processed at the moment of calling, but when calling <code><b>first</b></code>, <code><b>all</b></code>, or <code><b>count</b></code> instead.</p>
|
||
<p class="p_Normal">As an example, let<span style="color: #202122; background-color: #ffffff;">’s consider the following script:</span></p>
|
||
<p class="p_CodeExample" style="white-space: normal; page-break-inside: avoid;"><span class="f_CodeExample">async</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">function</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">search_items():</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">Promise<</span><span class="f_CodeExample" style="font-weight: bold;">void</span><span class="f_CodeExample">></span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">{</span><br />
|
||
<span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample" style="font-weight: bold;">const</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">search</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">=</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">Application.search();</span><br />
|
||
<span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">console.debug('1');</span><br />
|
||
<span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">search.where((f)</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">=></span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">{</span><br />
|
||
<span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">console.debug('2');</span><br />
|
||
<span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample" style="font-weight: bold;">return</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">f.__name.eq(Context.data.name);</span><br />
|
||
<span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">});</span><br />
|
||
<span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">console.debug('3');</span><br />
|
||
<span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample" style="font-weight: bold;">const</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">res</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">=</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">await</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">search.count();</span><br />
|
||
<span class="f_CodeExample">}</span></p>
|
||
<p class="p_Normal">Console contents in version 2024.11:</p>
|
||
<p class="p_CodeExample" style="white-space: normal; page-break-inside: avoid;"><span class="f_CodeExample">1</span><br />
|
||
<span class="f_CodeExample">2</span><br />
|
||
<span class="f_CodeExample">3</span></p>
|
||
<p class="p_Normal">Console contents in version 2025.1 (the order has changed):</p>
|
||
<p class="p_CodeExample" style="white-space: normal; page-break-inside: avoid;"><span class="f_CodeExample">1</span><br />
|
||
<span class="f_CodeExample">3</span><br />
|
||
<span class="f_CodeExample">2</span></p>
|
||
<ol style="list-style-type:decimal" start="2">
|
||
<li value="2" class="p_Normal">TEAM-18293 Added the ability to bulk delete app items using scripts </li></ol>
|
||
<p class="p_Normal"><code><b>Application.batch().delete():</b></code></p>
|
||
<p class="p_CodeExample" style="white-space: normal; page-break-inside: auto;"><span class="f_CodeExample" style="font-weight: bold;">const</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">count</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">=</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">await</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">Application.batch()</span><br />
|
||
<span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">.</span><span class="f_CodeExample" style="font-weight: bold;">delete</span><span class="f_CodeExample">()</span><br />
|
||
<span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">.where((f,</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">g)</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">=></span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">f.__name.eq(''))</span><br />
|
||
<span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">.notify(needNotify)</span><br />
|
||
<span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">.size(batchSize)</span><br />
|
||
<span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">.all();</span></p>
|
||
<p class="p_Normal">All bulk operations (create, update, delete) require the user to have permissions to import data in the app.</p>
|
||
<ol style="list-style-type:decimal" start="3">
|
||
<li value="3" class="p_CodeExample" style="white-space: normal; page-break-inside: auto;">TEAM-28786 The ability to retrieve table column names has been added to the API app diagrams. Now the API returns not only table column codes, but also their display names. This allows the app diagram data to be used in a more convenient format without the need for additional processing.</li><li value="4" class="p_CodeExample" style="white-space: normal; page-break-inside: auto;">TEAM-31153 Added the <code><b>GET /pub/v1/disk/file/{id}</b></code> API method. It returns minimal information about the file: id, title, dates, author, who updated, and its current version.</li><li value="5" class="p_CodeExample" style="white-space: normal; page-break-inside: auto;">TEAM-22101 Now when using the <code><b>createWithAuthData</b></code> method, no invitation is sent to the user, as the user is created immediately with the <span style="font-weight: bold;">Active</span> status.</li></ol>
|
||
<p class="p_Normal">This allows users with OAuth2 binding to be created without additional mailing, similar to the <code><b>addUserWithoutConfirmation</b></code> method for portal users.</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">TEAM-4713 If you disabled a service variable in the gateway without deleting the conditions of the connectors, you could not access the item properties. Now, when you disable a service variable, the conditions are automatically removed or an informational message is displayed.</li><li value="2" class="p_Normal">TEAM-30313 When updating solutions and workspaces, changed process names were not carried over. After importing a new version of a process into the target company, the name remained old. Now when updating the solution, the process names are synchronized correctly.</li><li value="3" class="p_Normal">TEAM-31108 Improved the order of processing the reply address in the <span style="font-weight: bold;">Email Notification</span> activity:</li></ol>
|
||
<p class="p_Normal" style="margin: 0 0 0 48px;">1. If the <span style="font-weight: bold;">Reply address</span> option is filled in, the option setting is used.</p>
|
||
<p class="p_Normal" style="margin: 0 0 0 48px;">2. If the <span style="font-weight: bold;">Reply address</span> option is not filled in, but the <span style="font-weight: bold;">Send from Reply-to address</span> setting is enabled, then the address set in the <span style="font-weight: bold;">Administration > Email Settings</span> workspace in the <span style="font-weight: bold;">Default reply address</span> option is used.</p>
|
||
<p class="p_Normal" style="margin: 0 0 0 48px;">3. In other cases, the login set in the <span style="font-weight: bold;">Administration > Email Settings</span> workspace is used.</p>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="4" class="p_Normal">TEAM-27241 The <code><b>setFilter</b></code> filter for the <span style="font-weight: bold;">Date/Time</span> field allowed values to be set that did not match the specified conditions, which resulted in incorrect data entry. Now, if the selected date does not match the filter, the field is automatically reverted to the previous value. Similar behavior is implemented for the <span style="font-weight: bold;">Number</span> type fields.</li><li value="5" class="p_Normal">TEAM-28246 When trying to enter data of another type (for example, a number) into a field of the <span style="font-weight: bold;">String</span> type via API, the following error occurred: “Failed to check for duplicates when saving”, and also the following error occurred in the console: “TypeError: STRING must be a string”. This behavior has been fixed. Now the error message displays the correct reason, excluding misleading wording.</li><li value="6" class="p_Normal">TEAM-28736 The <code><b>GET pub/v1/scheme/namespaces/{namespace}/processes/{code}</b></code> method did not include variable mapping data in the response, such as the localized name or currency type for money fields. This error has been fixed.</li><li value="7" class="p_Normal">TEAM-29486 If the <span style="font-weight: bold;">External Users</span> directory is configured to generate the item name via a <span style="font-weight: bold;">template</span> or a <span style="font-weight: bold;">key variable</span>, “<No name>” was displayed when creating a record. This error has been fixed.</li></ol>
|
||
<ol style="list-style-type:decimal" start="8">
|
||
<li value="8" class="p_Normal">TEAM-31387 When activating the <span style="font-weight: bold;">Sales Management</span> solution, the business process activity settings page would freeze if you opened the parameters of a custom action in the <span style="font-weight: bold;">CRM</span> workspace. Now custom actions in business process activities open correctly regardless of the activated solutions.</li></ol>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="9" class="p_Normal">TEAM-31507 When publishing an event handler, spontaneous exit from the constructor occurred periodically even if the script was valid. In the handler table, the handler was displayed in italics and with a red asterisk, indicating unsuccessful publication, although the status was corrected after refreshing the page. This behavior has been fixed.</li><li value="10" class="p_Normal">TEAM-31905 Previously, when performing bulk creation of app items using a script without the right to import data, the following error occurred: “Error: can't create many items: import access denied: forbidden”.</li></ol>
|
||
<p class="p_Normal">What has changed:</p>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal">The error message is now more informative: “can<span style="color: #202122; background-color: #ffffff;">’</span>t create many items: no import permission for app 'ns:code': import access denied: forbidden”.</li><li class="p_Normal">An indication on the necessity of <span style="font-weight: bold;">Data Import</span> type permissions to perform batch operations has been added to the method description.</li><li class="p_Normal">Updated Help materials.</li></ul>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="11" class="p_Normal">TEAM-32066 In server scripts, a wait blocking occurred while executing a call to <code><b>fetch</b></code> and another async operation, and a timeout error occurred in the script:</li></ol>
|
||
<p class="p_CodeExample" style="white-space: normal; page-break-inside: avoid;"><span class="f_CodeExample">font-family:"Times New Roman",serif;color:#333333;mso-ansi-language:EN-US">async function test(): Promise<void> {</span><br />
|
||
<span class="f_CodeExample">font-family:"Times New Roman",serif;color:#333333;mso-ansi-language:EN-US"> const res = await fetch(`https://ya.ru/`); //here could be any address</span><br />
|
||
<span class="f_CodeExample">color:#333333"></span><br />
|
||
<span class="f_CodeExample">color:#333333;mso-ansi-language:EN-US">const users = await System.users.search().first();</span><br />
|
||
<span class="f_CodeExample">font-family:"Times New Roman",serif;color:#333333;mso-ansi-language:EN-US"> const text = await res.text(); //this is where the blocking and freezing occurred</span><br />
|
||
<span class="f_CodeExample">color:#333333">}</span></p>
|
||
<p class="p_Normal">This behavior has been fixed in the new version, as well as in versions 2024.10 and 2024.11.</p>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="12" class="p_Normal">TEAM-32222 Web API description for creating an app item was incorrectly generated if a field of an <span style="font-weight: bold;">Arbitrary App</span> type was used. The description for such a field specified an object, although it should be an array of objects. The description has been fixed.</li><li value="13" class="p_Normal">TEAM-32327 Previously, when bulk updating app item fields using a <span style="font-weight: bold;">script</span>, the <span style="font-weight: bold;">Author</span> system field was changed, which resulted in incorrect data display. Now, when bulk updating field values, the <span style="font-weight: bold;">author of the item is not changed</span>, the original one remains.</li><li value="14" class="p_Normal">TEAM-32551 When clearing a <span style="font-weight: bold;">Number </span>type variable with the <span style="font-weight: bold;">Read only</span> attribute via <code><b>null</b></code> or <code><b>undefined</b></code>, the value in the field was not updated, although the variable became <code><b>undefined</b></code> in the console. Now the variable is correctly displayed as empty after clearing.</li><li value="15" class="p_Normal">TEAM-32790 When creating an external user via the <span style="font-weight: bold;">External Users</span> workspace, the following error occurred: “Error: __id is required” when the user tried to save data and go to the profile. This error has been fixed.</li><li value="16" class="p_Normal">TEAM-32934 When adding days off for <span style="font-weight: bold;">01/01/2025 </span>and<span style="font-weight: bold;"> 01/06/2025</span>, an error about a duplicate exception occurred in the work calendar. This behavior has been fixed.</li><li value="17" class="p_Normal">TEAM-33027 When creating a <span style="font-weight: bold;">Date/Time</span> object specifying month <span style="font-weight: bold;">0 (January)</span>, the value was incorrectly set as <span style="font-weight: bold;">01/01/1970</span>, while it worked correctly for other months. This behavior has been fixed.</li><li value="18" class="p_Normal">TEAM-31062 When opening two or more tabs with an external portal in one browser, an error could occur: “Cache failed to synchronize. Please reload or close the other tabs with the system to display the page correctly”. This error has been fixed.</li><li value="19" class="p_Normal">TEAM-32782 Fixed the display of holidays in the calendar. Previously they were not highlighted in red.</li><li value="20" class="p_Normal">TEAM-32800 Previously push notifications stopped working if a message exceeding the allowed size (e.g. 2300 characters for IOS) was sent. This would cause the device token to be deleted and new notifications would not reach the user.</li></ol>
|
||
<p class="p_Normal" style="margin: 0 0 0 34px;">Now, push notifications that are too long are automatically shortened to the allowable size, preventing loss of tokens and correct delivery of all subsequent notifications.</p>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="21" class="p_Normal">TEAM-33038 An issue was found when working with apps that have folder access restrictions. Users with edit permissions could not modify an item if the combined length of workspace and app codes exceeded 64 characters. It has been fixed.</li><li value="22" class="p_Normal">TEAM-14700 The buttons for attaching a file (the paper clip icon) and mentioning a user (@) were not displayed in the activity stream because their color matched the background. The buttons are now visible, have the correct contrast, and display in the activity stream without any errors.</li><li value="23" class="p_Normal">TEAM-15322 In contracts, when a source app item was deleted using a page, it remained in the list on the contract page. Now the list of items in the contract is automatically updated and deleted items are no longer displayed.</li><li value="24" class="p_Normal">TEAM-16822 Fixed document file deletion via the <span style="font-weight: bold;">Buttons: Download and Edit</span> widget. Added processing for deleted files. Now a task or app form with widget does not freeze, and it is possible to work with an app item and then add a file.</li><li value="25" class="p_Normal">TEAM-28184 Project tasks created in custom project types were missing a link to a linked project, unlike tasks in base types. This behavior has been fixed.</li><li value="26" class="p_Normal">TEAM-29441 In the mobile version of the system, the <span style="font-weight: bold;">Edit</span> button in the <span style="font-weight: bold;">Buttons: Download and Edit</span> widget was displayed even if its display was disabled in the widget settings. This bug has been fixed.</li><li value="27" class="p_Normal">TEAM-30041 In the generated documents, the number of decimal places did not match the specified ones in system settings. More characters were being displayed than specified in the variable settings. This error has been fixed.</li><li value="28" class="p_Normal">TEAM-30062 With <span style="font-weight: bold;">BRIX Advanced Security Pack</span> installed and file protection enabled, errors occurred when sending e-mail messages with attachments:</li></ol>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal">When importing data: “failed to get file body: 401 Unauthorized”.</li><li class="p_Normal">When sending an Email with attachment: “got HTTP status code 401”.</li></ul>
|
||
<p class="p_Normal" style="margin: 0 0 0 34px;">This bug has been fixed.</p>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="29" class="p_Normal">TEAM-30442 Previously, if a template project did not exist (for example, it was deleted or missing after a configuration migration), the <span style="font-weight: bold;">Edit</span> button in the <span style="font-weight: bold;">Administration > Project Types</span> workspace did not work.</li></ol>
|
||
<p class="p_Normal" style="margin: 0 0 0 34px;">Now if there is no template project, a new empty template is automatically created.</p>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="30" class="p_Normal">TEAM-30935 Custom statuses in approval sheets were not displayed or were ignored if multiple approval activities were used in a process. Such statuses are now displayed correctly.</li><li value="31" class="p_Normal">TEAM-30953 Previously, if a value was passed from a <span style="font-weight: bold;">File</span> type variable to another variable, editing the new variable modified the original file instead of creating an independent copy. Now editing does not affect the original.</li><li value="32" class="p_Normal">TEAM-31121 The <span style="font-weight: bold;">Reverse auto-scheduling</span> feature is hidden from the Gantt chart user interface. Gantt chart functionality needs to be enhanced for the backward planning feature to work correctly. The improvement is scheduled for the third or fourth quarter of 2025.</li><li value="33" class="p_Normal">TEAM-31123 Added the ability to link three or more phase tasks on a Gantt chart.</li><li value="34" class="p_Normal">TEAM-31434 Added priority for fonts downloaded via the <span style="font-weight: bold;">Administration</span> workspace. This priority now preserves correct formatting (line breaks) when converting documents to <span style="font-weight: bold;">.pdf</span>.</li><li value="35" class="p_Normal">TEAM-31723 When downloading signed attributes, the <code><b>__version</b></code> field was added even though it was not selected in the settings. Now when downloading, only the fields specified in the signing settings are present in the file.</li><li value="36" class="p_Normal">TEAM-31837 Fixed forms freezing when using the <span style="font-weight: bold;">Hierarchical Structure</span> widget.</li><li value="37" class="p_Normal">TEAM-31847 Project border shift logic now includes processing of nested tasks. Previously, nested tasks were not taken into account when calculating the automatic project border shift.</li><li value="38" class="p_Normal">TEAM-32135 Improved the <span style="font-weight: bold;">NumberToString()</span> function in the templating engine. Incorrect processing of a number with a fractional part has been fixed.</li><li value="39" class="p_Normal">TEAM-32157 Fixed project tasks highlighting with the <span style="font-weight: bold;">Process</span> type.</li><li value="40" class="p_Normal">TEAM-32192 Fixed the following pop-up error: “Cannot read properties of undefined” when closing a project.</li><li value="41" class="p_Normal">TEAM-32228 When exporting and importing solutions, hierarchical directory filters did not change their names and folder binding, nor were they deleted when necessary. This behavior has been fixed.</li><li value="42" class="p_Normal">TEAM-32342 When using a custom signing provider in E-IMZO, the task would not close after signing and the process would not continue. It has been fixed by fixing errors in extension zone operation in terms of handling electronic signatures in custom E-signature modules.</li><li value="43" class="p_Normal">TEAM-32409 When using a <span style="font-weight: bold;">SES</span> module with two-factor authorization, an “Internal error” occurred when attempting to sign a document. Now an additional check has been added and the document signing process is successful after entering the code sent to the specified email.</li><li value="44" class="p_Normal">TEAM-32442 In the default signature watermark template, the signature data was overlapping. The template has been fixed in the printed form of the document.</li><li value="45" class="p_Normal">TEAM-32731 With <span style="font-weight: bold;">BRIX Advanced Security Pack</span> installed and file protection enabled, import did not work and the company logo was not displayed. This error has been fixed. Added an exception for the logo to work when file protection is enabled.</li><li value="46" class="p_Normal">TEAM-32758 Fixed time display in a <span style="font-weight: bold;">Date/Time</span> type variable when generating a file by a template. The display corresponds to the variable settings.</li><li value="47" class="p_Normal">TEAM-32798 On initial loading of the contract page, after selecting multiple records and clicking the <span style="font-weight: bold;">Selected Items</span> button, the bulk action drop-down list was not displayed. Instead, only an arrow was shown. This error has been fixed.</li><li value="48" class="p_Normal">TEAM-32963 When completing an associated task, a false notification about incomplete tasks present occurred even if the previous parent task had already been closed. Now the status check of the preceding tasks is done correctly and the notification is not displayed unnecessarily.</li><li value="49" class="p_Normal">TEAM-31777 To improve the user experience, the icon for the <span style="font-weight: bold;">Create Shortcut</span> feature in the <span style="font-weight: bold;">Files</span> workspace has been changed. Previously, it was similar to the <span style="font-weight: bold;">Copy Link</span> function icon.</li><li value="50" class="p_Normal">TEAM-31848 Previously, when publishing a calendar plan, the enabled <span style="font-weight: bold;">Auto-scheduling</span> option caused the task dates to be adjusted. Now the function does not make the adjustment when publishing, only during the calendar plan editing.</li><li value="51" class="p_Normal">TEAM-31960 <span style="font-weight: bold;">Archived project plans</span> are now displayed in a <span style="font-weight: bold;">Gantt chart</span>. This allows you to view project plans even if they are in the <span style="font-weight: bold;">Archived</span> status and <span style="font-weight: bold;">retrospectively analyze</span> completed projects before returning them to work.</li><li value="52" class="p_Normal">TEAM-32975 Corrected the description of the <span style="font-weight: bold;">toPdf </span>and<span style="font-weight: bold;"> applyWatermark</span> methods for TS SDK scripts.</li><li value="53" class="p_Normal">TEAM-27194 Fixed incorrect system behavior when receiving a pop-up notification about a new session: previously clicking on the notification did not switch to the session. After the improvement, clicking on the notification triggers the transition to the session, also:</li></ol>
|
||
<p class="p_Normal" style="margin: 0 0 0 48px;">1. If there was a window opened, and it does not require saving changes, the window is closed.</p>
|
||
<p class="p_Normal" style="margin: 0 0 0 48px;">2. If there was a window opened, and it requires changes to be saved, the user is offered to save the changes (for example, on the edit form). If the user refuses, the session does not open.</p>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="54" class="p_Normal">TEAM-30141 Added handling of the messenger error “400 USERNAME_NOT_OCCUPIED” that occurs when trying to create a session in a Telegram channel. Now when such a response is returned, the user receives a clear notification that it is impossible to create a session for the selected account due to an error on the messenger side.</li><li value="55" class="p_Normal">TEAM-31834 Improved system behavior when quoting and editing messages in the session chat: now if a typed quote or edited text cannot be sent, the unsent message is saved so that the user does not have to type it again for the next attempt to send it.</li><li value="56" class="p_Normal">TEAM-31928 Fixed incorrect system behavior when quoting a message in a chat session. Prior to the fix, when quoting was used, the edited text was saved in the input field instead of the previously selected edit. After the fix, when quoting is selected, only the quote is displayed in the input field.</li><li value="57" class="p_Normal">TEAM-32303 Changed the operator selection logic in the session routing rule when selecting the <span style="font-weight: bold;">Assign to Least Occupied Operator in a Group</span> option.</li></ol>
|
||
<p class="p_Normal" style="margin: 0 0 0 34px;">Before the fix, only locked users were excluded from the selection. After the fix, when a rule with the specified action is triggered, a session cannot be assigned to users with the <span style="font-weight: bold;">Invited</span>, <span style="font-weight: bold;">Invitation canceled</span>, <span style="font-weight: bold;">Invitation rejected</span> statuses, i.e. a session can only be assigned to active users. If there are no operators matching these conditions, a system notification is issued.</p>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="58" class="p_Normal">TEAM-32376 The <span style="font-weight: bold;">Counter</span> item is hidden from the <span style="font-weight: bold;">Sessions</span> app settings because the <span style="font-weight: bold;">Index number</span> system field is not used in this app now.</li><li value="59" class="p_Normal">TEAM-32433 Fixed incorrect system behavior when moving words in a message from a client in LiveChat window: now it is moved word by word, left-aligned.</li><li value="60" class="p_Normal">TEAM-32460 Hidden the time display of the welcome message in LiveChat, since it is not actually part of the correspondence and is not indicative.</li><li value="61" class="p_Normal">TEAM-32650 Fixed an issue with the <span style="font-weight: bold;">Sessions</span> app not being available in the <span style="font-weight: bold;">Live Chats</span> workspace for the operators and supervisors who are not system administrators and supervisors.</li><li value="62" class="p_Normal">TEAM-12050 When working with business processes, variables assigned in a task context with empty values were not saved correctly. This caused variable values to remain the same even though they should have been reset. This behavior has been fixed.</li><li value="63" class="p_Normal">TEAM-22789 Now number of items in status on the kanban board is not shown when set to <span style="font-weight: bold;">Do not Show</span> in the <span style="font-weight: bold;">Show the number of items in the search field</span> setting.</li><li value="64" class="p_Normal">TEAM-31812 The activity stream counter was not working correctly, showing nonexistent unread messages. This bug has been fixed, now the <span style="font-weight: bold;">Read</span> button removes all incorrect counters.</li><li value="65" class="p_Normal">TEAM-31866 After creating a new group in a workspace, it was not displayed in the tree until the page refreshed. This was causing a possible incorrect retry to create a group. Now the new group is displayed immediately after creation, without the need to refresh the page.</li><li value="66" class="p_Normal">TEAM-31925 For substitutions of the <span style="font-weight: bold;">Inform</span> type created via script with <code><b>reassignTasksOnEnd = true</b></code> and <code><b>reassignTasksOnStart = true</b></code> enabled, tasks from the absent user should not have been reassigned, but they were. This bug has been fixed.</li><li value="67" class="p_Normal">TEAM-32011 Added error handling for email address and phone number when re-importing a user that was previously imported and deleted.</li><li value="68" class="p_Normal">TEAM-32470 When debugging an unpublished process with a task with a custom form, the task would not open and the error “Cannot read properties of undefined (reading ‘code’)” would appear. This error has been fixed. Now the process with a new form opens correctly in debugging mode.</li><li value="69" class="p_Normal">TEAM-32649 An error with the code 404 instead of 403 was returned earlier when the app page was not accessed. Now when a user does not have an access, error 403 is correctly received, indicating insufficient permissions to access the resource.</li><li value="70" class="p_Normal">TEAM-32925 When adding two modal windows with a <span style="font-weight: bold;">Table</span> type field to a form and filling at least one box, the table would start flashing and error 404 would appear in the console. This behavior has been fixed.</li><li value="71" class="p_Normal">TEAM-32962 When trying to leave a reaction to a message in the mobile version, the following issues occurred: the reaction was either not left or was left twice. This bug has been fixed.</li></ol>
|
||
|
||
<div class="bottom-nav">
|
||
|
||
<a id="prev-link" class="topic__navi_prev" href="2025_2.html">
|
||
<span class="bottom-nav__arrow bottom-nav__arrow--prev"></span> <span
|
||
class="bottom-nav__link">2025_2.html</span>
|
||
</a>
|
||
|
||
|
||
<a id="next-link" class="topic__navi_next" href="2024_11.html">
|
||
<span class="bottom-nav__link">2024_11.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>
|