koziavin
00717a92fb
All checks were successful
Deploy Static Site / deploy (push) Successful in 6m6s
356 lines
56 KiB
HTML
356 lines
56 KiB
HTML
<!DOCTYPE html>
|
||
<html lang="en">
|
||
|
||
<head>
|
||
<title>2023.10</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="Below is a list of changes that you can explore right now by activating the BRIX demo version. After November 16, 2023, all changes will become available to our clients in..." />
|
||
<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 / 2023.10</p>
|
||
</div>
|
||
|
||
</div>
|
||
<div class="topic__title"><h1 class="p_Heading1"><span class="f_Heading1">2023.10</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">Below is a list of changes that you can explore right now by activating the BRIX demo version. After November 16, 2023, all changes will become available to our clients in their active companies. Please note that the list may be expanded after the release.</p>
|
||
<p class="p_Normal"> </p>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Workspace administrators</span></h2>
|
||
<p class="p_Normal">TEAM-752: Local administration for workspaces has been added. To activate, the feature flag <code><b> 'useConfigurationAccess'</b></code> must be enabled.</p>
|
||
<p class="p_Normal">Administrators are assigned in the workspace menu.</p>
|
||
<p class="p_Normal">Restrictions for a workspace administrator:</p>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal">No access to the global <span style="font-weight: bold;">Administration</span> workspace and management of global entities (such as business processes, interfaces, users, modules, etc.).</li><li class="p_Normal">Unable to administer other workspaces without the corresponding rights.</li><li class="p_Normal">No access to app items and workspace pages if the corresponding rights were not provided.</li></ul>
|
||
<p class="p_Normal">Available features:</p>
|
||
<p class="p_Normal">Workspace administrators can manage all other settings and parameters within their workspace, excluding:</p>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal">additional parameters;</li><li class="p_Normal">access settings;</li><li class="p_Normal">API.</li></ul>
|
||
<p style="line-height: 1.20;"><span style="font-size: 13px; color: #000000;"> </span></p>
|
||
<p class="p_Normal"> </p>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Report type app</span></h2>
|
||
<p class="p_Normal">1. TEAM-17151: The following enhancements have been implemented for the <span style="font-weight: bold;">Report</span> type app:</p>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal">Added the ability to create fields of the <span style="font-weight: bold;">Report</span> type in widgets;</li><li class="p_Normal">When creating a field of the <span style="font-weight: bold;">Report</span> type in widgets in modules, the options Input/Output are locked and have the value <code><b>false</b></code>;</li><li class="p_Normal">Interface builder: when using a field of the <span style="font-weight: bold;">Report</span> type on a form, a link to this report is provided;</li><li class="p_Normal">Autocomplete by report columns added in TSSDK;</li><li class="p_Normal">Fields of the <span style="font-weight: bold;">Report</span> type are generated with the <code><b>'readonly'</b></code> modifier;</li><li class="p_Normal">Fields of the <span style="font-weight: bold;">Report</span> type provide search and filtering functions, similar to apps.</li></ul>
|
||
<p class="p_Normal">2. TEAM-19803: Similar to apps, an API item has been added to the menu of the <span style="font-weight: bold;">Report</span> type page. The API provides one method: "Getting a list of report items".</p>
|
||
<p class="p_Normal"> </p>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Authentication via external providers</span></h2>
|
||
<p class="p_Normal">TEAM-20617: In <span style="font-weight: bold;">Administration > Security Settings</span>, new features have been added:</p>
|
||
<p class="p_Normal">1. In the <span style="font-weight: bold;">Password Policy</span> block, the option to <span style="font-weight: bold;">Forbid password recovery</span> has been added. If it is enabled, the <span style="font-weight: bold;">Recover Password</span> button is not displayed on the login form.</p>
|
||
<p class="p_Normal">2. A new block has been added: <span style="font-weight: bold;">External Authentication Providers</span>. Options in the block:</p>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal">allow OAuth2 authentication <span style="font-weight: bold;">Select available providers</span>. If providers are not selected, all configured modules are available.</li><li class="p_Normal">default authentication method: Internal (login/password), External (OAuth).</li></ul>
|
||
<p class="p_Normal"> </p>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">SMS providers</span></h2>
|
||
<p class="p_Normal">1. TEAM-13177: Implemented the ability to add new SMS providers through modules for the standard SMS sending and 2FA block.</p>
|
||
<p class="p_Normal">To implement your own SMS provider, you need to:</p>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="1" class="p_Normal">Create a module.</li><li value="2" class="p_Normal">In the API methods tab, click <span style="font-weight: bold;">Edit</span> and go to the <span style="font-weight: bold;">Scripts</span> tab.</li><li value="3" class="p_Normal">Implement interfaces:</li></ol>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample" style="font-style: italic;">// Data structure for storing the connection check response.</span><br />
|
||
<span class="f_CodeExample" style="font-weight: bold;">interface</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">SMSTestConnectionResult</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">success:</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">boolean;</span><br />
|
||
<span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">failReason:</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample" style="font-weight: bold;">string</span><span class="f_CodeExample">;</span><br />
|
||
<span class="f_CodeExample">}</span><br />
|
||
<span class="f_CodeExample"> </span><br />
|
||
<span class="f_CodeExample" style="font-style: italic;">// Data structure for storing the response of sending SMS to a number.</span><br />
|
||
<span class="f_CodeExample" style="font-weight: bold;">interface</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">SMSSendError</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">phone:</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample" style="font-weight: bold;">string</span><span class="f_CodeExample">;</span><br />
|
||
<span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">statusCode?:</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">number;</span><br />
|
||
<span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">statusText?:</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample" style="font-weight: bold;">string</span><span class="f_CodeExample">;</span><br />
|
||
<span class="f_CodeExample">}</span></p>
|
||
<p class="p_Normal">Implement the SMS sending function.</p>
|
||
<p class="p_CodeExample" style="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">SMSSendSMS(phones:</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample" style="font-weight: bold;">string</span><span class="f_CodeExample">[],</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">msg:</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample" style="font-weight: bold;">string</span><span class="f_CodeExample">):</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">Promise<SMSSendError[]></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-style: italic;">// function content</span><br />
|
||
<span class="f_CodeExample">}</span></p>
|
||
<p class="p_Normal"> </p>
|
||
<p class="p_Normal">The implemented SMS provider can be used for:</p>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal">Two-factor authentication;</li><li class="p_Normal">Authentication via phone number and one-time codes;</li><li class="p_Normal">Send SMS block.</li></ul>
|
||
<p class="p_Normal"> </p>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Scripts</span></h2>
|
||
<p class="p_Normal">TEAM-18590: Added a restriction on the maximum size and storage time of data in the script cache: <code><b>System.cache, Namespace.cache, Application.cache</b></code>.</p>
|
||
<p class="p_Normal">Set maximum size to 16 MB (same as for storage). If more data is passed, an error appears.</p>
|
||
<p class="p_Normal">Set the maximum cache lifetime.</p>
|
||
<p class="p_Normal">Defaults:</p>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal">For on-premises = 180 days</li><li class="p_Normal">For SaaS = 14 days</li></ul>
|
||
<ul style="list-style-type:circle"><ul style="list-style-type:circle">
|
||
<li style="line-height: 1.20;">If a larger TTL is passed, the smaller one is used<span style="font-family: 'Segoe UI',Tahoma,Verdana,Arial,sans-serif;">.</span></li></ul></li></ul>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal">Added environment variables in the worker-gateway service (for configuration in on-premises):</li></ul>
|
||
<ul style="list-style-type:circle"><ul style="list-style-type:circle">
|
||
<li class="p_Normal"><code><b>ELMA365_MAX_CACHE_ITEM_SIZE</b></code> — the maximum size of the value that can be saved in System.cache or Namespace.cache, set in kilobytes, e.g., 1024 corresponds to 1 MB.</li><li class="p_Normal"><code><b>ELMA365_MAX_STORAGE_ITEM_SIZE</b></code> — the maximum size of the value that can be saved in System.storage or Namespace.storage, set in kilobytes, e.g., 1024 corresponds to 1 MB.</li><li class="p_Normal"><code><b>ELMA365_CACHE_ITEM_LIFETIME</b></code> — the maximum lifetime (TTL) of a value in the cache: System.cache or Namespace.cache, set as 1s (one second), 1h (one hour), etc.</li></ul></li></ul>
|
||
<p class="p_Normal"> </p>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Tables</span></h2>
|
||
<p class="p_Normal">1. TEAM-23: Added a function to the <span style="font-weight: bold;">Table</span> widget: <span style="font-weight: bold;">Predefined Filter</span>. A new tab has been introduced, allowing you to set filters that are automatically applied when displaying data. You can configure filtering by specific values or values obtained from contextual variables. This provides more accurate and convenient data handling immediately after opening the widget.</p>
|
||
<p class="p_Normal">2. TEAM-5539: Added the ability to link the <span style="font-weight: bold;">Table</span> widget to a variable.</p>
|
||
<p class="p_Normal">As a data source for the <span style="font-weight: bold;">Table</span> widget, you can now select a variable of the App type (many).</p>
|
||
<p class="p_Normal">Update features:</p>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal">The predefined filter will be automatically applied before showing data in the table.</li><li class="p_Normal">User access rights are now considered when displaying data: the table will only show items that the user has access to.</li></ul>
|
||
<p class="p_Normal"> </p>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Widgets</span></h2>
|
||
<p class="p_Normal"> </p>
|
||
<p class="p_Normal">1. TEAM-17931: Added a new <span style="font-weight: bold;">Rendering finished</span> setting in the widget builder. This allows developers to use the system function onLoad, which is activated after the widget has fully loaded. The function is now integrated into the user interface under the <span style="font-weight: bold;">Settings > System functions</span> tab.</p>
|
||
<p class="p_Normal"> </p>
|
||
<p class="p_Normal">2. TEAM-16243: The Associated items widget now allows adding filters available to users.</p>
|
||
<p class="p_Normal"> </p>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Launching processes from app forms</span></h2>
|
||
<p class="p_Normal"> </p>
|
||
<p class="p_Normal">1. TEAM-6347: The ability to add multiple <span style="font-weight: bold;">Save</span> buttons has been introduced on the creation and editing forms. These buttons can be linked to a process and triggered automatically after saving the form.</p>
|
||
<p class="p_Normal">Key features:</p>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal">The existing default <span style="font-weight: bold;">Save</span> button cannot be removed;</li><li class="p_Normal">Custom <span style="font-weight: bold;">Save</span> buttons can be deleted;</li><li class="p_Normal">Custom <span style="font-weight: bold;">Save</span> buttons allow selecting an associated business process;</li><li class="p_Normal">The automatic and manual linking of a business process, created in an app, binds the process to the existing default <span style="font-weight: bold;">Save</span> button;</li><li class="p_Normal">Custom <span style="font-weight: bold;">Save</span> buttons have the option to validate the required fields;</li><li class="p_Normal">Custom <span style="font-weight: bold;">Save</span> buttons have an <span style="font-weight: bold;">always</span> display option, if there is access to edit or delete;</li><li class="p_Normal">Custom <span style="font-weight: bold;">Save</span> buttons on the editing form have the option <span style="font-weight: bold;">Only for selected statuses</span>.</li></ul>
|
||
<p class="p_Normal"> </p>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Copying workspaces and apps</span></h2>
|
||
<p class="p_Normal"> </p>
|
||
<p class="p_Normal">TEAM-10461: Previously, copying an entity duplicated its history, leading to confusion and errors in data import and update. In the current update, copying an entity creates a new history to ensure its status as an independent object. Thus, copying a workspace or app now creates a new first entry in history for all structures in the copied namespace.</p>
|
||
<p class="p_Normal"> </p>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Data display</span></h2>
|
||
<p class="p_Normal">TEAM-4145: Updated interface: added a Subtype column in the properties lists. A new feature has been added to all tables where properties are displayed - a <span style="font-weight: bold;">Subtype</span> column. This update will allow viewing additional settings of property types for improved management and easier configuration.</p>
|
||
<p class="p_Normal"> </p>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Process administration</span></h2>
|
||
<p class="p_Normal">TEAM-10753: In <span style="font-weight: bold;">Administration</span>, the <span style="font-weight: bold;">Process Monitor</span> and <span style="font-weight: bold;">Business Processes</span> pages now include a <span style="font-weight: bold;">Module Processes</span> folder. It contains a list of custom modules and their processes.</p>
|
||
<p class="p_Normal"> </p>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Task reminders</span></h2>
|
||
<p class="p_Normal">TEAM-20395: We extended the reminder period for tasks in the user profile settings. New periods added: 3 hours 30 minutes, 4 hours, 8 hours, 1 day, 2 days, and 1 week.</p>
|
||
<p class="p_Normal"> </p>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Performance reports</span></h2>
|
||
<p class="p_Normal">TEAM-21787: Implemented the ability to delete saved periodic performance reports and report files to clear outdated data.</p>
|
||
<p class="p_Normal"> </p>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">ECM</span></h2>
|
||
<h3 class="p_Heading3"><span class="f_Heading3">Approval and sending for information</span></h3>
|
||
<p class="p_Normal">1. TEAM-2039 and TEAM-22958: Added the ability to configure a custom form for tasks in the <span style="font-weight: bold;">Approval</span> and <span style="font-weight: bold;">Send document/app item</span> activities.</p>
|
||
<p class="p_Normal">2. TEAM-22803: Added the option to select a specific electronic signature provider when setting up <span style="font-weight: bold;">Approval</span> and <span style="font-weight: bold;">Send document/app item</span> activities. This allows modeling a process with a pre-defined signature provider, which cannot be changed by the user during task execution.</p>
|
||
<h3 class="p_Heading3"><span class="f_Heading3">Contracts</span></h3>
|
||
<p class="p_Normal">TEAM-18661: Added a bulk action feature for contract items, including editing, deleting, restoring, and starting business processes. The feature is activated in the contract settings.</p>
|
||
<h3 class="p_Heading3"><span class="f_Heading3">Electronic signature</span></h3>
|
||
<p class="p_Normal">1. TEAM-19782: Enhanced the displayed information about certificates when signing. Now, when selecting a certificate for electronic signing, additional information is displayed, including details about the Certification Authority (CA), certificate location, and its validity period.</p>
|
||
<p class="p_Normal">2. TEAM-20732: In the administration settings, the <span style="font-weight: bold;">Electronic Signature</span> module now has an option for <span style="font-weight: bold;">Automatic certificate generation</span>. In this case, electronic signature certificates for users within BRIX will be created automatically. This option does not require additional setup, unlike issuing a certificate during a business process.</p>
|
||
<h3 class="p_Heading3"><span class="f_Heading3">Templates</span></h3>
|
||
<p class="p_Normal">1. TEAM-21246: Added multiple conditions in templates. Logical operators AND and OR allow setting multiple conditions as a single construct. When using OR, it is sufficient for at least one of the conditions to be met.</p>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">**Example</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">1**</span><br />
|
||
<span class="f_CodeExample">{</span><span class="f_CodeExample" style="font-weight: bold;">if</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">{$trip.transports_type}</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><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">OR</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">{$trip.transports_type}</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><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">{$business_trip_request.city}</span><br />
|
||
<span class="f_CodeExample">{end}</span></p>
|
||
<p class="p_Normal" style="margin: 20px 0 0 0;"><span style="font-family: 'Segoe UI',Tahoma,Verdana,Arial,sans-serif;">When using AND, all listed conditions need to be met.</span></p>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">**Example</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">1**</span><br />
|
||
<span class="f_CodeExample">{</span><span class="f_CodeExample" style="font-weight: bold;">if</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">{$item.price}</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">5000</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">AND</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">{$item.isAvailable}}</span><br />
|
||
<span class="f_CodeExample">-</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">{$item.name}</span><br />
|
||
<span class="f_CodeExample">{end}</span></p>
|
||
<p class="p_Normal">Conditions can also be combined using brackets.</p>
|
||
<p class="p_Normal">2. TEAM-21598: Users can now add document templates directly through <span style="font-weight: bold;">Administration</span> > <span style="font-weight: bold;">Document Templates</span>, even if the solution is locked.</p>
|
||
<h3 class="p_Heading3" style="line-height: 1.38;"><span class="f_Heading3">Document viewing</span></h3>
|
||
<p class="p_Normal">TEAM-21455: Added the ability to change the orientation of a document during viewing.</p>
|
||
<p class="p_Normal"> </p>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">BRIX CRM</span></h2>
|
||
<p class="p_Normal">1. TEAM-22815: Added a new widget in CRM: <span style="font-weight: bold;">Subscriber activity log</span>.</p>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal">Displays customer interactions from latest to earliest.</li><li class="p_Normal">Includes 13 types of actions: Leads, Deals, CRM tasks, and others.</li><li class="p_Normal">Recommended for use in <span style="font-weight: bold;">Contacts</span> and <span style="font-weight: bold;">Leads</span> apps.</li><li class="p_Normal">On the <span style="font-weight: bold;">Deals</span> form, gathers information from all related contacts.</li><li class="p_Normal">Planned update for adding custom activities by the end of 2023.</li><li class="p_Normal">For proper operation, requires to be bound with the widget's contacts. Also,in email settings, automatic binding of contacts with incoming emails is required.</li></ul>
|
||
<p class="p_Normal">2. TEAM-21600 and TEAM-22793: Added a <span style="font-weight: bold;">Nurturing stages</span> widget that shows customer readiness to purchase.</p>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal">Tracks customer touchpoints to assess their activity.</li><li class="p_Normal">Recommended to be placed on the right panel in <span style="font-weight: bold;">Subscribers</span>, <span style="font-weight: bold;">Leads</span>, <span style="font-weight: bold;">Contacts</span> apps.</li><li class="p_Normal">Ability to set rules for calculating nurturing stage.</li><li class="p_Normal">Added feature for recalculating the nurturing stage based on new rules. </li></ul>
|
||
<p class="p_Normal">3. TEAM-22023 and TEAM-22209: CRM now has a <span style="font-weight: bold;">Hierarchy</span> widget, allowing setting relationships between items and displaying them in tree or table form.</p>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal">Customizable composition of displayed properties.</li><li class="p_Normal">Supports up to 100 levels of nesting.</li><li class="p_Normal">Suitable for working with hierarchies of contractors or contacts.</li><li class="p_Normal">In the <span style="font-weight: bold;">Companies</span> app, <span style="font-weight: bold;">Parent company</span> and <span style="font-weight: bold;">Subsidiaries</span> fields added for creating hierarchical structures. </li></ul>
|
||
<p class="p_Normal">4. TEAM-22492: Improved contact search in CRM. When filling the <span style="font-weight: bold;">Contact</span> field in CRM tasks, you can now use advanced search. Here is how it works:</p>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal">When you start typing in the search field, only those contacts already linked to the company associated with the deal will be shown.</li><li class="p_Normal">If no contacts are linked to the company, you can quickly find the required contact among all records in the directory using the <span style="font-weight: bold;">Search by parameters</span> filter.</li></ul>
|
||
<p class="p_Normal">5. TEAM-22652: When creating a <span style="font-weight: bold;">Email Sent</span> activity, you can now save a link to the email in the activity card.</p>
|
||
<p class="p_Normal">6. TEAM-19663: Added a checkbox to the <span style="font-weight: bold;">App item status</span> widget settings: <span style="font-weight: bold;">Forbid to edit pipeline</span>.</p>
|
||
<p class="p_Normal">7. TEAM-21295: Added user identifier in the <span style="font-weight: bold;">Sales manager dashboard</span>.</p>
|
||
<p class="p_Normal"> </p>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">BRIX Service</span></h2>
|
||
<p class="p_Normal">1. TEAM-20675: For email, added the ability to create sessions for multiple users. Implemented through the send message block in the business process. When setting up the block with email as the communication channel, you can now specify additional recipients. Such a session remains open until closed by the operator. By default, the operator is the user who initiated the process, unless it is a system account. If the message is sent by the system, the session will be available in the general queue for operators.</p>
|
||
<p class="p_Normal"> </p>
|
||
<p class="p_Normal">2. TEAM-20677: Added channel filtering in live chat reports. Now you can filter data by the channel of incoming messages. This is convenient when you need to evaluate the team's work in different messengers, like email or Telegram. The feature will help understand the dynamics of requests and optimize the workload distribution among teams.</p>
|
||
<p class="p_Normal"> </p>
|
||
<p class="p_Normal">3. TEAM-21191: Added the ability to automatically send messages to customers when creating new sessions. This ensures that clients receive confirmation of message delivery before the operator joins the dialogue. In case of an error in sending the auto-reply, another attempt will be made after 15 seconds. If the retry is also unsuccessful, a corresponding system message about the malfunction will be displayed.</p>
|
||
<p class="p_Normal"> </p>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">BRIX Projects</span></h2>
|
||
<p class="p_Normal">1. TEAM-17138: Improved the import of projects from MS Project. This update fixes the previously occurring error 500 and ensures accurate preservation of task hierarchy according to your original project plan in MS Project.</p>
|
||
<p class="p_Normal">Update details:</p>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal">Fixed an error that caused a failure when importing multi-level projects.</li><li class="p_Normal">Implemented the creation of stage tasks with accurate adherence to levels of nesting.</li><li class="p_Normal">Now complex project plans can be easily imported, maintaining the entire structure and detail of tasks.</li></ul>
|
||
<p class="p_Normal">2. TEAM-17212: Added a toolbar for ease of working with the project plan in view mode. Project managers and participants can now adjust the scale, apply filters, and access settings directly from the Project Plan widget.</p>
|
||
<p class="p_Normal">Updates include:</p>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal">Icons for collapsing and expanding tasks.</li><li class="p_Normal">Scale control elements.</li><li class="p_Normal">Filters for easy search.</li><li class="p_Normal">Access to settings without auto-planning functions.</li><li class="p_Normal">Removed the <span style="font-weight: bold;">Edit</span> button for users without rights to change the plan.</li><li class="p_Normal">Clicking on the widget title navigates to the plan view page.</li><li class="p_Normal">Ability to mark tasks as completed and update their completion status.</li></ul>
|
||
<p class="p_Normal">3. TEAM-18911: Updated the Project Plan Item form.</p>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal">Removed the <span style="font-weight: bold;">Object activity stream</span> widget from the plan item to simplify communications.</li><li class="p_Normal">Users can now leave comments exclusively in project tasks of published plans.</li><li class="p_Normal">Migration conducted for a stable transition to the updated system for existing clients.</li></ul>
|
||
<p class="p_Normal">4. TEAM-19941: Added the <span style="font-weight: bold;">Resources</span>, <span style="font-weight: bold;">Resource Groups</span>, and <span style="font-weight: bold;">Workload</span> apps to the <span style="font-weight: bold;">Projects</span> section. On the project plan item edit form, a <span style="font-weight: bold;">Resources</span> table has been added to allow for the reservation of resources for project tasks.</p>
|
||
<p class="p_Normal">5. TEAM-20131: Implemented automatic scrolling to the current date in the Gantt chart widget when opening a project plan. If the current date is not within the range of dates displayed on the timeline, the timeline automatically scrolls either to the beginning or the end of the period, depending on whether the period is before or after the current date.</p>
|
||
<p class="p_Normal">6. TEAM-21101: The performance forecast request form now allows sorting by columns. This feature enables organizing tasks in ascending or descending order, facilitating the management and analysis of a large number of tasks in the calendar plan. The improvement was implemented to simplify working with tables containing many tasks, making the selection process more intuitive and less time-consuming.</p>
|
||
<p class="p_Normal">7. TEAM-22078: Added new fields to the Project plan Item.</p>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal">Added two non-system fields: Expenses (estimate) and Expenses (actual).</li><li class="p_Normal">Fields displayed in the sidebar on all forms of the plan item.</li><li class="p_Normal">Hidden on the view form if not filled.</li></ul>
|
||
<p class="p_Normal">These fields can be used to create and analyze expense charts, improving financial planning and control over the project budget. Examples of charts and additional tools for clients will be available through the BRIX Store.</p>
|
||
<p class="p_Normal">8. TEAM-22155: Implemented the function of automatic adjustment of task dates when copying a project from a template. Now the start and end dates of tasks are adapted according to the project start date, maintaining the original time intervals between tasks. This update simplifies planning by eliminating the need to manually adjust each date in the new project.</p>
|
||
<p class="p_Normal"> </p>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Bugs fixed</span></h2>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="1" class="p_Normal">TEAM-6655: Previously, only one file could be sent for approval in Diadoc, now multiple files can be sent.</li><li value="2" class="p_Normal">TEAM-11074: Fixed an issue with completing tasks created in business processes of custom modules.</li><li value="3" class="p_Normal">TEAM-11566: Fixed an error that prevented opening information tasks.</li><li value="4" class="p_Normal">TEAM-13070: Unified page names in the <span style="font-weight: bold;">Administration</span> workspace for email settings.</li><li value="5" class="p_Normal">TEAM-13130: Restored the ability to add the <span style="font-weight: bold;">Modal window content</span> widget after its deletion.</li><li value="6" class="p_Normal">TEAM-14169: Fixed incorrect display of licenses for external users of business solutions.</li><li value="7" class="p_Normal">TEAM-15720: Fixed the display of the <span style="font-weight: bold;">Contact Sales Rep</span> button in the Google browser.</li><li value="8" class="p_Normal">TEAM-16217: Excluded the selection of variables when using the system process for plan approval.</li><li value="9" class="p_Normal">TEAM-17468: Improved the security of user password storage in AD integration settings using AES encryption.</li><li value="10" class="p_Normal">TEAM-18544: Fixed errors in selecting files from the <span style="font-weight: bold;">Files</span> workspace.</li><li value="11" class="p_Normal">TEAM-19357: Solved the issue with adding a user to a trial version when the phone number is already in use.</li><li value="12" class="p_Normal">TEAM-19412: Fixed an issue with linking live chats to clients, maintaining the link only with the specified copy when writing from email.</li><li value="13" class="p_Normal">TEAM-19714: Fixed synchronization errors of app items with contracts. Previously, items created in source apps were not displayed in the corresponding contracts. Attempts to delete and restore the source led to errors.</li><li value="14" class="p_Normal">TEAM-20144: Fixed an error that prevented the deletion of an email address in live chat settings.</li><li value="15" class="p_Normal">TEAM-20319: Resolved a conflict of forms during import.</li><li value="16" class="p_Normal">TEAM-20438: Fixed the issue with assigning information tasks.</li><li value="17" class="p_Normal">TEAM-20540: Changes in app forms are now updated immediately after saving.</li><li value="18" class="p_Normal">TEAM-20558: Solved the problem with filtering by an App type field when using the “down” key.</li><li value="19" class="p_Normal">TEAM-20583: Fixed an error in deleting widgets in the second column on the main page.</li><li value="20" class="p_Normal">TEAM-20728: Solved the issue with disappearing search fields when reopening filters.</li><li value="21" class="p_Normal">TEAM-20763: Corrected the highlighting error of the source when added through a new app.</li><li value="22" class="p_Normal">TEAM-20764: Fixed an error in navigating through the title on the contract page.</li><li value="23" class="p_Normal">TEAM-20924: Eliminated the "A widget with this code already exists" error when editing the main page.</li><li value="24" class="p_Normal">TEAM-20961 and TEAM-20996: Fixed errors related to the deletion of filters and resetting of user settings after updating a workspace or solution.</li><li value="25" class="p_Normal">TEAM-21006: Resolved an issue with access to information tasks for user groups. The problem was related to the fact that the information or approval object file was deleted after the process started or was inaccessible (insufficient rights). Added process interruption in case of error. Transition conditions are executed if set. These changes only apply to files.</li><li value="26" class="p_Normal">TEAM-21194: Fixed an error with uploading files to app documents.</li><li value="27" class="p_Normal">TEAM-21220: Resolved an error in processes when opening a custom task form.</li><li value="28" class="p_Normal">TEAM-21302: Solved the issue with loading PDF document previews.</li><li value="29" class="p_Normal">TEAM-21433: Corrected a notification in the calendar.</li><li value="30" class="p_Normal">TEAM-21435: Eliminated a problem with sending messages with links in live chats through the WhatsApp messenger.</li><li value="31" class="p_Normal">TEAM-21488: Fixed the escaping of column names in the code when building reports.</li><li value="32" class="p_Normal">TEAM-21496: The 'Restart' function in the process monitor now correctly updates the process version.</li><li value="33" class="p_Normal">TEAM-21588: Resolved an issue where field mandatory conditions did not work with more than two widgets on a form.</li><li value="34" class="p_Normal">TEAM-21633: Fixed inheritance of subordinate rights by a manager.</li><li value="35" class="p_Normal">TEAM-21653: Restored forms and their scripts when restoring a business process version.</li><li value="36" class="p_Normal">TEAM-21738: Corrected the incorrect text "Required field" under the Phone number field type.</li><li value="37" class="p_Normal">TEAM-21780: Added an error notification when inviting a user with an already used email.</li><li value="38" class="p_Normal">TEAM-21837: Corrected the incorrect response when an HTTP method implementation is missing in API methods.</li><li value="39" class="p_Normal">TEAM-21907: Added the ability to request a code for incorrect phone number entries.</li><li value="40" class="p_Normal">TEAM-21915: Fixed the issue of deleting phone numbers when registering a portal user.</li><li value="41" class="p_Normal">TEAM-21919: Solved the problem with viewing all active users.</li><li value="42" class="p_Normal">TEAM-21940: Corrected a search file error with symbols ( ) in search parameters by name.</li><li value="43" class="p_Normal">TEAM-10967: Filtering an app through <code><b>setFilter</b></code> in a table now works correctly.</li><li value="44" class="p_Normal">TEAM-22033: Fixed an error that prevented the process monitor page from opening in full-screen mode.</li><li value="45" class="p_Normal">TEAM-22093: Resolved the 'need logout' error when downloading file versions.</li><li value="46" class="p_Normal">TEAM-22116: Fixed an export error of the portal during configuration export.</li><li value="47" class="p_Normal">TEAM-22149: Resolved an error in the Chart widget when selecting a measurement with a nested property of the app.</li><li value="48" class="p_Normal">TEAM-22157: Fixed an issue where the task name was displayed as the process name.</li><li value="49" class="p_Normal">TEAM-22240: Improved the portal export mechanism. Now, portals that are disabled are excluded from the export package. Enhanced the process of checking the portal status before including it in the export to ensure accuracy and currency of data in the manifest.</li><li value="50" class="p_Normal">TEAM-22315: The <code><b>System.directories.getFiles()</b></code> method now returns an empty set if there are no files in the directory.</li><li value="51" class="p_Normal">TEAM-22318: Added a dependency check on reports when exporting a page.</li><li value="52" class="p_Normal">TEAM-22328: Added an option to configure notifications of new tasks created in the process in the Create and Edit App Item blocks. This feature is relevant when a manual method is selected for working with the block.</li><li value="53" class="p_Normal">TEAM-22340: Improved the search for app items by the Money field type.</li><li value="54" class="p_Normal">TEAM-22386: Solved the problem of only loading the first 50 contracts when displayed as tiles.</li><li value="55" class="p_Normal">TEAM-22404: Corrected the <code><b>onInit</b></code> function after editing an element.</li><li value="56" class="p_Normal">TEAM-22428: Fixed an error in the Arbitrary app field property. Inconsistency was identified in the behavior of the Arbitrary app field when created with a single value. In PostgreSQL for such a field, the property array incorrectly sets to false, whereas for regular app in a similar situation, this property sets to true.</li><li value="57" class="p_Normal">TEAM-22433: The issue with the order of adding items in the Arbitrary app with multiple values was corrected. Now new items are correctly added to the end of the list, providing more intuitive and convenient data management.</li><li value="58" class="p_Normal">TEAM-22480: Eliminated the possibility of editing a process by a second user.</li><li value="59" class="p_Normal">TEAM-22552: Fixed an issue that prevented opening unpublished processes at the company and section level after changing the language.</li><li value="60" class="p_Normal">TEAM-22560: Resolved the issue with displaying the session name in live chats on mobile devices.</li><li value="61" class="p_Normal">TEAM-22561: Fixed an issue with sending messages in live chats on mobile devices.</li><li value="62" class="p_Normal">TEAM-22572: Resolved a problem in linking the Arbitrary app field type with other fields. The fix allows the Arbitrary app field (Field "A") to be correctly linked with a specific app (Field "B"). Now, if field "A" is linked to field "B" and has an "Output" setting, then field "A" will be typed with the value of field "B". This means that when selecting a value for field "A", the user will only have access to the values of field "B".</li><li value="63" class="p_Normal">TEAM-22594: Fixed an error in transferring funnel visibility settings to other companies.</li><li value="64" class="p_Normal">TEAM-22678: Eliminated an internal error (500) when working with the Alytics module.</li><li value="65" class="p_Normal">TEAM-22778: Corrected an export error in the calendar with external participants. The calendar now successfully synchronizes with external calendar apps, including all scheduled events with external participants.</li><li value="66" class="p_Normal">TEAM-22780: Solved the problem of downloading files with Cyrillic names in AWS s3.</li><li value="67" class="p_Normal">TEAM-22781: Fixed an error in processing Money type fields related to incorrect currency display. Implemented checks for creating and editing Money fields in different contexts (apps, processes, parameters, widgets). Specifically checked the case with an empty currency in Money field settings, including editing field metadata in the database. Scripts related to changing currency in field settings and displaying the default currency depending on the company's locale settings were tested.</li><li value="68" class="p_Normal">TEAM-22839: Corrected an error in the <code><b>getPermissions()</b></code> method.</li><li value="69" class="p_Normal">TEAM-22895: In version 2023.9, an error was found in the Project Plan widget, where the timeline was not displayed on app forms on old platforms after a system update, despite the true value set for this option in the form builder. As a result of fixing this error, the functionality of displaying the timeline has been restored, and it now correctly appears on app forms according to settings made in the form builder.</li><li value="70" class="p_Normal">TEAM-22901: Fixed an error in displaying the content of the widget in the navigator.</li><li value="71" class="p_Normal">TEAM-22905: Corrected an error that occurred when attempting to reply to an email into which an image had been pasted using CTRL+V. Previously, attempting to send such an email resulted in an error displayed in the har-logs, making it impossible to send.</li><li value="72" class="p_Normal">TEAM-22945: Resolved a problem with text formatting when communicating with a bot in live chats.</li><li value="73" class="p_Normal">TEAM-22948: The Gantt chart widget now adapts in width when resizing the project view form.</li><li value="74" class="p_Normal">TEAM-22953: The Control field on the Project Plan Item form is displayed correctly.</li><li value="75" class="p_Normal">TEAM-22964: Fixed updating the timeline length in the Gantt Chart widget.</li><li value="76" class="p_Normal">TEAM-23139: Resolved an error when publishing a process with the <span style="font-weight: bold;">Create Package</span> block.</li><li value="77" class="p_Normal">TEAM-23149: Fixed a problem with displaying status and approvers when viewing a document package.</li><li value="78" class="p_Normal">TEAM-23276: Resolved an error in the process of registering external users on the portal when the <code><b>addUserWithoutConfirmation</b></code> function was called for a phone number already existing in the system. Previously, when trying to register such users, a non-informative error "phone-already-exists" occurred, even if the phone field was empty. After the fix, in case of a conflict with OAuth2 data, a clear error with code 409 and text {"code":"oauth2-already-exists"} is now returned. This update simplifies the diagnosis of issues related to user registration and helps system administrators more effectively manage the authentication process.</li><li value="79" class="p_Normal">TEAM-23295: Fixed a bug in editing in the Gantt widget in view mode. Editing fields is no longer available in view mode.</li><li value="80" class="p_Normal">TEAM-23355: Improved access at the level of app items for the User (multiple) app property type</li></ol>
|
||
|
||
<div class="bottom-nav">
|
||
|
||
<a id="prev-link" class="topic__navi_prev" href="2024_4.html">
|
||
<span class="bottom-nav__arrow bottom-nav__arrow--prev"></span> <span
|
||
class="bottom-nav__link">2024_4.html</span>
|
||
</a>
|
||
|
||
|
||
<a id="next-link" class="topic__navi_next" href="2025_3_op.html">
|
||
<span class="bottom-nav__link">2025_3_op.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>
|