All checks were successful
Deploy Static Site / deploy (push) Successful in 6m6s
278 lines
45 KiB
HTML
278 lines
45 KiB
HTML
<!DOCTYPE html>
|
||
<html lang="en">
|
||
|
||
<head>
|
||
<title>Send Document/App Item</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 Send Document/App Item activity is used in a process when its participants need to get informed about the contents of a file, a document, or an app item. The users receive..." />
|
||
<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 / Send Document/App Item</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;">Send Document/App Item</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="send_document1" width="106" height="86" style="float:left;margin:0;width:106px;height:86px;border:none" src="send_document1.png"/>The <span style="font-weight: bold;">Send Document/App Item</span> activity is used in a process when its participants need to <a href="360010245000.html#sendforinformation" class="topiclink">get informed</a> about the contents of a <a href="360014164452.html" class="topiclink">file</a>, a <a href="360009923631.html" class="topiclink">document</a>, or an <a href="360016427291.html" class="topiclink">app item</a>. <span style="font-family: Inter;">The users receive a task containing a link to the object that they have to view or read. After that, a </span><a href="360010385600.html#h_5d6dfa6b-3345-49e7-ac8f-47c604f77f17" class="topiclink">list of informed users</a> <span style="font-family: Inter;">is created on its page. It contains the employee’s decisions, comments, and additional files.</span></p>
|
||
<p style="text-align: justify; line-height: 1.20; margin: 14px 0 0 0;">To learn how to use the activity in a business process, refer to the <span style="color: #0000ff;"><a href="send-for-information-use-case.html" class="topiclink">Send for information use case</a></span> article.</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;"><span style="font-family: Inter;">To open the activity settings, double-click on it on the process diagram. </span>Configure settings on the <span style="color: #0000ff;"><a href="360010385600.html#general-tab" class="topiclink">General</a></span>, <span style="color: #0000ff;"><a href="360010385600.html#form" class="topiclink">Form</a></span>, <span style="color: #0000ff;"><a href="360010385600.html#interrupt" class="topiclink">Deadline</a></span>, <span style="color: #0000ff;"><a href="360010385600.html#schedule-in-calendar" class="topiclink">Schedule in Calendar</a></span>, <span style="color: #0000ff;"><a href="360010385600.html#transitions-tab" class="topiclink">Connectors</a></span>, <span style="color: #0000ff;"><a href="360010385600.html#custom-statuses-tab" class="topiclink">Custom Statuses</a></span>, <span style="color: #0000ff;"><a href="360010385600.html#signature-settings-tab" class="topiclink">Signature</a></span>, and <span style="color: #0000ff;"><a href="360010385600.html#substitutions" class="topiclink">Substitutions</a></span> tabs.</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;">Before configuring the settings, make sure that the <a href="process_context.html" class="topiclink">process context</a> contains a variable for storing the object that the users will have to view or read.</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;"><a id="general-tab" class="hmanchor"></a><span class="f_Heading2" style="font-size: 24px;">General tab</span></h2>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 19px 0 0 0;"><img alt="send-item-brix-01" width="906" height="477" style="margin:0;width:906px;height:477px;border:none" src="send-item-brix-01.png"/></p>
|
||
<ul style="list-style-type:disc">
|
||
<li style="line-height: 1.20;"><span style="font-weight: bold;">Name</span><span style="font-weight: bold; color: #ff0000;">*</span>.<span style="font-weight: bold;"> </span>Enter the text that will be shown on the process diagram.</li><li style="line-height: 1.20;"><span style="font-weight: bold;">Task name</span><span style="font-weight: bold; color: #ff0000;">*</span>. Enter a brief and informative subject. It will be used as the title for the task shown to users in their <a href="360014162972.html" class="topiclink">#Activity stream</a>. To include <a href="process_context.html" class="topiclink">context variables</a> in the subject, click on the <span style="font-weight: bold;">{+}</span> symbol in the right corner of the field. <span style="font-family: Inter;">You can also <a href="360007679591.html#conditions-and-functions" class="topiclink">add conditions and functions</a>, just like for the item name templates. This allows you to generate a more informative name for the task.</span></li><li style="line-height: 1.20;"><span style="font-family: Inter; font-weight: bold;">Items to send</span><span style="font-family: Inter;">.</span><span style="font-family: Inter; font-weight: bold;"> </span><span style="font-family: Inter;">Select the context variable storing the file, document, or app item that you want the users to view or read.</span></li><li style="line-height: 1.20;"><span style="font-family: Inter; font-weight: bold;">Notify the executor</span><span style="font-family: Inter;">. If this option is enabled, the executor will receive a notification in their #Activity stream when the task is assigned.</span></li><li style="line-height: 1.20;"><span style="font-family: Inter; font-weight: bold;">Notification to the activity stream</span><span style="font-family: Inter;">. If this option is enabled, a message about the start of the task will be sent to the object’s activity stream.</span></li><li style="line-height: 1.20;"><span style="font-family: Inter; font-weight: bold;">Message Text</span><span style="font-family: Inter;">. Here you can specify all the information that you want the employees to see. Also, you can use context variables to, for example, add a comment of a process participant. To include a variable, click on the </span><span style="font-family: Inter; font-weight: bold;">{+}</span><span style="font-family: Inter;"> symbol in the right corner of the field. You can also add a condition or a function in the same way as in the </span><span style="font-family: Inter; font-weight: bold;">Task name</span><span style="font-family: Inter; font-weight: bold; color: #ff0000;">*</span><span style="font-family: Inter;"> field.</span></li></ul>
|
||
<h2 class="p_Heading2" style="line-height: 1.20; margin: 19px 0 0 0;"><a id="form" class="hmanchor"></a><span class="f_Heading2" style="font-size: 24px;">Form tab</span></h2>
|
||
<p style="line-height: 1.20; margin: 7px 0 7px 0;">This tab appears if an app item has been sent for review. It allows you to configure your own review form from scratch. If you want to use the <span style="color: #0000ff;"><a href="360010385600.html#h_5d6dfa6b-3345-49e7-ac8f-47c604f77f17" class="topiclink">default form</a></span>, you do not need to change the settings on this tab.</p>
|
||
<p style="line-height: 1.20; margin: 7px 0 7px 0;">To create a form, click <span style="font-weight: bold;">Default</span> and then click <span style="font-weight: bold;">+Create Form</span>.</p>
|
||
<p style="line-height: 1.20; margin: 7px 0 7px 0;">This opens the <span style="color: #0000ff;"><a href="360029250931.html#form_template" class="topiclink">form template</a></span> in the interface designer. Place the widgets and buttons you want on the form. You can apply scripts, set form validation, and so on. Save the settings.</p>
|
||
<p style="line-height: 1.20; margin: 7px 0 7px 0;">To customize the display of the properties of the app item being sent for information, go back to the <span style="font-weight: bold;">Form</span> tab in the activity settings. </p>
|
||
<p style="text-align: justify; line-height: 1.20; margin: 7px 0 7px 0;"><img alt="send-item-brix-02" width="713" height="430" style="margin:0;width:713px;height:430px;border:none" src="send-item-brix-02.png"/></p>
|
||
<p style="line-height: 1.20; margin: 7px 0 7px 0;">Place the required fields on the form or create new ones. Set the settings of their visibility and mandatory filling. These actions are similar to the form settings in the <span style="color: #0000ff;"><a href="360012495611.html" class="topiclink">Task</a></span> element. Please note that these settings are available only for a custom form.</p>
|
||
<h2 class="p_Heading2" style="line-height: 1.20; margin: 19px 0 0 0;"><a id="interrupt" class="hmanchor"></a><span class="f_Heading2" style="font-size: 24px;">Deadline tab</span></h2>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;"><img alt="send-item-brix-03" width="671" height="347" style="margin:0;width:671px;height:347px;border:none" src="send-item-brix-03.png"/></p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 19px 0 0 0;">On this tab, you can configure the due date for the task, as well as determine what happens if the task is not completed at the specified time.</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">There are two ways to set the deadline: </p>
|
||
<ul style="list-style-type:disc">
|
||
<li style="line-height: 1.20;"><span style="font-weight: bold;">Exact Time</span>.<span style="font-weight: bold;"> </span><span style="font-family: Inter;">Specify the number of days, hours, or minutes that the executor has to complete the task. The calculations can be based on the</span> <a href="360004890291.html" class="topiclink">business calendar</a>.</li></ul>
|
||
<ul style="list-style-type:disc">
|
||
<li style="line-height: 1.20;"><span style="font-weight: bold;">Variable</span>. <span style="font-family: Inter;">Sometimes it is important that the user completes the task before a certain date. For example, an employee can specify the exact date before which others need to read the new internal regulations. By this day, all specified users should have read the document. In this case, you can use a</span> <a href="process_context.html" class="topiclink">context variable</a> <span style="font-family: Inter;">of the </span><span style="font-family: Inter; font-weight: bold;">Date/Time</span><span style="font-family: Inter;"> type to determine the deadline for the task.</span></li><li style="line-height: 1.20;"><span style="font-family: Inter; font-weight: bold;">Consider the duration of the work day as a constant</span><span style="font-family: Inter;">. </span>This option is available when the business calendar is taken into account. It allows calculating the task deadline based on the number of working hours per day. The time specified in the business calendar settings in the <span style="font-weight: bold;">Standard work schedule</span> field is used for calculation.</li></ul>
|
||
<p style="line-height: 1.28; margin: 0 0 11px 34px;"><span style="font-family: Inter;">If the task belongs to a swimlane with multiple executors and a variable is used to define the deadline, all the executors will have to complete their tasks by the specified moment. Otherwise, the task will be considered overdue.</span></p>
|
||
<p style="line-height: 1.20; margin: 14px 0 0 0;"><span style="font-family: Inter;">In the </span><span style="font-family: Inter; font-weight: bold;">Notification </span><span style="font-family: Inter;">field, you can select users who will be notified if the executor fails to complete the task on time. You can select the current user, a context variable (for example, the process initiator), a user group, or an org chart item.</span></p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;"><img alt="sdai 4" width="743" height="251" style="margin:0;width:743px;height:251px;border:none" src="hmfile_hash_95ae5ae4.png"/></p>
|
||
<p style="line-height: 1.28; margin: 0 0 11px 0;"><span style="font-family: Inter;">By default, a message will be sent to all employees specified in the</span> <a href="360012263032.html" class="topiclink">swimlane</a> <span style="font-family: Inter;">settings. To select other recipients, click the </span><span style="font-family: Inter; font-weight: bold;">Add</span><span style="font-family: Inter;"> button.</span></p>
|
||
<ul style="list-style-type:disc">
|
||
<li style="line-height: 1.20;"><span style="font-family: Inter; font-weight: bold;">Current User</span><span style="font-family: Inter;">. Executor of the swimlane where the activity is placed.</span></li><li style="line-height: 1.20;"><span style="font-family: Inter; font-weight: bold;">Context variable</span><span style="font-family: Inter;">. The recipient is specified in a</span> <a href="process_context.html" class="topiclink">process context</a> variable of the <span style="font-weight: bold;">User</span> type.</li><li style="line-height: 1.20;"><span style="font-weight: bold;">Group</span>. <span style="font-family: Inter;">The message will be sent to a specific</span> <a href="360007146071.html" class="topiclink">user group</a>.</li><li style="line-height: 1.20;"><span style="font-weight: bold;">Org Chart Item</span>. <span style="font-family: Inter;">You can specify the recipient using an</span> <a href="360003861992.html" class="topiclink">org chart</a> item. </li></ul>
|
||
<p style="line-height: 1.20;"><span style="font-size: 13px; color: #000000;"> </span></p>
|
||
<p style="line-height: 1.20; margin: 7px 0 16px 0;"><span style="font-family: Inter;">In the </span><span style="font-family: Inter; font-weight: bold;">Interrupt</span><span style="font-family: Inter;"> field, determine what the next step in the process will be if the executor does not have time to complete the task before the specified time.</span></p>
|
||
<p style="line-height: 1.28; margin: 0 0 11px 0;"><span style="font-family: Inter;">BRIX will automatically select the specified connector if the set time expires and the executor does not confirm that the task has been completed. On the process diagram, such a connector is marked with a clock icon.</span></p>
|
||
<h2 class="p_Heading2"><a id="schedule-in-calendar" class="hmanchor"></a><span class="f_Heading2">Schedule in Calendar tab</span></h2>
|
||
<p class="p_Normal"><img alt="send-item-brix-04" width="753" height="353" style="margin:0;width:753px;height:353px;border:none" src="send-item-brix-04.png"/></p>
|
||
<p class="p_Normal">This tab appears if the task has a deadline. Here you can enable the task to be displayed in the executor's calendar.</p>
|
||
<p class="p_Normal">To avoid cluttering the calendar, you can schedule the task only on specific days. For example, if the review period is three days, you can choose to display the task in the calendar only on the last day. To do this:</p>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="1" class="p_Normal">Add <span style="font-weight: bold;">Date/Time</span> type variables to the context, which will store the values for the task deadlines in the calendar.</li><li value="2" class="p_Normal">Before the <span style="font-weight: bold;">Send document/App item</span> activity in the process diagram, place a <a href="360027203731.html" class="topiclink">script</a> that calculates the values of these variables.</li><li value="3" class="p_Normal">On the current tab, link the<span style="font-weight: bold;"> Start date</span> and <span style="font-weight: bold;">End date</span> fields to these variables.</li></ol>
|
||
<h2 class="p_Heading2"><a id="transitions-tab" class="hmanchor"></a><span class="f_Heading2">Connectors tab</span></h2>
|
||
<p>This tab is used to configure outgoing <a href="360015835331.html" class="topiclink">connectors</a>.</p>
|
||
<p>The main connector, where the process will continue after the user is informed, needs to be marked as the default one.</p>
|
||
<p>You can also add error-handling connectors to the process diagram. Their settings specify the conditions under which the process will automatically continue along the corresponding branches. For example, an additional connector can be used when a file sent for review has been deleted, a new version of the document has been added, or the user does not have permissions to view it. If the condition is met, the process will go down this path, and the <span style="font-weight: bold;">Rejected </span>status will be written to the file page or item page.</p>
|
||
<p class="p_Normal"><img alt="send-item-brix-05" width="729" height="375" style="margin:0;width:729px;height:375px;border:none" src="send-item-brix-05.png"/></p>
|
||
<p>Please note that if an <a href="360010385600.html#interrupt" class="topiclink">escalation connector</a> is configured on the <span style="font-weight: bold;">Deadline</span> tab, the other connectors can only be activated before the task deadline.</p>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">начало внимание</span></p>
|
||
<p class="p_Normal">Since the process is routed through additional connectors automatically, there are no buttons for them in the review task. By default, the user will only see the <span style="font-weight: bold;">Informed</span> button. You can add buttons to make a <a href="360010385600.html#custom-statuses-tab" class="topiclink">custom decision on review</a>, but they do not affect the selection of a connector during the process execution.</p>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">конец внимание</span></p>
|
||
<p class="p_Normal">To open the window with connector settings, click on its name.</p>
|
||
<p class="p_Normal">On the <span style="font-weight: bold;">General</span> tab, enter a name for the connector that will appear on the process diagram. You can also enter a description.</p>
|
||
<p class="p_Normal"><img alt="send_item_08" width="576" height="283" style="margin:0;width:576px;height:283px;border:none" src="send_item_08.png"/></p>
|
||
<p>Then go to the <span style="font-weight: bold;">Conditions</span> tab, click <span style="font-weight: bold;">+Add Condition</span>, and specify:</p>
|
||
<p><img alt="send_item_09" width="633" height="258" style="margin:0;width:633px;height:258px;border:none" src="send_item_09.png"/></p>
|
||
<ul style="list-style-type:disc">
|
||
<li style="line-height: 1.20; margin-top: 14px; margin-right: 0; margin-bottom: 0;"><span style="font-weight: bold;">Process Variable</span>. Specify a variable from the process context or a specific value: </li></ul>
|
||
<ul style="list-style-type:disc"><ul style="list-style-type:circle">
|
||
<li style="line-height: 1.20; margin-top: 14px; margin-right: 0; margin-bottom: 0;"><span style="font-weight: bold;">Archived</span>.<span style="font-size: 15px;"> </span>Check whether the list of informed users has been archived. Please note that for items, the <span style="color: #0000ff;"><a href="approval-settings.html" class="topiclink">rules of list archiving</a></span> are set in the app settings. For files, lists are always archived when a new version is added.</li><li style="line-height: 1.20; margin-top: 14px; margin-right: 0; margin-bottom: 0;"><span style="font-weight: bold;">Cannot find information object</span>. Check that the object is not deleted from the system. Please note that this option works only when a file is sent for information. If an app item is being sent, the process will be terminated with an error upon its deletion.</li><li style="line-height: 1.20; margin-top: 14px; margin-right: 0; margin-bottom: 0;"><span style="font-weight: bold;">No access to the information object</span>.</li></ul></li></ul>
|
||
<ul style="list-style-type:disc">
|
||
<li><span style="font-weight: bold;">Operation</span>. Specify a comparison operator to check a specific condition.</li><li><span style="font-weight: bold;">Field value</span>. Enter the value with which the condition will be considered fulfilled.</li><li><span style="font-family: Inter; font-weight: bold;">Logical Operator</span><span style="font-family: Inter;">.</span><span style="font-family: Inter; font-weight: bold;"> </span><span style="font-family: Inter;">Determine which logical operations to apply when checking several conditions:</span></li></ul>
|
||
<ul style="list-style-type:disc"><ul style="list-style-type:circle">
|
||
<li style="line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;"><span style="font-family: Inter; font-weight: bold;">AND</span><span style="font-family: Inter;">. The result is </span><span style="font-family: Inter; font-weight: bold;">True</span><span style="font-family: Inter;"> if both conditions that this operator connects are met.</span></li><li style="line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;"><span style="font-family: Inter; font-weight: bold;">OR</span><span style="font-family: Inter;">. The result is </span><span style="font-family: Inter; font-weight: bold;">True</span><span style="font-family: Inter;"> if at least one of the conditions that this operator connects is met.</span></li><li style="line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;"><span style="font-family: Inter; font-weight: bold;">AND NOT</span><span style="font-family: Inter;">.</span><span style="font-family: Inter; font-weight: bold;"> </span><span style="font-family: Inter;">The result is </span><span style="font-family: Inter; font-weight: bold;">True</span><span style="font-family: Inter;"> if the first condition is met while the second condition is not.</span></li><li style="line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;"><span style="font-family: Inter; font-weight: bold;">OR NOT</span><span style="font-family: Inter;">.</span><span style="font-family: Inter; font-weight: bold;"> </span><span style="font-family: Inter;">The result is </span><span style="font-family: Inter; font-weight: bold;">True</span><span style="font-family: Inter;"> if the first condition is met or the second condition is not.</span></li></ul></li></ul>
|
||
<p style="text-indent: -24px; line-height: 1.20; margin: 7px 0 7px 24px;"><span style="font-family: Inter;">Please note that the conditions are checked in the order they are listed in the connector settings.</span></p>
|
||
<p style="line-height: 1.20; margin: 7px 0 7px 0;"><span style="font-family: Inter;">For review tasks placed in the swimlane with multiple executors, the transition conditions are checked each time one of the users completes the task.</span></p>
|
||
<p style="text-indent: -24px; line-height: 1.20; margin: 7px 0 7px 24px;"><span style="font-family: Inter;">For more information about using connectors in processes, see the <a href="connectors-use-cases.html" class="topiclink">Connectors</a> article.</span></p>
|
||
<h2 class="p_Heading2"><a id="custom-statuses-tab" class="hmanchor"></a><span class="f_Heading2">Custom Statuses tab</span></h2>
|
||
<p style="line-height: 1.20; margin: 7px 0 16px 0;"><span style="font-family: Inter;">When creating a custom status in the task, an additional button will appear. With its help, employees will be able to provide custom decisions within the standard process of sending documents and app items for review.</span></p>
|
||
<p style="line-height: 1.20; margin: 7px 0 16px 0;"><span style="font-family: Inter;">Depending on what object (app item or file) is stored in the variable specified on the </span><span style="font-family: Inter; font-weight: bold;">General</span><span style="font-family: Inter;"> tab in the </span><span style="font-family: Inter; font-weight: bold;">Items to send</span><span style="font-family: Inter;"> field, the button will appear on the item page or on the file preview page.</span></p>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">начало внимание</span></p>
|
||
<p class="p_Normal">The buttons in the review task are used only for specifying custom decisions and do not determine the further course of the business process. Regardless of the selected button, if the review is completed successfully, the process will continue with the <a href="360010385600.html#transitions-tab" class="topiclink">default connector</a> selected in the settings.</p>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">конец внимание</span></p>
|
||
<p style="line-height: 1.20; margin: 7px 0 16px 0;"><span style="font-family: Inter;">For instance, you can add the </span><span style="font-family: Inter; font-weight: bold;">Requires Clarification </span><span style="font-family: Inter;">status. An employee can complete the task of viewing a document and specify that they have questions after reading it. The document progress through the process will continue according to the logic defined by the outgoing connectors. In the list of informed users, opposite the name of the user who selected this decision, the </span><span style="font-family: Inter; font-weight: bold;">Requires Clarification </span><span style="font-family: Inter;">status will appear.</span></p>
|
||
<p style="line-height: 1.20; margin: 7px 0 16px 0;"><span style="font-family: Inter;">The final status of the item, regardless of the chosen decisions, will be </span><span style="font-family: Inter; font-weight: bold;">Informed</span><span style="font-family: Inter;">.</span></p>
|
||
<p style="line-height: 1.28; margin: 0 0 11px 0;"><span style="font-family: Inter;">To configure a custom status, enable the </span><span style="font-family: Inter; font-weight: bold;">Use custom status</span><span style="font-family: Inter;"> option and fill in the fields that appear:</span></p>
|
||
<p style="line-height: 1.28; margin: 0 0 11px 0;"><img alt="send-item-brix-06" width="776" height="317" style="margin:0;width:776px;height:317px;border:none" src="send-item-brix-06.png"/></p>
|
||
<ul style="list-style-type:disc">
|
||
<li style="line-height: 1.28; margin-top: 0; margin-right: 0; margin-bottom: 11px;"><span style="font-family: Inter; font-weight: bold;">Button label in task</span><span style="font-family: Inter; font-weight: bold; color: #ff0000;">*</span><span style="font-family: Inter;">. Enter the name of the button that the user will click to complete the task. The additional button will be displayed next to the </span><span style="font-family: Inter; font-weight: bold;">Informed</span><span style="font-family: Inter;"> system button. </span><img alt="send-document-custom-statuses-2" width="881" height="457" style="margin:0;width:881px;height:457px;border:none" src="send-document-custom-statuses-2.png"/></li><li style="line-height: 1.28; margin-top: 0; margin-right: 0; margin-bottom: 11px;"><span style="font-family: Inter; font-weight: bold;">Status Label</span><span style="font-family: Inter; font-weight: bold; color: #ff0000;">*</span><span style="font-family: Inter;">. Enter the name of the status that will be displayed in the list of informed users after closing the task.</span></li></ul>
|
||
<p style="line-height: 1.28; margin: 0 0 11px 34px;"><img alt="send-document-custom-statuses-3" width="264" height="193" style="margin:0;width:264px;height:193px;border:none" src="send-document-custom-statuses-3.png"/></p>
|
||
<p style="line-height: 1.20; margin: 7px 0 16px 0;"><span style="font-family: Inter;">The custom status will be shown in the list of informed users and will also be displayed alongside the </span><span style="font-family: Inter; font-weight: bold;">Informed </span><span style="font-family: Inter;">system status when the list is exported.</span></p>
|
||
<h2 class="p_Heading2"><a id="signature-settings-tab" class="hmanchor"></a><span class="f_Heading2">Signature tab</span></h2>
|
||
<p style="line-height: 1.20; margin: 7px 0 16px 0;">You can configure the use of electronic signature at the reviewing step. In this case, the user clicks the <span style="font-weight: bold;">Informed</span> button in the incoming task and then enables the signing option. In the opened window, the employee selects the objects for signing: attributes and file. In this way, they confirm that they have reviewed the document. The data about it are saved on the page of the signed app item. To learn more about how to perform such a task and where to view the details of the applied electronic signature, see the <a href="/en/help/ecm/digital_signtature_in_apps.html" target="_blank" class="weblink">Digital signature in apps</a> article. </p>
|
||
<p style="line-height: 1.20; margin: 7px 0 16px 0;">To enable signing of the review object, on the <span style="font-weight: bold;">Signature</span> tab set the parameters in the same way as for the <span style="font-weight: bold;">Approval</span> activity. The only option missing in the settings is <span style="font-weight: bold;">Sign Decision</span> because when getting informed, no resolution is made on the document. Read more about it in the <a href="360010366380.html" class="topiclink">Approval</a> article.</p>
|
||
<p style="line-height: 1.28; margin: 0 0 11px 0;"><img alt="send-item-brix-07" width="809" height="345" style="margin:0;width:809px;height:345px;border:none" src="send-item-brix-07.png"/></p>
|
||
<h2 class="p_Heading2"><a id="substitutions" class="hmanchor"></a><span class="f_Heading2">Substitutions tab</span></h2>
|
||
<p style="line-height: 1.20; margin: 7px 0 16px 0;">On this tab, you can specify a variable that controls the reassignment of the task to an employee who <span style="color: #0000ff;"><a href="360010244599.html" class="topiclink">substitutes</a></span> the primary performer.</p>
|
||
<p style="text-align: justify; line-height: 1.20; margin: 7px 0 16px 0;"><img alt="send-item-brix-08" width="727" height="219" style="margin:0;width:727px;height:219px;border:none" src="send-item-brix-08.png"/></p>
|
||
<p style="line-height: 1.20; margin: 7px 0 16px 0;">In the <span style="font-weight: bold;">Ignore substitution</span> field, specify a variable from the business process context of the <span style="color: #0000ff;"><a href="360009707032.html#yes-no-switch" class="topiclink">Yes/No switch</a></span> type.</p>
|
||
<p style="line-height: 1.20; margin: 7px 0 16px 0;">If the variable is set to <span style="font-weight: bold;">Yes</span>, the task will be assigned to the initially specified approver, and if it is set to <span style="font-weight: bold;">No</span>, it will be assigned to the substitute employee. The value of the variable can be changed during the business process, for example, by placing the variable on the form of another task, or by using <span style="color: #0000ff;"><a href="360027203731.html" class="topiclink">scripts</a></span>.</p>
|
||
<p style="line-height: 1.20; margin: 7px 0 16px 0;">For example, you can ignore substitution if the document to be read contains confidential data that should not be disclosed to third parties.</p>
|
||
<h2 class="p_Heading2"><a id="h_5d6dfa6b-3345-49e7-ac8f-47c604f77f17" class="hmanchor"></a><span class="f_Heading2">List of informed users</span></h2>
|
||
<p style="line-height: 1.20; margin: 0 0 11px 0;">Once the process reaches the <span style="font-weight: bold;">Send document/App item</span> activity, a notification about the assigned task with a link to a file, document, or app item is displayed in the <span style="color: #0000ff;"><a href="360014162972.html" class="topiclink">#Activity stream</a></span> of executors. </p>
|
||
<p style="line-height: 1.20; margin: 14px 0 0 0;">A list of informed users is created on the object page with a list of employees to whom tasks have been assigned. A question mark is displayed next to the user who has not yet viewed the document. After the task is completed, the date, time, and the comment left, and the file attached during the review are added to the list.</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;"><img alt="sdai 5" width="797" height="397" style="margin:0;width:797px;height:397px;border:none" src="hmfile_hash_edab3e8e.png"/></p>
|
||
<p style="line-height: 1.20; margin: 14px 0 0 0;">If a document has been sent to multiple executors, you can view the entire list by clicking <span style="font-weight: bold;">All</span> <span style="font-weight: bold;">users</span> in the list. By applying a filter, you can find out which employees have not yet completed the task.</p>
|
||
<p style="line-height: 1.28; margin: 0 0 11px 0;"><img alt="send-document-list-export" width="291" height="252" style="margin:0;width:291px;height:252px;border:none" src="send-document-list-export.png"/></p>
|
||
<p style="text-align: justify; line-height: 1.20; margin: 19px 0 0 0;">You can export list of informed users with all decisions by clicking the upload icon on the sidebar of the document:</p>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal"><img alt="read_doc_icon" width="19" height="19" style="margin:0;width:19px;height:19px;border:none" src="read_doc_icon.png"/> To export the list as an <span style="font-weight: bold;">.xlsx</span> file.</li><li class="p_Normal"><img alt="pdf-icon" width="18" height="22" style="margin:0;width:18px;height:22px;border:none" src="pdf-icon.png"/><span class="f_ImageCaption"> </span>To export the list as a <span style="font-weight: bold;">.pdf</span> file. The icon will be displayed if a <a href="ready-made-sheets-settings.html#create-template" class="topiclink">custom template</a> for sheet generation is used.</li></ul>
|
||
<p style="line-height: 1.20; margin: 7px 0 16px 0;">Read more in the <a href="/en/help/ecm/approval-sheets.html" target="_blank" class="weblink">Lists of informed users and approval sheets</a> article.</p>
|
||
|
||
<div class="bottom-nav">
|
||
|
||
<a id="prev-link" class="topic__navi_prev" href="watermark.html">
|
||
<span class="bottom-nav__arrow bottom-nav__arrow--prev"></span> <span
|
||
class="bottom-nav__link">watermark.html</span>
|
||
</a>
|
||
|
||
|
||
<a id="next-link" class="topic__navi_next" href="send-for-information-use-case.html">
|
||
<span class="bottom-nav__link">send-for-information-use-case.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>
|