205 lines
21 KiB
HTML
205 lines
21 KiB
HTML
<!DOCTYPE html>
|
||
<html lang="en">
|
||
|
||
<head>
|
||
<title>Send document for information use case</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="Let’s look at how to configure the process of the sales plan review." />
|
||
<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 > <a href="360010385600.html">Send Document/App Item</a> / Send document for information use case</p>
|
||
</div>
|
||
|
||
</div>
|
||
<div class="topic__title"><h1 class="p_Heading1"><span class="f_Heading1">Send document for information use case</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 style="text-align: justify; line-height: 1.20; margin: 0 0 11px 0;">Let’s look at how to configure the process of the sales plan review.</p>
|
||
<p style="text-align: justify; line-height: 1.20; margin: 0 0 11px 0;"><img alt="send-document-item-01" width="1313" height="703" style="margin:0;width:1313px;height:703px;border:none" src="send-document-item-01.png"/></p>
|
||
<p style="text-align: justify; line-height: 1.20; margin: 0 0 11px 0;">It includes the following steps:</p>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="1" style="text-align: justify; line-height: 1.20; margin-top: 0; margin-right: 0; margin-bottom: 11px;">The CFO, who is the initiator of the process, develops a sales plan and sends it to the CEO for approval.</li><li value="2" style="text-align: justify; line-height: 1.20; margin-top: 0; margin-right: 0; margin-bottom: 11px;">The CEO reads the plan and either approves it or sends it back for correction.</li><li value="3" style="text-align: justify; line-height: 1.20; margin-top: 0; margin-right: 0; margin-bottom: 11px;">If the plan is not approved, the CFO is tasked with finalizing the document. The plan is then sent for approval again.</li><li value="4" style="text-align: justify; line-height: 1.20; margin-top: 0; margin-right: 0; margin-bottom: 11px;">Once the plan is approved, it is sent to all sales reps for review. A list of informed users is generated, and each sales rep confirms that they have been informed about the content of the document. At the same time, the employee may leave a comment.</li><li value="5" style="text-align: justify; line-height: 1.20; margin-top: 0; margin-right: 0; margin-bottom: 11px;">If the sales plan has been changed by the time of review, the CFO should verify it. The plan is then sent back for approval and review.</li><li value="6" style="text-align: justify; line-height: 1.20; margin-top: 0; margin-right: 0; margin-bottom: 11px;">If the sales reps do not confirm that they have been informed about the plan within the set deadline, the CFO is assigned the task of monitoring the review. They can re-send the plan for review with a new deadline or deliver the information to the employees in person. In the second case, a corresponding message is added to the activity stream of the sales plan, and the list of informed users will have the <span style="font-weight: bold;">Canceled</span> status.</li><li value="7" style="text-align: justify; line-height: 1.20; margin-top: 0; margin-right: 0; margin-bottom: 11px;"> Error handling is configured for the information step. If an error appears, the system supervisor is assigned with a task to handle the error and resume the process.</li></ol>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Configure the review activity</span></h2>
|
||
<p style="text-align: justify; line-height: 1.20; margin: 0 0 11px 0;">Let’s see how to set up a review in the described process:</p>
|
||
<ol style="list-style-type:upper-roman">
|
||
<li value="1" style="text-align: justify; line-height: 1.20; margin-top: 0; margin-right: 0; margin-bottom: 11px;">Open the settings of the <span style="font-weight: bold;">Review sales plan</span> activity and go to the <span style="color: #0000ff;"><a href="360010385600.html#transitions-tab" class="topiclink">Connectors</a></span> tab. Outgoing connectors added for the activity are displayed here.</li></ol>
|
||
<p style="text-align: justify; line-height: 1.20; margin: 0 0 11px 34px;"><img alt="send-document-item-case-02" width="910" height="523" style="margin:0;width:910px;height:523px;border:none" src="send-document-item-case-02.png"/></p>
|
||
<ol style="list-style-type:upper-roman">
|
||
<li value="2" style="text-align: justify; line-height: 1.20; margin-top: 0; margin-right: 0; margin-bottom: 11px;">Mark <span style="font-weight: bold;">Informed</span> as the default connector. Once all sales reps have reviewed the document, the process will be completed and the list of informed users will have the Informed status.</li><li value="3" style="text-align: justify; line-height: 1.20; margin-top: 0; margin-right: 0; margin-bottom: 11px;">Set up the connector that will be used if the plan sent for review is edited. To do this, click on the <span style="font-weight: bold;">Plan changed</span> connector and open the <span style="font-weight: bold;">Conditions</span> tab. Set the condition under which the connector will be activated and save the settings.</li></ol>
|
||
<p style="text-align: justify; line-height: 1.20; margin: 0 0 11px 34px;"><img alt="send-for-information-use-case-3" width="659" height="292" style="margin:0;width:659px;height:292px;border:none" src="send-for-information-use-case-3.png"/></p>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">начало внимание</span></p>
|
||
<p class="p_Normal">To use the <span style="font-weight: bold;">Archived</span> option, you must set the <a href="approval-settings.html" class="topiclink">rules for archiving lists of informed users</a> in the app settings.</p>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">конец внимание</span></p>
|
||
<ol style="list-style-type:upper-roman">
|
||
<li value="4" style="text-align: justify; line-height: 1.20; margin-top: 0; margin-right: 0; margin-bottom: 11px;">Set up the <span style="font-weight: bold;">Deadline violated</span> connector. If not all sales reps review the document within the set time, the Commercial Director will be assigned a monitoring task.</li></ol>
|
||
<p style="text-align: justify; line-height: 1.20; margin: 0 0 11px 34px;">To limit the task time frame, go to the <a href="360010385600.html#interrupt" class="topiclink">Deadline</a> tab. Enable the <span style="font-weight: bold;">Set deadline for the task</span> option, set the time, and in the <span style="font-weight: bold;">Interrupt</span> field, select the <span style="font-weight: bold;">Deadline violated</span> connector.</p>
|
||
<ol style="list-style-type:upper-roman">
|
||
<li value="5" style="text-align: justify; line-height: 1.20; margin-top: 0; margin-right: 0; margin-bottom: 11px;">Set up the connector for error handling, so that the process takes this path if there is an error in the <span style="font-weight: bold;">Send Document/App item</span> block. In the example above, in case of such an error, a task is assigned to the system supervisor to correct the error and resume the process. Go to the <span style="font-weight: bold;">Error Handling</span> tab and enable the <span style="font-weight: bold;">Interrupt</span> option. Then select the configured <span style="font-weight: bold;">Handle the error</span> connector.</li><li value="6" style="text-align: justify; line-height: 1.20; margin-top: 0; margin-right: 0; margin-bottom: 11px;">Add the <span style="font-weight: bold;">Comment left</span> custom status so that the sales rep can draw executives’ attention to their comment when reviewing. The status will be displayed in the review task as a button. If an employee clicks it, their comment will be marked with a color in the list. This choice does not affect the process or the final status of the review.</li></ol>
|
||
<p style="text-align: justify; line-height: 1.20; margin: 0 0 11px 34px;">To configure it, go to the <span style="color: #0000ff;"><a href="360010385600.html#custom-statuses-tab" class="topiclink">Custom Statuses</a></span> tab. Enable the use of the optional status and set the text that will be displayed on the button in the sales rep’s task and the list of informed users.</p>
|
||
<p style="text-align: justify; line-height: 1.20; margin: 0 0 11px 34px;"><img alt="send-for-information-use-case-4" width="877" height="371" style="margin:0;width:877px;height:371px;border:none" src="send-for-information-use-case-4.png"/></p>
|
||
<p style="text-align: justify; line-height: 1.20; margin: 0 0 11px 34px;">If a sales rep clicks the <span style="font-weight: bold;">Leave comment</span> button when performing a task, the corresponding text will be displayed in the list.</p>
|
||
<p style="text-align: justify; line-height: 1.20; margin: 0 0 11px 34px;"><img alt="send-for-information-use-case-5" width="386" height="224" style="margin:0;width:386px;height:224px;border:none" src="send-for-information-use-case-5.png"/></p>
|
||
<p style="text-align: justify; line-height: 1.20; margin: 0 0 11px 0;">Once you have configured the settings, save and publish the process.</p>
|
||
|
||
<div class="bottom-nav">
|
||
|
||
<a id="prev-link" class="topic__navi_prev" href="360010385600.html">
|
||
<span class="bottom-nav__arrow bottom-nav__arrow--prev"></span> <span
|
||
class="bottom-nav__link">360010385600.html</span>
|
||
</a>
|
||
|
||
|
||
<a id="next-link" class="topic__navi_next" href="360010366380.html">
|
||
<span class="bottom-nav__link">360010366380.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>
|