All checks were successful
Deploy Static Site / deploy (push) Successful in 6m6s
352 lines
61 KiB
HTML
352 lines
61 KiB
HTML
<!DOCTYPE html>
|
||
<html lang="en">
|
||
|
||
<head>
|
||
<title>Approval</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 Approval activity is used to manually or automatically approve or reject a document, an app item, or a file during a business process. When the process moves to the..." />
|
||
<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 / Approval</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;">Approval</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;"><img alt="approval 1" width="115" height="90" style="margin:0;width:115px;height:90px;border:none" src="hmfile_hash_a1140c6d.png"/>The <span style="font-weight: bold;">Approval</span> activity is used to manually or automatically approve or reject a <span style="color: #394149;"><a href="360009923631" class="weblink">document</a></span><span style="color: #394149;">, an </span><span style="color: #394149;"><a href="360016427291" class="weblink">app item</a>,</span><span style="color: #394149;"> or a </span><span style="color: #394149;"><a href="360014164452" class="weblink">file</a></span><span style="font-size: 15px; color: #394149;"> </span>during a business process. When the process moves to the <span style="font-weight: bold;">Approval</span> activity, an <a href="approval-sheets.html" class="topiclink">approval sheet</a> is automatically created. By default, the final <span style="font-weight: bold;">Approved</span> or <span style="font-weight: bold;">Rejected</span> resolution is displayed in it after the process is completed. You can generate the approval result after the approval stage. To do this, use the <a href="360011756780.html" class="topiclink">End Approval</a> activity.</p>
|
||
<p style="line-height: 1.20; margin: 7px 0 16px 0;"><a id="manual" class="hmanchor"></a>The location of the activity on the process diagram and its settings differ depending on the approval method that you select:</p>
|
||
<ul style="list-style-type:disc">
|
||
<li style="line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 0;"><span style="font-weight: bold;">Manually</span>. In this case, when the process moves to the <span style="font-weight: bold;">Approval</span> activity, the task to review the document is assigned to the executor and an approval sheet with the <span style="font-weight: bold;">Pending approval</span> status is created. In the activity settings, you can configure the approval management. You can set parallel or sequential approvals for a group of approvers, the requirement to sign the document with a digital signature, and set a deadline. An employee actively participates in the approval process by performing the task that you have configured in the activity.</li><li style="line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 16px;"><span style="font-weight: bold;">Automatically</span>. This option provides that the <span style="font-weight: bold;">Approval</span> activity is executed automatically. No approval task is assigned within the activity. Such a task should be set up additionally and placed on the process diagram before it moves to the <span style="font-weight: bold;">Approval</span> activity. The executor only needs to make a decision (approve or reject) via the standard task interface. Then the process will move to the <span style="font-weight: bold;">Approval</span> activity, where the corresponding decision will be made automatically. At the same time, an approval sheet with the decision is created. Read more in the <span style="color: #0000ff;"><a href="auto-approval.html" class="topiclink">Automatic approval</a></span> article.</li></ul>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Set up manual approval</span></h2>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 19px 0 0 0;">Place the <span style="font-weight: bold;">Approval</span> activity on the process segment where the employee specified in the swimlane must approve or reject the document. The user will be tasked to review the document. At the same time, an <a href="approval-sheets.html" class="topiclink">approval sheet</a> will be created. It will record the approvers’ decisions and their comments with additionally attached files.</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 19px 0 0 0;">By default, the final <span style="font-weight: bold;">Approved</span> or <span style="font-weight: bold;">Rejected</span> resolution is generated after the end of the process. Until then, users see the <span style="font-weight: bold;">Pending approval</span> status. To display the final resolution in the approval sheet after the approval stage, use the <a href="360011756780.html" class="topiclink">End Approval</a> block. You can find the example of such process in the <a href="approval-use-case.html" class="topiclink">Approval use case</a> article.</p>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">начало внимание</span></p>
|
||
<p style="line-height: 1.20; margin: 14px 0 0 0;">Make sure that you have added a <a href="process_context.html" class="topiclink">process context</a> variable that will store the object <span style="font-family: Inter;">sent for approval</span>.</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: 19px 0 0 0;">To open the settings, double-click on the <span style="font-weight: bold;">Approval</span> activity on the process diagram.<span style="font-weight: bold;"> </span>The settings are managed in three tabs: <a href="360010366380.html#general_tab" class="topiclink">General</a>, <a href="360010366380.html#deadline_tab" class="topiclink">Deadline</a>, <a href="360010366380.html#schedule" class="topiclink">Schedule in Calendar</a>, <a href="360010366380.html#connectors_tab" class="topiclink">Connectors</a>, <a href="360010366380.html#custom-statuses" class="topiclink">Custom Statuses</a>, <a href="360010366380.html#signature" class="topiclink">Signature</a>, and<span style="font-family: 'Times New Roman',Times,Georgia,serif;"> </span><a href="360010366380.html#signature" class="topiclink">Substitutions</a><span style="font-family: 'Times New Roman',Times,Georgia,serif;">. </span>You can specify the task name, set a deadline, define the approval logic, add the task to the executor’s calendar, enable the signature, etc.</p>
|
||
<h3 class="p_Heading3"><a id="general_tab" class="hmanchor"></a><span class="f_Heading3">General tab</span></h3>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 19px 0 0 0;"><img alt="approval-brix-01" width="788" height="507" style="margin:0;width:788px;height:507px;border:none" src="approval-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 a name that will be displayed in the process diagram. We recommend choosing a short yet informative name to make the process diagram easy to read.</li><li style="line-height: 1.20;"><span style="font-weight: bold;">Task name</span><span style="font-weight: bold; color: #ff0000;">*</span>.<span style="font-weight: bold;"> </span>Enter a text that the task executor will see in their task list or on the task page. You can add a <a href="process_context.html" class="topiclink">context variable</a> to the name to make it more detailed. To do that, click on the <span style="font-weight: bold;">{+}</span> icon in the right corner of the field. You can also add <a href="360007679591.html#conditions-and-functions" class="topiclink">conditions and functions</a>, just like for the item name templates. This allows you to generate a more informative name for the task.</li><li style="line-height: 1.20;"><span style="font-weight: bold;">Item to send for approval</span><span style="font-weight: bold; color: #ff0000;">*</span>. Specify the <a href="process_context.html" class="topiclink">context variable</a> that will store the file or app item.</li><li style="line-height: 1.20;"><span style="font-weight: bold;">Write the output to a variable</span>. Specify a variable of the <span style="font-weight: bold;">String</span> type to which the code of the result of the current activity execution will be written: <code><b>approved</b></code> or <code><b>rejected</b></code>. The result depends on which button the approver clicks on the task page: <span style="font-weight: bold;">Approve</span> or <span style="font-weight: bold;">Reject</span>.<span style="font-weight: bold;"> </span>When there are several approvers and at least one of them refuses to approve, the result will contain the<code><b>rejected</b></code> value. If the agreement is terminated, the terminated value will be written. This variable can be placed on the app form, as well as used in <a href="360012495911.html" class="topiclink">gateways</a> and <a href="360027203731.html" class="topiclink">scripts</a> to implement more complex approval logic.</li><li style="line-height: 1.20;"><span style="font-weight: bold;">Approval method</span>. Depending on the selected method, the set of tabs in the settings window and the list of settings listed below the current tab differ. To configure <span style="color: #0000ff;"><a href="auto-approval.html" class="topiclink">automatic approval</a></span>, select the <span style="font-weight: bold;">Automatically</span> option.</li><li style="line-height: 1.20;"><span style="font-weight: bold;">Notification to the activity stream</span>. Enable this option so that a notification about approval start is sent to the file or app item activity stream.</li></ul>
|
||
<p style="line-height: 1.20;">In case you select the <span style="font-weight: bold;">Manually</span> approval method, the following fields will be displayed below:</p>
|
||
<ul style="list-style-type:disc">
|
||
<li style="line-height: 1.20;"><span style="font-weight: bold;">Notification</span>. Enable the option to ensure that the approver receives a task assignment notification in the activity stream.</li><li style="line-height: 1.20;"><span style="font-weight: bold;">Approval type</span>.<span style="font-weight: bold;"> </span>This option appears only if a user group or a department is specified as executor in <a href="360012263032.html" class="topiclink">swimlane</a> settings. Determine how the approval task should be assigned and executed:</li></ul>
|
||
<ul style="list-style-type:disc"><ul style="list-style-type:disc">
|
||
<li style="line-height: 1.20;"><span style="font-weight: bold;">Parallel</span>. The approval task will be simultaneously assigned to all executors included in the swimlane. Depending on the <a href="360010366380.html#connectors_tab" class="topiclink">connector settings</a>, there are two options. Either each executor needs to review the document before the process moves on to the next step, or the next step starts as soon as one of the executors approves or rejects the document.</li></ul></li></ul>
|
||
<ul style="list-style-type:disc"><ul style="list-style-type:disc">
|
||
<li style="line-height: 1.20;"><span style="font-weight: bold;">Sequential</span>.<span style="font-weight: bold;"> </span>The task will be assigned consequently to all the executors included in the swimlane one by one. The process will go to the next step only when all the employees will complete the task. With <a href="360010366380.html#connectors_tab" class="topiclink">connector settings</a>, you can determine what happens if an approver rejects the document.</li></ul></li></ul>
|
||
<p style="line-height: 1.20; margin: 14px 0 0 58px;">Please note that in a dynamic swimlane, the tasks will be assigned in the same order as users were specified in the variable that stores users. In a static swimlane, the sequence is random.</p>
|
||
<ul style="list-style-type:disc">
|
||
<li style="line-height: 1.20;"><span style="font-weight: bold;">Leave only actual participants</span>. Remove those users who were assigned the approval task but had neither approved nor rejected the document from the approval sheet.</li></ul>
|
||
<p style="line-height: 1.20;"><span style="font-size: 13px; color: #000000;"> </span></p>
|
||
<p style="line-height: 1.20; margin: 14px 0 0 0;">Here are some examples to explain more clearly in which cases this or that type of approval is used.</p>
|
||
<p class="p_Normal"><a class="dropdown-toggle" style="font-style: normal; font-weight: normal; color: #000000; background-color: transparent; text-decoration: none;" href="javascript:HMToggle('toggle','TOGGLE0186A1')">Example 1</a></p>
|
||
<div id="TOGGLE0186A1" class="dropdown-toggle-body" style="text-align: left; text-indent: 0; line-height: 1.80; padding: 0 0 0 0; margin: 0 0 0 0;"><table style="border:none; border-spacing:0;">
|
||
<tr>
|
||
<td style="vertical-align:top; padding:0; border:none"><p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;"> <br />
|
||
Let’s assume that the approval process in a company is organized in such a way that the contract is sent to an accountant, a lawyer, an economist, and a security officer for review. It is important for us that the work on the contract is not delayed and the decision is made as soon as possible, so the task of approval should come to all the specified employees at the same time. In this case, you should wait for each of them to decide before sending the contract further down the path. If you select the <span style="font-weight: bold;">Parallel</span> option and set the approval percentage to 100 in the connector settings, then all employees will receive the task <span style="font-weight: bold;">Approve</span> <span style="font-weight: bold;">contract</span>, and until each of them completes their work, the process will not move on.</p>
|
||
</td>
|
||
</tr>
|
||
</table>
|
||
</div>
|
||
<p class="p_Normal"><a class="dropdown-toggle" style="font-style: normal; font-weight: normal; color: #000000; background-color: transparent; text-decoration: none;" href="javascript:HMToggle('toggle','TOGGLE0186A2')">Example 2</a></p>
|
||
<div id="TOGGLE0186A2" class="dropdown-toggle-body" style="text-align: left; text-indent: 0; line-height: 1.80; padding: 0 0 0 0; margin: 0 0 0 0;"><table style="border:none; border-spacing:0;">
|
||
<tr>
|
||
<td style="vertical-align:top; padding:0; border:none"><p class="p_Normal"> <br />
|
||
Let’s consider the work of the legal department. Any employee can check the content of the contract for compliance with the law and predict the legal consequences of the stated conditions. It does not matter who exactly will be involved in the approval, it is only important that the task be completed as quickly as possible. In this case, you should use the <span style="font-weight: bold;">Parallel</span> option, but at the same time set the percentage of approvals and rejections in the <a href="360010366380.html#connectors_tab" class="topiclink">connector settings</a> to be higher than zero. The task will be sent to each employee of the legal department, and the one who is less busy at the moment will be able to start performing it immediately. When one of the employees makes a decision, the approval task will disappear from the list of tasks of other users. If the <span style="font-weight: bold;">Leave only actual participants</span> option is enabled, only the user who provided a decision will be displayed in the approval sheet.</p>
|
||
</td>
|
||
</tr>
|
||
</table>
|
||
</div>
|
||
<p class="p_Normal"><a class="dropdown-toggle" style="font-style: normal; font-weight: normal; color: #000000; background-color: transparent; text-decoration: none;" href="javascript:HMToggle('toggle','TOGGLE0186A3')">Example 3</a></p>
|
||
<div id="TOGGLE0186A3" class="dropdown-toggle-body" style="text-align: left; text-indent: 0; line-height: 1.80; padding: 0 0 0 0; margin: 0 0 0 0;"><table style="border:none; border-spacing:0;">
|
||
<tr>
|
||
<td style="vertical-align:top; padding:0; border:none"><p class="p_Normal"> <br />
|
||
Suppose we need several managers to read and approve a report before the process continues. If you select the <span style="font-weight: bold;">Sequential</span> option, the system assigns the review task to one manager first, and after they approve the report, to another manager. In the connector settings, you can specify how to proceed if one of the approvers rejects the report.</p>
|
||
</td>
|
||
</tr>
|
||
</table>
|
||
</div>
|
||
<h3 class="p_Heading3"><a id="form" class="hmanchor"></a><span class="f_Heading3">Form tab</span></h3>
|
||
<p style="line-height: 1.20; margin: 7px 0 16px 0;">This tab appears if an app item has been sent for approval. It allows you to configure your own approval task form from scratch. If you want to use the default form, you do not need to change the settings on this tab.</p>
|
||
<p style="line-height: 1.20; margin: 7px 0 16px 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 16px 0;">This opens the <span style="color: #0000ff;"><a href="360029250931.html" 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, etc. Save the settings you have made.</p>
|
||
<p style="line-height: 1.20; margin: 7px 0 16px 0;">To configure the display of the app item properties being sent for approval, go to the <span style="font-weight: bold;">Form</span> tab in the <span style="font-weight: bold;">Approval</span> activity settings again.</p>
|
||
<p style="text-align: justify; line-height: 1.20; margin: 7px 0 16px 0;"><img alt="approval_activity_02" width="785" height="504" style="margin:0;width:785px;height:504px;border:none" src="approval_activity_02.png"/></p>
|
||
<p style="line-height: 1.28; margin: 0 0 11px 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#form" class="topiclink">Task</a></span> element. Please note that these settings are available only for a custom form.</p>
|
||
<h3 class="p_Heading3"><a id="deadline_tab" class="hmanchor"></a><span class="f_Heading3">Deadline tab</span></h3>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 19px 0 0 0;"><img alt="approval_main2" width="597" height="326" style="margin:0;width:597px;height:326px;border:none" src="approval_main2.png"/></p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">On this tab, you can set the due date for the task as well as specify the system behavior in case the task is not completed on 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>Specify the number of days, hours, or minutes that the executor has to complete the task. <span style="font-family: Inter;">The calculations can be based on the</span> <a href="360004890291.html" class="topiclink">business calendar</a>.</li></ul>
|
||
<p style="line-height: 1.20; margin: 0 0 0 34px;">If the approval task belongs to a swimlane with multiple executors, each of the executors will have the specified number of days, hours, and minutes to complete the task.</p>
|
||
<ul style="list-style-type:disc">
|
||
<li style="line-height: 1.20;"><span style="font-weight: bold;">Variable</span>.<span style="font-weight: bold;"> </span>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 made a decision on the document. In this case, you can use a <a href="process_context.html" class="topiclink">context variable</a> of the <span style="font-weight: bold;">Date/Time</span> type to define the deadline for the approval task.</li></ul>
|
||
<p style="line-height: 1.20; margin: 0 0 0 34px;"><span style="font-family: Inter;">If the approval 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 this moment. Otherwise, the task will be considered overdue.</span></p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">In the <span style="font-weight: bold;">Notification </span>field, you can select users who will be notified if the executor fails to complete the approval 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.</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;"><img alt="sdai 4" width="646" height="218" style="margin:0;width:646px;height:218px;border:none" src="hmfile_hash_95ae5ae4.png"/></p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">The <span style="font-weight: bold;">Interrupt</span> field allows you to specify which path the process flow should take if the executor fails to complete the task on time.<a id="escalation" class="hmanchor"></a></p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;"><img alt="approval_activity_05" width="607" height="235" style="margin:0;width:607px;height:235px;border:none" src="approval_activity_05.png"/></p>
|
||
<p style="line-height: 1.20; margin: 14px 0 0 0;">This connector is marked with the timer icon on the process diagram. The process takes this path if the set time is over but the executor hasn’t marked the task as completed. The other connectors will not be activated.</p>
|
||
<p style="line-height: 1.28; margin: 0 0 11px 0;">For example, let’s say that the employee from the legal department didn’t complete the contract approval task on time. The process flow will take the escalation connector and assign the next task to the CEO.</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;"><img alt="05.PNG" title="05.PNG" width="912" height="485" style="margin:0;width:912px;height:485px;border:none" src="360007221480-05.png"/></p>
|
||
<p class="p_Normal"> </p>
|
||
<h3 class="p_Heading3"><span class="f_Heading3">Schedule in Calendar tab</span></h3>
|
||
<p style="line-height: 1.20;"><a id="schedule" class="hmanchor"></a></p>
|
||
<p style="line-height: 1.20;"><img alt="approval_activity_04" width="844" height="255" style="margin:0;width:844px;height:255px;border:none" src="approval_activity_04.png"/></p>
|
||
<p style="line-height: 1.20;">This tab appears if a deadline is set for the task, and is used to add the task to the executor’s calendar.</p>
|
||
<p style="line-height: 1.20; margin: 16px 0 0 0;">To avoid overscheduling, you can schedule the task only for some of the days. Let’s say that the approval deadline is in a week. You can schedule the task to appear in the calendar only on the last three days of the week:</p>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="1" style="line-height: 1.20;">Add <span style="font-weight: bold;">Date/Time</span> variables to the context. They will store the values for the task deadlines in the calendar.</li><li value="2" style="line-height: 1.20;">Add a <a href="360027203731.html" class="topiclink">script</a> on the process diagram before the <span style="font-weight: bold;">Approval</span> activity to calculate the values of these variables.</li><li value="3" style="line-height: 1.20;">On the <span style="font-weight: bold;">Schedule in Calendar</span> tab, link the variables with the <span style="font-weight: bold;">Start date</span> and <span style="font-weight: bold;">End date</span> fields.</li></ol>
|
||
<p style="line-height: 1.20;"><span style="font-size: 13px; color: #000000;"> </span></p>
|
||
<h3 class="p_Heading3"><a id="connectors_tab" class="hmanchor"></a><span class="f_Heading3">Connectors tab</span></h3>
|
||
<p style="line-height: 1.28; margin: 0 0 11px 0;">Here you can define the approval logic: specify the conditions that define which <a href="360015835331.html" class="topiclink">connector</a> the process flow should take. Do not forget to specify a default connector that the process will follow if none of the specified conditions are met.</p>
|
||
<p style="line-height: 1.20; margin: 0 0 11px 0;">If you have added a connector for <span style="color: #0000ff;"><a href="360010366380.html#error-handling" class="topiclink">error handling</a></span>, it will be displayed on this tab along with the others. Do not set conditions for it, as they will be ignored when the process is executed.</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 19px 0 0 0;"><img alt="approval_activity_03" width="699" height="369" style="margin:0;width:699px;height:369px;border:none" src="approval_activity_03.png"/></p>
|
||
<p class="p_Normal" style="line-height: 1.20; page-break-inside: avoid; margin: 14px 0 0 0;">Note that if an<span style="font-size: 15px; color: #394149;"> </span><a href="360010366380.html#escalation" class="topiclink">escalation connector</a> is set up on the <span style="font-weight: bold;">Deadlines</span> tab, the other connectors can be activated only before the task’s deadline is reached.</p>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">начало внимание</span></p>
|
||
<p style="line-height: 1.28; margin: 0 0 11px 0;">By default, the <span style="font-weight: bold;">Approval</span> task form has only two buttons: <span style="font-weight: bold;">Approve</span> and <span style="font-weight: bold;">Reject</span>, regardless of how many outgoing connectors the activity has on the process diagram. You can add other buttons for the task by setting up <a href="360010366380.html#custom-statuses" class="topiclink">custom approval statuses</a>. However, the further process flow is determined only by the conditions set for the connectors.</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;">To open the connector’s settings, double-click on its name.</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">On the <span style="font-weight: bold;">General</span> tab, enter a short and understandable name for the connector. It will be displayed on the process diagram. You can also add a description of the connector.</p>
|
||
<h3 class="p_Heading3" style="line-height: 1.20; margin: 26px 0 0 0;"><img alt="approval 6" width="564" height="271" style="margin:0;width:564px;height:271px;border:none" src="hmfile_hash_9f9fe8b4.png"/></h3>
|
||
<p class="p_Normal"><a id="condition" class="hmanchor"></a>On the <span style="font-weight: bold;">Conditions</span> tab, adjust the settings:</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;"><img alt="approval_activity_06" width="553" height="251" style="margin:0;width:553px;height:251px;border:none" src="approval_activity_06.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: <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;">Approval Percentage</span>.</li><li style="line-height: 1.20; margin-top: 14px; margin-right: 0; margin-bottom: 0;"><span style="font-weight: bold;">Rejection Percentage</span>.</li><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 approval sheet has been archived. Please note that for items the <span style="color: #0000ff;"><a href="approval-settings.html" class="topiclink">rules of sheet archiving</a></span> are set in the app settings. For files, sheets 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;">Approval object not found</span>. Check that the object is not deleted from the system. Please note that this option works only when a file is sent for approval. 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 approval object</span>.</li></ul></li></ul>
|
||
<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;">Operation</span>. Define a comparison operator to check a specific condition.</li><li style="line-height: 1.20; margin-top: 14px; margin-right: 0; margin-bottom: 0;"><span style="font-weight: bold;">Field Value</span>. Enter the value at which the condition will be met.</li><li style="line-height: 1.20; margin-top: 14px; margin-right: 0; margin-bottom: 0;"><span style="font-weight: bold;">Logical Operator</span>. This is a logical operation used to check multiple conditions. If the overall check result is <span style="font-weight: bold;">True</span>, the process continues with this connector:<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;">AND</span>. The result is <span style="font-weight: bold;">True</span> if both conditions are met.</li><li style="line-height: 1.20; margin-top: 14px; margin-right: 0; margin-bottom: 0;"><span style="font-weight: bold;">OR</span>. The result is <span style="font-weight: bold;">True</span> if at least one condition is met.</li><li style="line-height: 1.20; margin-top: 14px; margin-right: 0; margin-bottom: 0;"><span style="font-weight: bold;">AND NOT</span>. The result is <span style="font-weight: bold;">True</span> if the first condition is met while the second condition is not.</li><li style="line-height: 1.20; margin-top: 14px; margin-right: 0; margin-bottom: 0;"><span style="font-weight: bold;">OR NOT</span>. The result is <span style="font-weight: bold;">True</span> if the first condition is met or the second condition is not.</li></ul></li></ul>
|
||
<p style="line-height: 1.20; margin: 14px 0 0 0;">Please note that conditions are checked in the order they are listed in the connector settings.</p>
|
||
<p style="line-height: 1.20; margin: 14px 0 0 0;">For approval tasks assigned to a swimlane with multiple executors, connector conditions are checked each time one of them completes the task.</p>
|
||
<p style="line-height: 1.20; margin: 14px 0 0 0;">For more details on using connectors in the process, refer to the <a href="360015835331.html" class="topiclink">Connectors</a> article. To configure conditions for connectors in the <span style="font-weight: bold;">Approval</span> activity, read the <a href="approval-use-case.html" class="topiclink">Approval use case</a> article.</p>
|
||
<h3 class="p_Heading3"><a id="custom-statuses" class="hmanchor"></a><span class="f_Heading3">Custom Statuses tab</span></h3>
|
||
<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 approval process.</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;">Item to send for approval</span><span style="font-family: Inter; font-weight: bold; color: #ff0000;">*</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 style="line-height: 1.28; margin: 0 0 11px 0;">The buttons in the approval task are used only for making a decision and do not determine the further flow of the business process. The path to which the process is directed is automatically selected depending on the conditions set in the <a href="360010366380.html" class="topiclink">connector settings</a>.</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 status </span><span style="font-family: Inter; font-weight: bold;">Approved with Comments</span><span style="font-family: Inter;">. Employees can approve a document that requires minor edits. The document will continue to move through the process according to the logic defined by outgoing connectors. In the approval sheet, the </span><span style="font-family: Inter; font-weight: bold;">Approved with Comments </span><span style="font-family: Inter;">status will appear next to the last name of the user who selected this decision.</span></p>
|
||
<p style="line-height: 1.20; margin: 7px 0 16px 0;"><span style="font-family: Inter;">The final status of the item will depend on whether it is approved or rejected by the approvers.</span></p>
|
||
<p style="line-height: 1.20; margin: 7px 0 16px 0;"><span style="font-family: Inter;">To configure custom statuses, fill out the fields:</span></p>
|
||
<p style="line-height: 1.20; margin: 7px 0 16px 0;"><img alt="approval-custom-statuses-1" width="876" height="263" style="margin:0;width:876px;height:263px;border:none" src="approval-custom-statuses-1.png"/></p>
|
||
<ul style="list-style-type:disc">
|
||
<li style="line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 16px;"><span style="font-family: Inter; font-weight: bold;">Approved/Rejected</span><span style="font-family: Inter;">. Enable the </span><span style="font-family: Inter; font-weight: bold;">Use custom status</span><span style="font-family: Inter;"> option if you want users to be able to provide an additional decision within the approval or rejection decisions.</span></li></ul>
|
||
<ul style="list-style-type:disc">
|
||
<li style="line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 16px;"><span style="font-family: Inter; font-weight: bold;">Button label in the task</span><span style="font-family: Inter; font-weight: bold; color: #ff0000;">*</span><span style="font-family: Inter;">. Enter the name for the button that the user will click to make a decision on the app item or file, for example, </span><span style="font-family: Inter; font-weight: bold;">Approve with Comments</span><span style="font-family: Inter;">. Buttons for additional decisions will be displayed next to the system ones in the approval task.</span></li></ul>
|
||
<p style="text-indent: -24px; line-height: 1.20; margin: 7px 0 16px 36px;"><img alt="approval-custom-statuses-2" width="750" height="385" style="margin:0;width:750px;height:385px;border:none" src="approval-custom-statuses-2.png"/></p>
|
||
<ul style="list-style-type:disc">
|
||
<li style="line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 16px;"><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 approval sheet after closing the task.</span></li></ul>
|
||
<p style="text-indent: -24px; line-height: 1.20; margin: 7px 0 16px 36px;"><img alt="approval-custom-statuses-3" width="262" height="226" style="margin:0;width:262px;height:226px;border:none" src="approval-custom-statuses-3.png"/></p>
|
||
<p style="line-height: 1.20; margin: 14px 0 0 0;"><span style="font-family: Inter;">The custom status will be shown in the approval sheet and will also be displayed alongside the system statuses when the sheet is exported.</span></p>
|
||
<p style="line-height: 1.20; margin: 14px 0 0 0;"><img alt="approval-custom-statuses-4" width="483" height="350" style="margin:0;width:483px;height:350px;border:none" src="approval-custom-statuses-4.png"/></p>
|
||
<h3 class="p_Heading3"><a id="signature" class="hmanchor"></a><span class="f_Heading3">Signature tab</span></h3>
|
||
<p style="line-height: 1.28; margin: 0 0 11px 0;">You can configure the use of an electronic signature at the approval step. In this case, the user clicks the <span style="font-weight: bold;">Approve</span> button in the received task and then enables the option of signing. In the opened window, the employee selects the objects to sign: attributes, file, and resolution. Thus, they make the resolution and confirm it with their electronic signature. The data about it are saved on the page of the signed document. For more information on how to perform such a task and where to view the details of the applied electronic signature, see the <a href="digital_signtature_in_apps.html" class="topiclink">Digital signature in apps</a> article.</p>
|
||
<p style="line-height: 1.20; margin: 7px 0 16px 0;">To make it possible to sign the approval object or decision, set the following parameters on the <span style="font-weight: bold;">Signature</span> tab:</p>
|
||
<p style="line-height: 1.20; margin: 7px 0 16px 0;"><img alt="approval_activity_07" width="909" height="331" style="margin:0;width:909px;height:331px;border:none" src="approval_activity_07.png"/></p>
|
||
<ul style="list-style-type:disc">
|
||
<li style="line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 16px;"><span style="font-weight: bold;">Enable signing</span>. You can disable signing by selecting <span style="font-weight: bold;">Do not use</span>. Then the user completing the task will only need to click <span style="font-weight: bold;">Approve</span> without having to sign the document.</li></ul>
|
||
<p style="line-height: 1.20; margin: 7px 0 16px 34px;">To make a signing pop-up appear when a user clicks <span style="font-weight: bold;">Approve</span>, select one of the following options:</p>
|
||
<ul style="list-style-type:disc"><ul style="list-style-type:circle">
|
||
<li style="line-height: 1.20;"><span style="font-weight: bold;">Optional</span>. The <span style="font-weight: bold;">Sign</span> option is disabled by default. Instead of <span style="font-weight: bold;">Next</span>, the user sees the <span style="font-weight: bold;">Approve</span> button. By clicking it, the user will approve the document without signing. At the same, time the user can set a checkbox and proceed to signing by clicking <span style="font-weight: bold;">Next</span>.</li><li style="line-height: 1.20;"><span style="font-weight: bold;">Preferred</span>. The <span style="font-weight: bold;">Sign</span> option is by default enabled but the user can disable it.</li><li style="line-height: 1.20;"><span style="font-weight: bold;">Required</span>. The <span style="font-weight: bold;">Sign</span> option is by default enabled, and the user cannot disable it. The user will not be able to close the task unless they move on to signing the attributes, document file, and solution.</li></ul></li></ul>
|
||
<ul style="list-style-type:disc">
|
||
<li style="line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 16px;"><span style="font-weight: bold;">Sign attributes</span>. Defines whether the approver needs to sign the app item attributes:</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-weight: bold;">Do not use</span>. The <span style="font-weight: bold;">Sign attributes</span> option will not be displayed. The user cannot sign the attributes.</li><li style="line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;"><span style="font-weight: bold;">Optional</span>. The default checkbox is not selected in the <span style="font-weight: bold;">Sign attributes</span> option, the user can enable it.</li><li style="line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;"><span style="font-weight: bold;">Preferred</span>. The default checkbox is selected in the <span style="font-weight: bold;">Sign attributes</span> option, the user can disable it.</li><li style="line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;"><span style="font-weight: bold;">Required</span>. The option is selected by default and cannot be disabled. The user cannot approve the document without singing its attributes.</li></ul></li></ul>
|
||
<ul style="list-style-type:disc">
|
||
<li style="line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;"><span style="font-weight: bold;">Sign File</span>. The settings for this field are the same as for <span style="font-weight: bold;">Sign attributes</span>.</li><li style="line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 16px;"><span style="font-weight: bold;">Sign Decision</span>. The settings for this field are the same as for <span style="font-weight: bold;">Sign attributes</span>.<a id="provider" class="hmanchor"></a> With this option, the user signs a text file generated by the system. It includes information about the approval task, the item sent for approval, the approver’s decision and comment, and the user who was approving the document.</li><li style="line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 16px;"><span style="font-weight: bold;">Provider</span>. Select the provider whose certificate will be used for signing. The list is formed from the <a href="electronic-signature.html" class="topiclink">digital signature provider</a> modules that are configured in <span style="font-weight: bold;">Administration > Modules > Digital Signature</span>. The user will not be able to change the selected value to another one. If the field is left blank, the provider can be selected at the moment of signing.</li></ul>
|
||
<h3 class="p_Heading3"><span class="f_Heading3">Substitutions tab</span></h3>
|
||
<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 approval 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="approval_activity_08" width="869" height="154" style="margin:0;width:869px;height:154px;border:none" src="approval_activity_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" 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 approval 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 agreed upon contains confidential data that should not be disclosed to third parties.</p>
|
||
<h3 class="p_Heading3"><a id="error-handling" class="hmanchor"></a><span class="f_Heading3">Error handling tab</span></h3>
|
||
<p style="line-height: 1.20; margin: 7px 0 16px 0;">During the process, an error may occur during the approval. For example, if a variable storing a file or app item for approval is not populated. You can define which path the business process will follow in this case and configure a notification:</p>
|
||
<p style="text-align: justify; line-height: 1.20; margin: 7px 0 16px 0;"><img alt="approval-14" width="658" height="355" style="margin:0;width:658px;height:355px;border:none" src="approval-14.png"/></p>
|
||
<ul style="list-style-type:disc">
|
||
<li style="line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 16px;"><span style="font-weight: bold;">Notification</span>. Enable the option and specify the users to whom notification of an error in the process will be sent. You can select a user, a user <span style="color: #0000ff;"><a href="360007146071.html" class="topiclink">group</a></span>, or an <span style="color: #0000ff;"><a href="360003861992.html" class="topiclink">org chart item</a></span>, and specify a <span style="color: #0000ff;"><a href="process_context.html" class="topiclink">context variable</a></span>, for example, the process initiator.</li><li style="line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 16px;"><span style="font-weight: bold;">Interrupt</span>. Enable the option and then specify in the <span style="font-weight: bold;">Transition</span> field which path the process will follow in case of an error. The connector specified in these settings is marked on the process diagram with the <img alt="error-connector-icon" width="23" height="25" style="margin:0;width:23px;height:25px;border:none" src="error-connector-icon.png"/><span class="f_ImageCaption"> </span>icon.</li></ul>
|
||
<p style="line-height: 1.20; margin: 7px 0 16px 0;">Please note that if you select a connector for which <span style="color: #0000ff;"><a href="360010366380.html#condition" class="topiclink">conditions are set</a></span>, they will be ignored when the process executes. The process will continue on the specified connector only in case of an error.</p>
|
||
<p style="line-height: 1.20; margin: 7px 0 16px 0;">When the settings are complete, click the <span style="font-weight: bold;">Save</span> button.</p>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Approval sheet</span></h2>
|
||
<p class="p_Normal">As soon as the process reaches the <span style="font-weight: bold;">Approval</span> activity, a notification about the assigned task appears in the <a href="360014162972.html" class="topiclink">#Activity stream</a> of the executors with a link to the file, document, or app item.</p>
|
||
<p class="p_Normal">An approval sheet is created on the object’s page, listing the employees assigned to the tasks. A question mark appears next to the user who has not yet reviewed the document.</p>
|
||
<p class="p_Normal">After the task is completed, the approval sheet is updated with the date, time, decision, any comments left, and an additional attached file explaining the employee’s decision. You can download an attached file by clicking on it in the sheet.</p>
|
||
<p style="text-align: justify; line-height: 1.20; margin: 7px 0 16px 0;"><img alt="approval-15" width="706" height="410" style="margin:0;width:706px;height:410px;border:none" src="approval-15.png"/></p>
|
||
<p style="line-height: 1.20; margin: 7px 0 16px 0;">If the document is sent to multiple executors, you can view the entire list by clicking <span style="font-weight: bold;">All users</span> in the approval sheet. In the opened window, users can be filtered by decision.</p>
|
||
<p style="text-align: justify; line-height: 1.20; margin: 19px 0 0 0;"><img alt="approval_sheets_03" width="381" height="277" style="margin:0;width:381px;height:277px;border:none" src="approval_sheets_03.png"/></p>
|
||
<p style="text-align: justify; line-height: 1.20; margin: 19px 0 0 0;">You can export the approval sheet 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 class="p_Normal">Read more about it in the <a href="approval-sheets.html" class="topiclink">Lists of informed users and approval sheets</a> article.</p>
|
||
|
||
<div class="bottom-nav">
|
||
|
||
<a id="prev-link" class="topic__navi_prev" href="send-for-information-use-case.html">
|
||
<span class="bottom-nav__arrow bottom-nav__arrow--prev"></span> <span
|
||
class="bottom-nav__link">send-for-information-use-case.html</span>
|
||
</a>
|
||
|
||
|
||
<a id="next-link" class="topic__navi_next" href="auto-approval.html">
|
||
<span class="bottom-nav__link">auto-approval.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>
|
||
<script type="text/javascript">
|
||
HMInitToggle('TOGGLE0186A1','hm.type','dropdown','hm.state','0');
|
||
HMInitToggle('TOGGLE0186A2','hm.type','dropdown','hm.state','0');
|
||
HMInitToggle('TOGGLE0186A3','hm.type','dropdown','hm.state','0');
|
||
</script>
|
||
</body>
|
||
|
||
</html>
|