This commit is contained in:
317
platform/360012495611.html
Normal file
317
platform/360012495611.html
Normal file
@ -0,0 +1,317 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Task</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="A task is performed by an employee as a part of a business process. Tasks are assigned automatically in the order they appear in the process diagram. They represent the steps..." />
|
||||
<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 / Task</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;">Task</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="task 13" width="97" height="73" style="margin:0;width:97px;height:73px;border:none" src="hmfile_hash_041e4e53.png"/>A<span style="font-weight: bold;"> task </span>is performed by an employee as a part of a business process. Tasks are assigned automatically in the order they appear in the process diagram. They represent the steps that the process participants have to complete to achieve a specific outcome. For example, in the order management process, employees will fill out the order form, check stock availability, pick and pack the order, etc.</p>
|
||||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;"><img alt="order_process_tasks" width="668" height="347" style="margin:0;width:668px;height:347px;border:none" src="order_process_tasks.png"/></p>
|
||||
<h2 class="p_Heading2" style="line-height: 1.20; margin: 19px 0 0 0;"><span class="f_Heading2" style="font-size: 24px;">Configure a user task</span></h2>
|
||||
<p class="p_Normal" style="line-height: 1.20; margin: 19px 0 0 0;">There are five tabs with settings: <a href="360012495611.html#general" class="topiclink">General</a>, <a href="360012495611.html#form" class="topiclink">Form</a>, <a href="360012495611.html#deadline" class="topiclink">Deadline</a>, <a href="360012495611.html#schedule_tab" class="topiclink">Schedule in Calendar</a>, <a href="360012495611.html#connectors" class="topiclink">Connectors</a>, and <a href="360012495611.html#substitutions" class="topiclink">Substitutions</a>.</p>
|
||||
<p class="p_Normal" style="line-height: 1.20; margin: 19px 0 0 0;">You can add a template for the task name, select multiple-instance execution, change the form, specify a deadline, etc.</p>
|
||||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">Double-click on the task shape in the process diagram to open the settings window.</p>
|
||||
<h2 class="p_Heading2"><a id="general" class="hmanchor"></a><span class="f_Heading2">General tab</span></h2>
|
||||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">The <span style="font-weight: bold;">General</span> tab contains the main information about the task: </p>
|
||||
<p class="p_Normal" style="line-height: 1.20; margin: 19px 0 0 0;"><img alt="task-1" width="655" height="570" style="margin:0;width:655px;height:570px;border:none" src="task-1.png"/></p>
|
||||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;"> </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>. Specify the name of the task on the process diagram. Keep it short so that the diagram is easy to read.</li></ul>
|
||||
<ul style="list-style-type:disc">
|
||||
<li style="line-height: 1.20;"><span style="font-weight: bold;">Task name</span>.<span style="font-weight: bold;"> </span>Select the <span style="font-weight: bold;">Generate name from template</span> option to include <a href="process_context.html" class="topiclink">context variables</a> into the name that the user will see in their task list and on the task page.<ul style="list-style-type:circle">
|
||||
<li style="line-height: 1.20;"><span style="font-weight: bold;">Template</span><span style="font-family: 'Times New Roman',Times,Georgia,serif; font-weight: bold; color: #ff0000;">*</span>.<span style="font-weight: bold;"> </span>Click the <span style="font-weight: bold;">{+}</span> icon in the right corner of the field and select a variable. You can also include <a href="360007679591.html#date_time" class="topiclink">conditions and functions</a> to generate the item name according to a template. This will allow you to create a more informative name for the task. If this option is not used, the text specified in the <span style="font-weight: bold;">Name</span><span style="font-family: 'Times New Roman',Times,Georgia,serif; font-weight: bold; color: #ff0000;">*</span> field will be displayed in the task list and on the form.</li></ul></li></ul>
|
||||
<ul style="list-style-type:disc">
|
||||
<li style="line-height: 1.20;"><span style="font-weight: bold;">Default block with form errors</span>. Enable the option to show a widget with a list of errors if there are errors in the fields of the task form. It is checked that the user specified the data correctly in accordance with the settings of the <a href="360009707032.html" class="topiclink">system data types</a>.</li><li style="line-height: 1.20;"><span style="font-weight: bold;">Notification</span>. When this option is selected, the executor will be notified in the #Activity stream about the assigned task. For the executor to additionally receive email notifications about new tasks, they need to enable this option in their <a href="360016398552.html#email-tab" class="topiclink">profile settings</a>.</li><li style="line-height: 1.20;"><span style="font-weight: bold;">Reassignment</span>.<span style="font-weight: bold;"> </span>Use this setting to allow or forbid an employee to reassign a task to other users. <a id="multi" class="hmanchor"></a></li><li style="line-height: 1.20;"><span style="font-weight: bold;">Perform on behalf of</span>.<span style="font-weight: bold;"> </span>Select who will be specified as the task author:</li></ul>
|
||||
<ul style="list-style-type:disc"><ul style="list-style-type:circle">
|
||||
<li style="line-height: 1.20;"><span style="font-weight: bold;">Current user</span>. The person who started the process instance is specified.</li><li style="line-height: 1.20;"><span style="font-weight: bold;">Context variable</span>.<span style="font-weight: bold;"> </span>Select a <a href="360009707032.html#users" class="topiclink">Users</a> variable of the <span style="font-weight: bold;">One</span> type from the process context. The employee stored in this variable will be specified as the task author. For example, it can be the user who belongs to the swimlane where the previous tasks are located.</li><li style="line-height: 1.20;"><span style="font-weight: bold;">System</span>. The task will be assigned by the user selected as the <a href="360006871932.html#supervisor" class="topiclink">system supervisor</a>.</li></ul>
|
||||
<li style="line-height: 1.20;"><span style="font-weight: bold;">Description</span>. Choose a <span style="font-weight: bold;">String</span> type variable from the process context to display an expanded description of the task. The value of the variable can be assigned within the <a href="type-script.html" class="topiclink">script written in TypeScript</a>. For example, you can place the <a href="360027203731.html" class="topiclink">Script</a> activity before the task in the process diagram. You need to add the variable with the description in the <a href="360012495611.html#form" class="topiclink">task form settings</a>.</li><li style="line-height: 1.20;"><span style="font-weight: bold;">Priority</span>. Select a <span style="font-weight: bold;">Number</span> type variable from the process context to display the urgency of the task. The variable can be filled with any numerical value within the <a href="type-script.html" class="topiclink">script written in TypeScript</a>.</li></ul>
|
||||
<ul style="list-style-type:disc">
|
||||
<li style="line-height: 1.20;"><span style="font-weight: bold;">Multiple instance task</span>.<span style="font-weight: bold;"> </span>This setting is available only if a swimlane represents a group of users or a department. The task will be assigned to all employees within the group or department, but the system’s behavior will depend on the option selected:</li></ul>
|
||||
<ul style="list-style-type:circle"><ul style="list-style-type:circle">
|
||||
<li style="line-height: 1.20;"><span style="font-weight: bold;">First Response</span>.<span style="font-weight: bold;"> </span>All the executors represented by the swimlane will be simultaneously assigned the task. Once somebody starts working on the task or marks it as completed, it will disappear from the task list of the other executors. You can additionally set up the task using one of the following options:</li></ul></li></ul>
|
||||
<ul style="list-style-type:disc"><ul style="list-style-type:circle"><ol style="list-style-type:decimal">
|
||||
<li value="1" style="line-height: 1.20;"><span style="font-weight: bold;">Hide the</span> <span style="font-weight: bold;">Start Task</span> button. In this case, only transition buttons will be displayed on the task form. Any employee from the group will be able to complete the task without actually starting working on it. This option is best for quick tasks.</li><li value="2" style="line-height: 1.20;"><span style="font-weight: bold;">Hide transition buttons</span>. There will only be one button displayed on the form: <span style="font-weight: bold;">Start Task</span>. After the employee clicks on it, the task will be assigned to them individually, and transition buttons will appear on the form.</li><li value="3" style="line-height: 1.20;"><span style="font-weight: bold;">Show all buttons</span>. The <span style="font-weight: bold;">Start Work</span> button and the transition buttons will be all displayed on the form. One of the employees from the group will be able to assign the task to themselves or mark it as completed right away.</li></ol></li></ul></li></ul>
|
||||
<ul style="list-style-type:circle"><ul style="list-style-type:circle">
|
||||
<li style="line-height: 1.20;"><a id="parallel" class="hmanchor"></a><span style="font-weight: bold;">Parallel</span>. The task will be assigned simultaneously to all executors specified in the swimlane settings. The process will continue only after all executors complete the task.</li><li style="line-height: 1.20;"><a id="sequential" class="hmanchor"></a><span style="font-weight: bold;">Sequential</span>. The task will be assigned to the executors of the swimlane one by one. The process will continue only after all executors complete the task.</li></ul></li></ul>
|
||||
<p style="line-height: 1.20;">If you select the <span style="font-weight: bold;">Parallel</span> or <span style="font-weight: bold;">Sequential</span> option, you need to:</p>
|
||||
<ul style="list-style-type:disc">
|
||||
<li style="text-align: justify; line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;">Specify the default connector on the <span style="font-weight: bold;">Connectors</span> tab.</li><li style="text-align: justify; line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;">Set the conditions in the connector settings. To learn more, see <a href="360015835331.html" class="topiclink">Connectors</a>.</li></ul>
|
||||
<p class="p_Normal">Note that in a dynamic swimlane, the tasks are assigned in the same order as the variable storing the executors was filled in. In a static swimlane, the order is random.</p>
|
||||
<p class="p_Normal">Take a look at the following examples to better understand how different types of multiple instance tasks work.</p>
|
||||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">начало примера</span></p>
|
||||
<p class="p_Normal">Example 1</p>
|
||||
<p class="p_Normal">Consider the operation of a warehouse. Any warehouse employee can prepare goods for shipping. It does not matter who exactly will be doing the packaging; what really matters is that the task is completed as fast as possible. If you select the <span style="font-weight: bold;">First Response</span> option, the task will be assigned to all the warehouse employees, and the person who is less busy at the moment will be able to immediately start working on it. As soon as BRIX that the employee has started the task (the employee needs to click on the confirmation button on the task page), the task will be canceled for other executors.</p>
|
||||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">конец примера</span></p>
|
||||
<p class="p_Normal"> </p>
|
||||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">начало примера</span></p>
|
||||
<p class="p_Normal">Example 2</p>
|
||||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">After a meeting, all the participants should receive the minutes of meeting. It is important that every employee who attended the meeting receives and reads this document, but the order in which people complete this does not matter. If you select the <span style="font-weight: bold;">Parallel</span> option, all meeting participants will be assigned the task <span style="font-weight: bold;">Read minutes of meetings</span>, and until each of them completes the task, the process will not continue.</p>
|
||||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">конец примера</span></p>
|
||||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">начало примера</span></p>
|
||||
<p class="p_Normal">Example 3</p>
|
||||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">Suppose that several managers need to read and approve a report before the process continues. If you select the <span style="font-weight: bold;">Sequential</span> option, the system will first assign the task of reviewing the report to one manager, and after he or she approves the document, to another. In the connectors settings, you can specify how the system should behave if someone from the approvers rejects the report. To find out how to do it, see <a href="360015835331.html" class="topiclink">Connectors</a>.</p>
|
||||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">конец примера</span></p>
|
||||
<h2 class="p_Heading2"><a id="form" class="hmanchor"></a><span class="f_Heading2">Form tab</span></h2>
|
||||
<p class="p_Normal" style="line-height: 1.20; margin: 19px 0 0 0;">On this tab, you can configure what the task form will look like.</p>
|
||||
<h3 class="p_Heading3" style="line-height: 1.20; margin: 19px 0 0 0;"><img alt="task-2" width="629" height="396" style="margin:0;width:629px;height:396px;border:none" src="task-2.png"/></h3>
|
||||
<p class="p_Normal"> </p>
|
||||
<p class="p_Normal" style="margin: 20px 0 0 0;">The <span style="font-weight: bold;">Context</span> column lists the fields added to the process context. To display them on the task page, drag them into the <span style="font-weight: bold;">Name on Form</span> column. Mark the required <img alt="required-fields-icon" width="21" height="20" style="margin:0;width:21px;height:20px;border:none" src="required-fields-icon.png"/> and read-only <img alt="read only" width="20" height="19" style="margin:0;width:20px;height:19px;border:none" src="hmfile_hash_96aa8b20.png"/> fields.</p>
|
||||
<p class="p_Normal" style="margin: 20px 0 0 0;">To create a new property, click the <span style="font-weight: bold;">+Add</span> button. The property will appear in the <span style="font-weight: bold;">Context</span> column as well as in the <a href="process_context.html" class="topiclink">process context</a>.</p>
|
||||
<h3 class="p_Heading3"><span class="f_Heading3">Property display settings</span></h3>
|
||||
<p class="p_Normal" style="margin: 20px 0 0 0;">To modify the settings of a field, click on it in the <span style="font-weight: bold;">Name on Form</span> column. You can edit the name and the tooltip text, make it required, and so on.</p>
|
||||
<p class="p_Normal" style="margin: 20px 0 0 0;">For the <a href="360009707032.html#app" class="topiclink">App</a> type field, depending on its settings, additional tabs are available:</p>
|
||||
<ul style="list-style-type:disc">
|
||||
<li style="line-height: 1.20;">If the <span style="font-weight: bold;">Read only</span> option is enabled, the <span style="font-weight: bold;">Properties</span> tab appears. </li></ul>
|
||||
<p style="line-height: 1.20; margin: 0 0 0 34px;"><img alt="task-3" width="599" height="375" style="margin:0;width:599px;height:375px;border:none" src="task-3.png"/></p>
|
||||
<p style="line-height: 1.20; margin: 0 0 0 34px;">On this tab, the <span style="font-weight: bold;">Context</span> column shows the properties of the selected app. You can add them to the task form by dragging them into the <span style="font-weight: bold;">Name on Form</span> column. These properties will be displayed on the task page under the app field.</p>
|
||||
<ul style="list-style-type:disc">
|
||||
<li style="line-height: 1.20;">If the <span style="font-weight: bold;">Read only</span> option is disabled, the <span style="font-weight: bold;">Add Item</span> tab is available.</li></ul>
|
||||
<p style="line-height: 1.20; margin: 0 0 0 34px;"><img alt="task-4" width="588" height="311" style="margin:0;width:588px;height:311px;border:none" src="task-4.png"/></p>
|
||||
<p style="line-height: 1.20; margin: 0 0 0 34px;">Here you can specify how the field will be filled.</p>
|
||||
<p class="p_Normal" style="margin: 0 0 0 34px;">To allow the user to select an existing app item, check the <span style="font-weight: bold;">Allow selecting from the list of existing items</span> option. You can <a href="360009923311.html#table-settings" class="topiclink">edit the item table</a> that will be displayed in the item selection window by clicking <span style="font-weight: bold;">Set up columns of the list</span>. In the window that opens, add fields to be used as table columns and configure sorting.</p>
|
||||
<p class="p_Normal" style="margin: 0 0 0 34px;">To enable the user to add a new item from the task page using the <span style="font-weight: bold;">+Create</span> button, enable the <span style="font-weight: bold;">Show a button that allows users to add new items</span> option.</p>
|
||||
<p class="p_Normal" style="margin: 20px 0 0 0;">If the field on the task form is editable, and the user doesn’t have the corresponding access to the app, they will automatically gain permission to fill out the field on the task form. The user doesn’t get direct access to the app and won’t be able to edit its fields after filling out the form.</p>
|
||||
<p class="p_Normal" style="margin: 20px 0 0 0;">You can modify the standard task form and create a template in the Low-code designer. Read more in the <a href="360012495991.html" class="topiclink">Forms tab</a> article.</p>
|
||||
<h2 class="p_Heading2"><a id="deadline" class="hmanchor"></a><span class="f_Heading2">Deadline tab</span></h2>
|
||||
<p class="p_Normal" style="line-height: 1.20; margin: 19px 0 0 0;">For some tasks, it is crucial to meet deadlines and stay on schedule. This is especially true for customer communications. Quickly handled requests and timely delivered goods provide your competitive advantage.</p>
|
||||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">On this tab, you can customize the deadlines for the task, as well as determine what happens if the task is not completed on time.</p>
|
||||
<h3 class="p_Heading3" style="line-height: 1.20; margin: 19px 0 0 0;"><img alt="task-5" width="516" height="266" style="margin:0;width:516px;height:266px;border:none" src="task-5.png"/></h3>
|
||||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">There are two ways to set the task deadline: </p>
|
||||
<ul style="list-style-type:disc">
|
||||
<li style="line-height: 1.20;"><a id="exact-time" class="hmanchor"></a><span style="font-weight: bold;">Exact time</span>. Specify how many minutes, hours, or days will be spent on the task. The deadline can be specified taking into account the settings of the <a href="360004890291.html" class="topiclink">current business calendar</a>. In this case, non-working hours are not included in the calculation of the due date.</li></ul>
|
||||
<ul style="list-style-type:disc">
|
||||
<li style="line-height: 1.20;"><span style="font-weight: bold;">Variable</span>. Sometimes it is impossible to determine how much time it requires to complete the task, but it is important that the work is done by a specific date. For example, an employee specifies the leave start and end dates, and the accountant must calculate the vacation pay and give the money 3 days before the employee takes their vacation. In this case, determine the task completion time as a context variable and specify it in the <span style="font-weight: bold;">Deadline</span> field.</li></ul>
|
||||
<ul style="list-style-type:disc"><ul style="list-style-type:circle">
|
||||
<li class="p_Normal"><span style="font-weight: bold;">Change time</span>. Use this option to add or subtract days, hours, or minutes from the time stored in the variable. Select <span style="font-weight: bold;">Add</span> or <span style="font-weight: bold;">Subtract</span>, and enter the number of days, hours, or minutes. The deadline will be changed accordingly. You can also limit the execution time considering the current business calendar in the same way as you do <a href="360012495611.html#exact-time" class="topiclink">when setting an exact time for the task deadline</a>.</li></ul></li></ul>
|
||||
<p style="line-height: 1.20; margin: 7px 0 7px 48px;">When specifying the deadline for a task, you can activate the following options:</p>
|
||||
<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;">According to the business calendar</span>. The deadline is calculated according to the business calendar and does not include non-working hours of the employee.</li><li style="line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;"><span style="font-weight: bold;">Calculate the duration of the work day using a constant</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 class="p_CodeExample" style="white-space: normal; page-break-inside: avoid;"><span class="f_CodeExample">начало внимание</span></p>
|
||||
<p class="p_Normal">If the calendar settings are edited, the process should be published again to apply the new work schedule to the due dates of the tasks.</p>
|
||||
<p class="p_CodeExample" style="white-space: normal; page-break-inside: avoid;"><span class="f_CodeExample">конец внимание</span></p>
|
||||
<p class="p_Normal"><a id="examples-deadline" class="hmanchor"></a><a class="dropdown-toggle" style="font-style: normal; font-weight: normal; color: #000000; background-color: transparent; text-decoration: none;" href="javascript:HMToggle('toggle','TOGGLE0186A1')">Examples of calculating the deadline for tasks</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"><ol style="list-style-type:decimal">
|
||||
<li value="1" style="line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;">Without taking the business calendar into account.</li></ol>
|
||||
<p class="p_Normal">When setting the due date without additional options, only the specified days, hours and minutes will be taken into account. A task can become overdue during the employee<span style="color: #202122; background-color: #ffffff;">’</span>s non-working hours. For example, a user works Monday through Friday from 9 AM to 6 PM. He is assigned a task for two days on Friday at 5 PM. This means that it will be considered overdue tomorrow at 12 AM. If you set a deadline of six hours, the task will be overdue today at 10 PM. A task is assigned to them with a two-day deadline at 5:00 PM on Friday. This means the task will be considered overdue at 12:00 AM on Sunday. If you set a deadline of six hours, the task will be overdue at 10:00 PM on the same day.</p>
|
||||
<ol style="list-style-type:decimal">
|
||||
<li value="2" class="p_Normal">According to the work calendar.</li></ol>
|
||||
<p class="p_Normal">Suppose you have assigned a task to the same user, also with a deadline of two days, at 5 PM on Friday, but taking into account their working calendar. In this case, the first day to work on the task will be Friday, and the deadline will be Monday at 6 PM. Saturday and Sunday are excluded from the calculation as weekends. If you set the deadline in hours, the task will be overdue on Monday at 3 PM. One work hour on Friday and five hours on Monday will be counted. The time between 1 PM and 2 PM is lunchtime.</p>
|
||||
<ol style="list-style-type:decimal">
|
||||
<li value="3" style="line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;">According to the duration of the workday.</li></ol>
|
||||
<p style="line-height: 1.20; margin: 7px 0 7px 96px;">When using the business calendar, you can also take into account the number of working hours per day by using the <span style="font-weight: bold;">Calculate the duration of the work day using a constant</span> option. Then, in our example, if the task duration is measured in days, it will be overdue on Tuesday at 5 PM. The standard number of working hours for the user is eight. On Friday they only have one hour to work on the task, Saturday and Sunday are days off, on Monday they have a full day of eight hours, and the missing seven hours are transferred to an extra day. The calculation of the task completion time in hours is not affected by using this option, because by default the employee<span style="font-size: 15px; font-weight: bold; color: #202122; background-color: #ffffff;">’</span>s working hours are taken into account.</p>
|
||||
<ol style="list-style-type:decimal">
|
||||
<li value="4" style="line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;">Calculate the duration of the workday with irregular working hours.</li></ol>
|
||||
<p class="p_Normal">If a user is assigned a calendar with a different number of working hours each day, the <span style="font-weight: bold;">Calculate the duration of the work day using a constant</span> option will take into account the time specified in the calendar settings in the <span style="font-weight: bold;">Standard work schedule</span> field. In this case a situation may occur when a task will be overdue during the employee’s non-working hours. Or its actual due date will be delayed by several days. When taking into account the working calendar with irregular working hours, we recommend setting the due date in hours and minutes without using the <span style="font-weight: bold;">Calculate the duration of the work day using a constant </span>option.</p>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</div>
|
||||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">Sometimes tasks are not completed on time despite the deadlines. In this case, control tools are needed to timely respond to the situation and take necessary measures.</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 specify the employees who will receive a notification if the executor does not meet the deadline. You can add a current user, a context variable (for example, the <span style="font-weight: bold;">Initiator</span>), a user group, or an <a href="360003861992.html" class="topiclink">org chart item</a> to determine the notification recipient.</p>
|
||||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;"><img alt="task 10" width="561" height="183" style="margin:0;width:561px;height:183px;border:none" src="hmfile_hash_9b6fde73.png"/></p>
|
||||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">In the <span style="font-weight: bold;">Interrupt</span> field, define the next process step in case the executor does not complete the task in time.</p>
|
||||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;"><img alt="task 11" width="535" height="181" style="margin:0;width:535px;height:181px;border:none" src="hmfile_hash_8162bb80.png"/></p>
|
||||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">The process will automatically go down the selected connector if the task deadline is not met and the executor does not confirm that the task has been completed. In the process diagram, such connector has a clock icon.</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;">The connector specified in the <span style="font-weight: bold;">Interrupt</span> field does not appear as a button on the task page.</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;"><img alt="360019646532-mceclip11" width="710" height="350" style="margin:0;width:710px;height:350px;border:none" src="360019646532-mceclip11.png"/></p>
|
||||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">For example, it may be very important for your company to meet the order processing deadlines. Warehouse employees must timely check stock availability and, if necessary, purchase the missing goods. This task is limited in time. If the employee doesn’t meet the deadline, the task is automatically assigned to the purchasing manager to deal with the situation.</p>
|
||||
<h2 class="p_Heading2"><a id="schedule_tab" class="hmanchor"></a><span class="f_Heading2">Schedule in Calendar tab</span></h2>
|
||||
<p class="p_Normal" style="margin: 7px 0 0 0;">This tab appears if a <a href="360012495611.html#deadline" class="topiclink">deadline</a> is set for the task. On this tab, you can enable the task to appear in the executor’s calendar.</p>
|
||||
<p class="p_Normal" style="margin: 7px 0 0 0;"><img alt="task-schedule-in-calendar" width="586" height="347" style="margin:0;width:586px;height:347px;border:none" src="task-schedule-in-calendar.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;">Start date</span><span style="font-family: Inter;">,</span><span style="font-family: Inter; font-weight: bold;"> End date</span><span style="font-family: Inter;">. Specify the variables of the </span><span style="font-family: Inter; font-weight: bold;">Date/Time</span><span style="font-family: Inter;"> type that store the start and end dates of the task from the process context. These variables determine the period during which the event will be displayed in the user’s calendar. Variable values can be assigned within a <a href="type-script.html" class="topiclink">script written in TypeScript</a>. For example, you can place the <a href="360027203731.html" class="topiclink">Script</a> activity before the task in the process diagram.</span></li></ul>
|
||||
<p style="line-height: 1.28; margin: 0 0 11px 34px;"><span style="font-family: Inter;">To avoid overloading the calendar, you can schedule a task in it only for specific days. For example, if the task’s duration is one week, you can display it in the calendar only for the last three days of that period. To do this:</span></p>
|
||||
<ol style="list-style-type:decimal">
|
||||
<li value="1" style="line-height: 1.28; margin-top: 0; margin-right: 0; margin-bottom: 11px;"><span style="font-family: Inter;">Add </span><span style="font-family: Inter; font-weight: bold;">Date/Time</span><span style="font-family: Inter;"> type variables to the process context, where the values for the task deadlines in the calendar will be recorded.</span></li><li value="2" style="line-height: 1.28; margin-top: 0; margin-right: 0; margin-bottom: 11px;"><span style="font-family: Inter;">On the process diagram, place a <a href="360027203731.html" class="topiclink">script</a> that calculates the values of these variables before the </span><span style="font-family: Inter; font-weight: bold;">Task</span><span style="font-family: Inter;"> item.</span></li><li value="3" style="line-height: 1.28; margin-top: 0; margin-right: 0; margin-bottom: 11px;"><span style="font-family: Inter;">On the current tab, link the </span><span style="font-family: Inter; font-weight: bold;">Start date</span><span style="font-family: Inter;"> and </span><span style="font-family: Inter; font-weight: bold;">End date </span><span style="font-family: Inter;">fields with these variables.</span></li></ol>
|
||||
<ol style="list-style-type:decimal" start="2"><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;">Place</span><span style="font-family: Inter;">. Choose a </span><span style="font-family: Inter; font-weight: bold;">String</span><span style="font-family: Inter;"> type variable where the event location is stored.</span></li><li style="line-height: 1.28; margin-top: 0; margin-right: 0; margin-bottom: 11px;"><span style="font-family: Inter; font-weight: bold;">External participants</span><span style="font-family: Inter;">.</span><span style="font-family: Inter; font-weight: bold;"> </span><span style="font-family: Inter;">Specify which clients from the <a href="360012584960.html" class="topiclink">Contacts</a> app will participate in the task. For this, select an </span><span style="font-family: Inter; font-weight: bold;">App</span><span style="font-family: Inter;"> type variable that stores the </span><span style="font-family: Inter; font-weight: bold;">Contacts</span><span style="font-family: Inter;"> app of the </span><span style="font-family: Inter; font-weight: bold;">CRM</span><span style="font-family: Inter;"> workspace and can store </span><span style="font-family: Inter; font-weight: bold;">Many</span><span style="font-family: Inter;"> values. You can choose an existing variable from the dropdown list or create a new one.</span></li></ul></li></ol>
|
||||
<h2 class="p_Heading2"><a id="connectors" class="hmanchor"></a><span class="f_Heading2">Connectors tab</span></h2>
|
||||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">On this tab, you can configure all the outgoing task <a href="360015835331.html" class="topiclink">connectors</a>: edit the name, add a confirmation box, change the button color, etc. To open these settings, click on the name of a connector. To learn more, see <a href="360015835331.html" class="topiclink">Connectors</a>.</p>
|
||||
<p class="p_Normal" style="line-height: 1.20; margin: 19px 0 0 0;"><img alt="task 12" width="553" height="236" style="margin:0;width:553px;height:236px;border:none" src="hmfile_hash_df4f268a.png"/></p>
|
||||
<p style="text-align: justify; line-height: 1.20; margin: 19px 0 0 0;">If you have selected <span style="color: #0000ff;"><a href="360012495611.html#parallel" class="topiclink">Parallel</a></span> or <span style="color: #0000ff;"><a href="360012495611.html#sequential" class="topiclink">Sequential</a></span> execution, additional settings will appear on the <span style="font-weight: bold;">Connectors</span> tab:</p>
|
||||
<ul style="list-style-type:disc">
|
||||
<li style="text-align: justify; line-height: 1.20; margin-top: 19px; margin-right: 0; margin-bottom: 0;"><span style="font-weight: bold;">Interrupt</span>. Enable the option so that when a user selects the connector, the task is canceled for the rest of the employees.</li><li style="text-align: justify; line-height: 1.20; margin-top: 19px; margin-right: 0; margin-bottom: 0;"><span style="font-weight: bold;">By Default</span>. Specify the connector by which the process will continue if none of the participants selects other options. To learn more about using this option, see the <span style="color: #0000ff;"><a href="connectors-use-cases.html" class="topiclink">Connector use cases</a></span> article.</li></ul>
|
||||
<h2 class="p_Heading2"><a id="substitutions" class="hmanchor"></a><span class="f_Heading2">Substitutions tab</span></h2>
|
||||
<p class="p_Normal" style="margin: 20px 0 20px 0;">On this tab, you can specify a variable that controls the reassignment of a task to an employee who <a href="360010244599.html" class="topiclink">substitutes</a> the primary executor.</p>
|
||||
<p class="p_Normal" style="margin: 20px 0 20px 0;"><img alt="task-substitutions" width="590" height="274" style="margin:0;width:590px;height:274px;border:none" src="task-substitutions.png"/></p>
|
||||
<p class="p_Normal" style="margin: 20px 0 0 0;">In the <span style="font-weight: bold;">Ignore substitution</span> field, specify a <a href="360009707032.html#yes-no-switch" class="topiclink">Yes/No switch</a> variable from the business process context.</p>
|
||||
<p class="p_Normal" style="margin: 20px 0 0 0;">If the variable is set to <span style="font-weight: bold;">Yes</span>, the task will go to the originally specified executor, and if set to <span style="font-weight: bold;">No</span>, it will go to the substituting employee. The value of the variable can be changed during the business process, for example, by presenting the variable on the form of another task or using <a href="360027203731.html" class="topiclink">scripts</a>.</p>
|
||||
<p class="p_Normal" style="margin: 20px 0 0 0;">For instance, ignoring substitution can be useful if the task contains confidential data that should not be shared with third parties.</p>
|
||||
|
||||
<div class="bottom-nav">
|
||||
|
||||
<a id="prev-link" class="topic__navi_prev" href="connectors-use-cases.html">
|
||||
<span class="bottom-nav__arrow bottom-nav__arrow--prev"></span> <span
|
||||
class="bottom-nav__link">connectors-use-cases.html</span>
|
||||
</a>
|
||||
|
||||
|
||||
<a id="next-link" class="topic__navi_next" href="360012495791.html">
|
||||
<span class="bottom-nav__link">360012495791.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');
|
||||
</script>
|
||||
</body>
|
||||
|
||||
</html>
|
Reference in New Issue
Block a user