224 lines
23 KiB
HTML
224 lines
23 KiB
HTML
<!DOCTYPE html>
|
||
<html lang="en">
|
||
|
||
<head>
|
||
<title>Manage Status</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="The Manage Status activity is used only in the business processes that involve apps with customized statuses. It allows you to track the process progress and also determines..." />
|
||
<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>Business process designer > Graphical elements / Manage Status</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;">Manage Status</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;"><img alt="manage_status" width="106" height="88" style="float:left;margin:0;width:106px;height:88px;border:none" src="manage_status.png"/><span class="f_ImageCaption"> </span>The <span style="font-weight: bold;">Manage Status</span> activity is used only in the business processes that involve <a href="360006963072.html" class="topiclink">apps</a> with customized <a href="360009920611.html" class="topiclink">statuses</a>. It allows you to track the process progress and also determines the status of one or several app items at a particular stage of the process.</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">For example, you can create an <span style="font-weight: bold;">Contracts</span> app and set up an <a href="360009921131.html" class="topiclink">associated business process</a> for document approval. By setting up statuses, you can track at what stage of the document life-cycle an contract currently is. As the process progresses, the contract will automatically acquire different statuses: <span style="font-weight: bold;">Approved</span>, <span style="font-weight: bold;">Signed</span>, <span style="font-weight: bold;">Rejected</span>, etc, providing clear information on how the work is being done.</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">You can also use the block to change the status of several app items, for example, if a manager approves a number of similar agreements in a task.</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;"><img alt="00.PNG" title="00.PNG" width="582" height="427" style="margin:0;width:582px;height:427px;border:none" src="360009277400-00.png"/></p>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Create statuses for the app</span></h2>
|
||
<p class="p_Normal">To customize a block, first define the statuses. You can do this in one of the following ways:</p>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Heading2" style="line-height: 1.20; margin-top: 19px; margin-right: 0; margin-bottom: 0;">In the <a href="360009920611.html" class="topiclink">app settings</a>.</li><li class="p_Normal">In the graphic process designer on the <a href="status-tab.html" class="topiclink">Statuses</a> tab.</li></ul>
|
||
<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;">The <span style="font-weight: bold;">Statuses</span> tab is only available in business processes <a href="360009921131.html" class="topiclink">associated with an app</a>. In global company and workspace processes, this tab is unavailable.</p>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">конец внимание</span></p>
|
||
<h2 class="p_Heading2" style="line-height: 1.20; margin: 19px 0 0 0;"><span class="f_Heading2" style="font-size: 24px;">Set up the Manage Status activity </span></h2>
|
||
<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;">Open the process page and in the toolbar on the right, click the <span style="font-weight: bold;">System Elements</span> tab. </li><li value="2" class="p_Normal" style="line-height: 1.20; margin-top: 19px; margin-right: 0; margin-bottom: 0;">Drag the <span style="font-weight: bold;">Manage Status</span> block onto the diagram and place it where you want to change the status.<br />
|
||
<img alt="Manage3" width="787" height="407" style="margin:0;width:787px;height:407px;border:none" src="manage3.png"/></li></ol>
|
||
<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;">Double-click on the block in the diagram. In the window that opens, specify:<br />
|
||
<img alt="ms4" width="631" height="398" style="margin:0;width:631px;height:398px;border:none" src="ms4.png"/></li></ol>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal" style="line-height: 1.20; margin-top: 14px; margin-right: 0; margin-bottom: 0;"><span style="font-weight: bold;">Name</span><span style="font-weight: bold; color: #ff0000;">*</span>. Enter the name of the block to be displayed on the process diagram.</li><li class="p_Normal" style="line-height: 1.20; margin-top: 14px; margin-right: 0; margin-bottom: 0;"><span style="font-weight: bold;">Variable</span><span style="font-weight: bold; color: #ff0000;">*</span>. Specify the variable to which the items for status change are written.<br />
|
||
<br />
|
||
If the process is associated with an app, the <span style="font-weight: bold;">Variable</span> field will already contain the <a href="process_context.html" class="topiclink">context variable</a> representing the app. To edit it, click <span style="font-weight: bold;">Change variable settings</span>. For example, in the window that opens, you can select the <span style="font-weight: bold;">Many</span> subtype when you are customizing a block to change the status of multiple items of the same app in bulk.<br />
|
||
<br />
|
||
If the variable is not set in the process context, click <span style="font-weight: bold;">Create new variable</span>.</li><li class="p_Normal" style="line-height: 1.20; margin-top: 14px; margin-right: 0; margin-bottom: 0;"><span style="font-weight: bold;">Set status</span><span style="font-weight: bold; color: #ff0000;">*</span>. Select a value to assign to the items from the variable, and click <span style="font-weight: bold;">Save</span>.<br />
|
||
<br />
|
||
If you are setting up status change for the <a href="360012693999.html" class="topiclink">Deals</a> app, an additional <span style="font-weight: bold;">Reason for rejection</span> field will appear if the <span style="font-weight: bold;">Lost</span> status is selected. </li></ul>
|
||
<h2 class="p_Heading2" style="line-height: 1.20; margin: 19px 0 0 0;"><span class="f_Heading2" style="font-size: 24px;">Changing statuses of two or more apps in one process</span></h2>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 19px 0 0 0;">Sometimes you will use several apps in one process. The approval process mentioned above describes the stages of approving a contract. <span style="font-weight: bold;">Contracts</span> belong to the <span style="font-weight: bold;">Order Management</span> workspace, which may also store other apps, for instance, <span style="font-weight: bold;">Customers</span>, <span style="font-weight: bold;">Orders</span>, <span style="font-weight: bold;">Claims</span>. Each of these apps might have its own <a href="360009920611.html" class="topiclink">set of statuses</a>.</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;"><img alt="ms5" width="888" height="345" style="margin:0;width:888px;height:345px;border:none" src="ms5.png"/></p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">When the contract’s status changes, it seems reasonable to change the contractor’s status, too. For example, once the contract is signed, the contractor’s status can change from <span style="font-weight: bold;">Contract approval</span> to <span style="font-weight: bold;">Order</span> <span style="font-weight: bold;">fulfillment</span>.</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">This way, both of these apps will be included in one process, and the statuses of both apps will change as the process progresses.</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">Here is how you can set this up:</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;"> </p>
|
||
<ol style="list-style-type:upper-roman">
|
||
<li value="1" style="line-height: 1.20;">In process designer, go to the <span style="font-weight: bold;">Context</span> tab. <a href="process_context.html#add_new_variable" class="topiclink">Add a new variable</a> to represent the Contractoror app.</li></ol>
|
||
<p style="line-height: 1.20;"><img alt="ms6" width="885" height="402" style="margin:0;width:885px;height:402px;border:none" src="ms6.png"/></p>
|
||
<ol style="list-style-type:upper-roman">
|
||
<li value="2" style="line-height: 1.20;">Place new <span style="font-weight: bold;">Manage status</span> elements where necessary, for instance, before and after the <span style="font-weight: bold;">Sign the contract</span> task.</li></ol>
|
||
<p style="line-height: 1.20;"><img alt="07.PNG" title="07.PNG" width="581" height="465" style="margin:0;width:581px;height:465px;border:none" src="360009279020-07.png"/></p>
|
||
<ol style="list-style-type:upper-roman">
|
||
<li value="3" style="line-height: 1.20;">Double-click on the element to open its settings. In the <span style="font-weight: bold;">Variable</span> field, select Contractor. In the drop-down list select the required status and click <span style="font-weight: bold;">Save</span>.</li></ol>
|
||
<p style="line-height: 1.20;"><img alt="ms 7" width="703" height="300" style="margin:0;width:703px;height:300px;border:none" src="hmfile_hash_86917ef3.png"/></p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">Now you only have to decide how the <span style="font-weight: bold;">Contractors</span> variable added on step 1 shall be filled in.</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">You can place the variable on a <a href="360012495611.html#form" class="topiclink">task form</a>. In this case, the employee performing this task will be asked to select a specific contractor on the task form. </p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">Sometimes users specify the contractor directly in the contract when adding a new <a href="360016427291.html" class="topiclink">app item</a>. In this case, the contractor’s details shall be sent from the <span style="font-weight: bold;">Contracts</span> app to the variable created in step 1. To do that, use the <a href="360020300571.html" class="topiclink">Assign value</a> activity. </p>
|
||
|
||
<div class="bottom-nav">
|
||
|
||
<a id="prev-link" class="topic__navi_prev" href="360027203731.html">
|
||
<span class="bottom-nav__arrow bottom-nav__arrow--prev"></span> <span
|
||
class="bottom-nav__link">360027203731.html</span>
|
||
</a>
|
||
|
||
|
||
<a id="next-link" class="topic__navi_next" href="360012495911.html">
|
||
<span class="bottom-nav__link">360012495911.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>
|