koziavin
00717a92fb
All checks were successful
Deploy Static Site / deploy (push) Successful in 6m6s
243 lines
28 KiB
HTML
243 lines
28 KiB
HTML
<!DOCTYPE html>
|
||
<html lang="en">
|
||
|
||
<head>
|
||
<title>Status field</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="With statuses, you can track the current state and progress of an app item." />
|
||
<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>Low-code designer > App builder / Status field</p>
|
||
</div>
|
||
|
||
</div>
|
||
<div class="topic__title"><h1 class="p_Heading1" style="text-align: center; line-height: 1.20; margin: 19px 0 19px 0;"><span class="f_Heading1" style="font-size: 32px;">Status field</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" style="line-height: 1.20; margin: 14px 0 0 0;">With <span style="font-weight: bold;">statuses</span>, you can track the current state and progress of an app item.</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">For example, the <span style="font-weight: bold;">Invoices</span> app can have the following statuses: <span style="font-weight: bold;">Pending approval</span>, <span style="font-weight: bold;">Approved</span>, <span style="font-weight: bold;">Rejected</span>, and <span style="font-weight: bold;">Paid</span>. At any moment you can see where the invoice is in its life-cycle.</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">Users can change statuses <a href="360009920611.html#change_manually" class="topiclink">manually</a> when completing a corresponding task or <a href="360009920611.html#change_automatically" class="topiclink">automatically within a business process</a>.</p>
|
||
<h2 class="p_Heading2" style="line-height: 1.20; margin: 19px 0 0 0;"><span class="f_Heading2" style="font-size: 24px;">Create status</span></h2>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">начало внимание</span></p>
|
||
<p style="line-height: 1.20; margin: 19px 0 0 0;">Only the users included in the <a href="360006871932.html" class="topiclink">Administrators</a> group can create and edit statuses.</p>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">конец внимание</span></p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">This can be done in two ways:</p>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="1" class="p_Normal" style="line-height: 1.20; margin-top: 14px; margin-right: 0; margin-bottom: 0;">Click the gear icon <img alt="app gear icon" width="19" height="20" style="margin:0;width:19px;height:20px;border:none" src="hmfile_hash_f96bd8e3.png"/> next to the app's name and select <span style="font-weight: bold;">Status Field</span>.</li></ol>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;"><img alt="status_field_0" width="584" height="480" style="margin:0;width:584px;height:480px;border:none" src="status_field_0.png"/></p>
|
||
<ol style="list-style-type:decimal" start="2">
|
||
<li value="2" class="p_Normal" style="line-height: 1.20; margin-top: 14px; margin-right: 0; margin-bottom: 0;">If you have created a business process at the app level, open the process designer and click the <span style="font-weight: bold;">Statuses</span> tab.</li></ol>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">The statuses configured from the app page and in the business process designer are linked. If you make changes in the designer, they are reflected in the status settings of the app where the process was created, and vice versa.</p>
|
||
<p class="p_Normal">The <span style="font-weight: bold;">Configure App Status</span> page opens.</p>
|
||
<ol style="list-style-type:decimal" start="3">
|
||
<li value="3" class="p_Normal">On the opened page, enable the <span style="font-weight: bold;">Add Status</span> field option.</li><li value="4" class="p_Normal">In the Status field enter a name and to the right of it click the <span style="font-weight: bold;">Add</span> button or press <span style="font-weight: bold;">Enter</span> on your keyboard.<br />
|
||
<img alt="status_field_01" width="731" height="331" style="margin:0;width:731px;height:331px;border:none" src="status_field_01.png"/></li><li value="5" class="p_Normal">The status will be added to the list with a special code that is used for working with <a href="https://brix365.com/en/help/360009921431.html" target="_blank" class="weblink">API</a>. You can edit the value in the <span style="font-weight: bold;">Code</span> field to refer to the status in scripts more easily.</li><li value="6" class="p_Normal">Create the rest of the statuses for this app by naming them and clicking <span style="font-weight: bold;">Add</span>.</li></ol>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;"><img alt="status_field_02" width="757" height="570" style="margin:0;width:757px;height:570px;border:none" src="status_field_02.png"/></p>
|
||
<p class="p_Normal"><span style="font-size: 15px; color: #394149;">The </span><span style="font-size: 15px; color: #394149;"><a href="360025745312.html" class="topiclink">Kanban board</a> will show the statuses in the same order as they are added to the list. </span><span style="font-size: 15px; color: #394149;">The first status listed will be assigned to all new items.</span></p>
|
||
<ol style="list-style-type:decimal" start="7">
|
||
<li value="7" class="p_Normal" style="line-height: 1.20; margin-top: 14px; margin-right: 0; margin-bottom: 0;">Check the <span style="font-weight: bold;">Final</span> option next to the final statuses in the app item lifecycle. A final status cannot be changed to the next status in line </li><li value="8" class="p_Normal" style="line-height: 1.20; margin-top: 14px; margin-right: 0; margin-bottom: 0;"><a id="hide_status" class="hmanchor"></a>For final statuses, you can check the <span style="font-weight: bold;">Hide</span> box. Enable it to prevent items with this status from being displayed on the Kanban board. You can find the hidden items by selecting the status in <a href="360009669952.html" class="topiclink">advanced search</a> parameters.</li></ol>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;"><img alt="status_field_03" width="579" height="519" style="margin:0;width:579px;height:519px;border:none" src="status_field_03.png"/></p>
|
||
<h2 class="p_Heading2" style="line-height: 1.20; margin: 19px 0 0 0;"><span class="f_Heading2" style="font-size: 24px;">Edit and delete status</span></h2>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 19px 0 0 0;">To change the name and the code of a status, click on the field that you want to edit and make the necessary changes. Also, you can check and uncheck the <span style="font-weight: bold;">Final</span> box at any moment<span style="font-weight: bold;">.</span></p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">Drag and drop the statuses to rearrange them in the list.</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;"><img alt="status_field_04" width="724" height="570" style="margin:0;width:724px;height:570px;border:none" src="status_field_04.png"/></p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 19px 0 0 0;">If you want to delete a status, click the recycle bin icon <img alt="trash" width="18" height="21" style="margin:0;width:18px;height:21px;border:none" src="trash.png"/> on the right-hand side of the status field and confirm it.</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;"> </p>
|
||
<h2 class="p_Heading2" style="line-height: 1.20; margin: 19px 0 0 0;"><span class="f_Heading2" style="font-size: 24px;">Status options</span></h2>
|
||
<p style="line-height: 1.20; margin: 19px 0 0 0;"><span style="font-size: 15px; color: #394149;">On the status configuration page, you can enable additional options for changing and tracking statuses:</span></p>
|
||
<ul style="list-style-type:disc">
|
||
<li style="line-height: 1.20; margin-top: 19px; margin-right: 0; margin-bottom: 0;"><span style="font-size: 15px; font-weight: bold; color: #394149;">Keep change history</span><span style="font-size: 15px; color: #394149;">. If the option is enabled, data about changes in the status of app items is recorded in the system. You can access this information in scripts using the </span><code><b>statusHistory()</b></code><span style="font-size: 15px; color: #394149;"> method. For example, to display in a widget the items that received a certain status during the last day. Read more in <a href="https://tssdk.brix365.com/en/latest/interfaces/_03_globals_.application.html#statushistory" target="_blank" class="weblink">BRIX TS SDK</a>.</span></li><li style="line-height: 1.20; margin-top: 19px; margin-right: 0; margin-bottom: 0;"><span style="font-size: 15px; font-weight: bold; color: #394149;">Save the date that the status was changed on</span><span style="font-size: 15px; color: #394149;">. The date and time of the item status change will be written to a system field in the </span><span style="font-size: 15px; font-weight: bold; color: #394149;">Date the status was changed</span><span style="font-size: 15px; color: #394149;"> app context. You can display the field on the item form or on its page on the Kanban board. You can use the field to keep track of items that are at a certain stage of work for a long time.</span></li><li style="line-height: 1.20; margin-top: 19px; margin-right: 0; margin-bottom: 0;"><span style="font-size: 15px; font-weight: bold; color: #394149;">Change status manually</span><span style="font-size: 15px; color: #394149;">. Users will be able to change the status of an item on its page or by moving it on the Kanban board.</span></li></ul>
|
||
<p style="line-height: 1.20; margin: 19px 0 0 0;"><span style="font-size: 13px; color: #000000;"> </span></p>
|
||
<h2 class="p_Heading2" style="line-height: 1.20; margin: 19px 0 0 0;"><a id="change_manually" class="hmanchor"></a><span class="f_Heading2" style="font-size: 24px;">Set up manual change of a status</span></h2>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 19px 0 0 0;">To allow users to manually change statuses on the <a href="360016427291.html#element_page" class="topiclink">item page,</a> follow these steps:</p>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="1" class="p_Normal" style="line-height: 1.20; margin-top: 19px; margin-right: 0; margin-bottom: 0;">On the status settings page, enable the <span style="font-weight: bold;">Change status manually</span> option.</li><li value="2" class="p_Normal" style="line-height: 1.20; margin-top: 19px; margin-right: 0; margin-bottom: 0;">The <span style="font-weight: bold;">Transitions</span> column will appear in the table with statuses. In it, the sequence of status changes is defined for each status, except for the final ones.</li><li value="3" class="p_Normal" style="line-height: 1.20; margin-top: 19px; margin-right: 0; margin-bottom: 0;">The default value for all statuses is <span style="font-weight: bold;">Next</span>. Click on it if you want to select a different option.</li></ol>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 19px 0 0 0;"><img alt="status_field_05" width="756" height="587" style="margin:0;width:756px;height:587px;border:none" src="status_field_05.png"/></p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;"> </p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;"><a id="next-status" class="hmanchor"></a><span style="font-weight: bold;">Any. </span>Users will be able to select any status from the list when changing the current one.</p>
|
||
<ul style="list-style-type:disc">
|
||
<li style="line-height: 1.20;"><span style="font-weight: bold;">Next.</span> Users will be able to change the current status to the one that stands next in the list. Drag and drop the statuses in the list to define the desired order.</li><li style="line-height: 1.20;"><span style="font-weight: bold;">Select Status.</span>Select the option and check the statuses that will be available to users when the current one is changed.</li></ul>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">For statuses marked as final, you cannot configure the change order.</p>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Ways to manually change item status</span></h2>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="1" class="p_Normal" style="line-height: 1.20; margin-top: 14px; margin-right: 0; margin-bottom: 0;">Change the status from the page using the <a href="app_element_status.html" class="topiclink">App item status</a> widget.</li></ol>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">The widget is added to the app view form automatically when the manual status change option is enabled. To change the current status, open the item page. In the sidebar, click <span style="font-weight: bold;">Change</span> and select an available status from the list.</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;"><a id="change_automatically" class="hmanchor"></a><img alt="sf 9" width="877" height="474" style="margin:0;width:877px;height:474px;border:none" src="hmfile_hash_9955ff3c.png"/></p>
|
||
<ol style="list-style-type:decimal" start="2">
|
||
<li value="2" class="p_Normal" style="line-height: 1.20; margin-top: 14px; margin-right: 0; margin-bottom: 0;">Change the status by dragging and dropping items on the Kanban board.</li></ol>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">Go to the app page and enable the display of items as a <a href="360009923311.html#kanban_board" class="topiclink">Kanban board</a> Drag and drop an item to the desired status on the board. The statuses can be assigned according to the transition settings set for each status.</p>
|
||
<ol style="list-style-type:decimal" start="3">
|
||
<li value="3" class="p_Normal" style="line-height: 1.20; margin-top: 14px; margin-right: 0; margin-bottom: 0;">Add a <span style="font-weight: bold;">Change status</span> button to the form.</li></ol>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">Open the page of any app item, click on the gear icon in the bottom left corner, and add a <span style="font-weight: bold;">Change status</span> button. To learn more about configuring the button, read <a href="360019228531.html#create-button" class="topiclink">Manage buttons on app item pages</a>.</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">To change status using the button, you don't need to enable the option to manually change status in the app. Using the <span style="font-weight: bold;">Change Status</span> button does not require you to enable <a href="360009920611.html#change_manually" class="topiclink">manual change of statuses</a>..</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">Users can click the button, select any of the app statuses, and leave a comment, which will be displayed in the activity stream on the item sidebar. </p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;"><img alt="sf 10" width="933" height="518" style="margin:0;width:933px;height:518px;border:none" src="hmfile_hash_1c48c89d.png"/></p>
|
||
<h2 class="p_Heading2" style="line-height: 1.20; margin: 19px 0 0 0;"><span class="f_Heading2" style="font-size: 24px;">Change status in a business process</span></h2>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 19px 0 0 0;">Statuses can change automatically during the execution of a business process. Depending on what stage the process is in, the app item gets one or another status. This is done by means of the <a href="360012263332.html" class="topiclink">Manage status</a><span style="font-weight: bold;"> </span>element. </p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">For example, when the accountant pays an invoice in the <span style="font-weight: bold;">Invoice Approval</span> process, the status of the invoice item automatically changes from <span style="font-weight: bold;">Approved</span> to <span style="font-weight: bold;">Paid</span>. </p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;"><img alt="Status_09.PNG" title="Status_09.PNG" width="725" height="597" style="margin:0;width:725px;height:597px;border:none" src="360019505012-status_09.png"/></p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">The new status is displayed in the app on the <a href="360016427291.html#element_page" class="topiclink">item page</a>.</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;"> </p>
|
||
|
||
<div class="bottom-nav">
|
||
|
||
<a id="prev-link" class="topic__navi_prev" href="work-with-folder-tree.html">
|
||
<span class="bottom-nav__arrow bottom-nav__arrow--prev"></span> <span
|
||
class="bottom-nav__link">work-with-folder-tree.html</span>
|
||
</a>
|
||
|
||
|
||
<a id="next-link" class="topic__navi_next" href="360009921131.html">
|
||
<span class="bottom-nav__link">360009921131.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>
|