248 lines
34 KiB
HTML
248 lines
34 KiB
HTML
<!DOCTYPE html>
|
||
<html lang="en">
|
||
|
||
<head>
|
||
<title>Events</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="Events affect the course of the process or process stages. They can start, pause, or end the flow of the process. On a process diagram, events are represented by circles. There..." />
|
||
<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 / Events</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;">Events</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;">Events affect the course of the process or process stages. They can start, pause, or end the flow of the process. On a process diagram, events are represented by circles. There are three main types of events: <span style="font-weight: bold;">start</span>, <span style="font-weight: bold;">intermediate</span>,<span style="font-weight: bold;"> </span>and <span style="font-weight: bold;">end</span>.</p>
|
||
<h2 class="p_Heading2" style="line-height: 1.20; margin: 19px 0 0 0;"><span class="f_Heading2" style="font-size: 24px;">Start event </span></h2>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 19px 0 0 0;"><img alt="1.png" title="1.png" width="53" height="57" style="float:left;margin:0 15px 0 3px;width:53px;height:57px;border:none" src="360011749271-1.png"/></p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;"><span style="font-family: 'Segoe UI',Tahoma,Verdana,Arial,sans-serif; color: #374151;">A </span><span style="font-family: 'Segoe UI',Tahoma,Verdana,Arial,sans-serif; font-weight: bold; color: #374151;">start event</span><span style="font-family: 'Segoe UI',Tahoma,Verdana,Arial,sans-serif; color: #374151;"> initiates the launch of a process and indicates where it begins. A process can have only one start event.</span></p>
|
||
<p class="p_Normal" style="margin: 20px 0 0 0;"><span style="font-family: 'Segoe UI',Tahoma,Verdana,Arial,sans-serif; color: #374151;">In the start event, you can configure the process execution parameters: enable scheduling and set a template for the naming of instances. The specified parameters will also be displayed in the <a href="360012263052.html" class="topiclink">process settings</a>.</span></p>
|
||
<p class="p_Normal" style="margin: 20px 0 0 0;"><span style="font-family: 'Segoe UI',Tahoma,Verdana,Arial,sans-serif; color: #374151;">Additionally, the start event determines the process start form. By default, when starting a process manually, the user sees a window with a button to start the process without additional data. The button</span><span style="font-size: 15px; font-family: Inter;">’</span><span style="font-family: 'Segoe UI',Tahoma,Verdana,Arial,sans-serif; color: #374151;">s name matches the label of the transition that connects the start event to the next activity.</span></p>
|
||
<p class="p_Normal" style="margin: 20px 0 0 0;"><span style="font-family: 'Segoe UI',Tahoma,Verdana,Arial,sans-serif; color: #374151;">You can customize the start form: place properties from the process context on it and set the <a href="360029250931.html" class="topiclink">form template</a>. After that users can fill in fields and immediately pass the necessary values to the process.</span></p>
|
||
<p class="p_Normal" style="margin: 20px 0 0 0;"><span style="font-family: 'Segoe UI',Tahoma,Verdana,Arial,sans-serif; color: #374151;">For example, for the </span><span style="font-family: 'Segoe UI',Tahoma,Verdana,Arial,sans-serif; font-weight: bold; color: #374151;">Leave request</span><span style="font-family: 'Segoe UI',Tahoma,Verdana,Arial,sans-serif; color: #374151;"> process, a start form is configured. The user clicks the process start button and sees a window with fields added to the form. After entering the vacation information, the employee clicks the </span><span style="font-family: 'Segoe UI',Tahoma,Verdana,Arial,sans-serif; font-weight: bold; color: #374151;">Start</span><span style="font-family: 'Segoe UI',Tahoma,Verdana,Arial,sans-serif; color: #374151;"> button. The vacation approval process instance launches with the entered data.</span></p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;"><img alt="events 4" width="645" height="449" style="margin:0;width:645px;height:449px;border:none" src="hmfile_hash_d503324c.png"/></p>
|
||
<p class="p_Normal" style="margin: 20px 0 0 0;"><span style="font-family: 'Segoe UI',Tahoma,Verdana,Arial,sans-serif; color: #374151;">To open the start event settings, double-click on the event graphic element in the process diagram.</span></p>
|
||
<h3 class="p_Heading3" style="line-height: 1.20; margin: 19px 0 0 0;"><span class="f_Heading3" style="font-size: 19px;">General tab</span></h3>
|
||
<p class="p_Normal">This tab includes general information about the process:</p>
|
||
<h3 class="p_Heading3" style="line-height: 1.20; margin: 19px 0 0 0;"><img alt="events-1" width="1012" height="441" style="margin:0;width:1012px;height:441px;border:none" src="events-1.png"/></h3>
|
||
<ul style="list-style-type:disc">
|
||
<li style="line-height: 1.20;"><span style="font-weight: bold;">Instructions</span>. <span style="font-family: 'Segoe UI',Tahoma,Verdana,Arial,sans-serif; color: #374151;">A brief description of the process or a guide for filling out the fields, which is displayed on the start form.</span></li></ul>
|
||
<ul style="list-style-type:disc">
|
||
<li style="line-height: 1.20;"><span style="font-weight: bold;">Notification on process start</span>. <span style="font-family: 'Segoe UI',Tahoma,Verdana,Arial,sans-serif; color: #374151;">A notification that the user will see at the top of the screen after starting the process.</span></li></ul>
|
||
<h3 class="p_Heading3" style="line-height: 1.20; margin: 19px 0 0 0;"><a id="form_tab" class="hmanchor"></a><span class="f_Heading3" style="font-size: 19px;">Form tab</span></h3>
|
||
<p class="p_Normal"><span style="font-family: 'Segoe UI',Tahoma,Verdana,Arial,sans-serif; color: #374151;">On this tab, you can configure what the start form includes. Set up the form in the same way as for the <a href="360012495611.html#form" class="topiclink">Task</a> activity.</span></p>
|
||
<p class="p_Normal"><span style="font-family: 'Segoe UI',Tahoma,Verdana,Arial,sans-serif; color: #374151;">The </span><span style="font-family: 'Segoe UI',Tahoma,Verdana,Arial,sans-serif; font-weight: bold; color: #374151;">Context</span><span style="font-family: 'Segoe UI',Tahoma,Verdana,Arial,sans-serif; color: #374151;"> column displays all variables from the process context. Drag the properties that will be displayed on the start form into the </span><span style="font-family: 'Segoe UI',Tahoma,Verdana,Arial,sans-serif; font-weight: bold; color: #374151;">Name on form</span><span style="font-family: 'Segoe UI',Tahoma,Verdana,Arial,sans-serif; color: #374151;"> column. To create a new variable, click the </span><span style="font-family: 'Segoe UI',Tahoma,Verdana,Arial,sans-serif; font-weight: bold; color: #374151;">+ Add</span><span style="font-family: 'Segoe UI',Tahoma,Verdana,Arial,sans-serif; color: #374151;"> button. The variable will appear in the process context, and you can use it in other activities.</span></p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 19px 0 0 0;"><img alt="events-2" width="962" height="513" style="margin:0;width:962px;height:513px;border:none" src="events-2.png"/></p>
|
||
<p class="p_Normal" style="margin: 20px 0 0 0;"><span style="font-family: 'Segoe UI',Tahoma,Verdana,Arial,sans-serif; color: #374151;">Specify which variables are required </span><img alt="required-star-red" width="20" height="20" style="margin:0;width:20px;height:20px;border:none" src="required-star-red.png"/><span style="font-family: 'Segoe UI',Tahoma,Verdana,Arial,sans-serif; color: #374151;"> and which are read only </span><img alt="read only" width="20" height="19" style="margin:0;width:20px;height:19px;border:none" src="hmfile_hash_96aa8b20.png"/><span style="font-family: 'Segoe UI',Tahoma,Verdana,Arial,sans-serif; color: #374151;">. Note that when using the </span><span style="font-family: 'Segoe UI',Tahoma,Verdana,Arial,sans-serif; font-weight: bold; color: #374151;">Read only</span><span style="font-family: 'Segoe UI',Tahoma,Verdana,Arial,sans-serif; color: #374151;"> option, only the field storing the item that the process is started for will be filled with a value.</span></p>
|
||
<p class="p_Normal" style="margin: 20px 0 0 0;"><span style="font-family: 'Segoe UI',Tahoma,Verdana,Arial,sans-serif; color: #374151;">If process instance names are <a href="360012496011.html#name_template" class="topiclink">generated by template</a>, the <a href="process_context.html#name-system-field" class="topiclink">Name</a> field will not be displayed on the start event form even if it is added.</span></p>
|
||
<p class="p_Normal" style="margin: 20px 0 0 0;"><span style="font-family: 'Segoe UI',Tahoma,Verdana,Arial,sans-serif; color: #374151;">To configure the form, you can also use a ready-made form template or create a new one. For more information on creating form templates, read the <a href="360012495991.html" class="topiclink">Forms tab</a> article.</span></p>
|
||
<h3 class="p_Heading3"><a id="schedule" class="hmanchor"></a><span class="f_Heading3">Start Settings tab</span></h3>
|
||
<p class="p_Normal">On this tab, you can configure how to start the process. You can set up a scheduled start event taking into account the <a href="360004890291.html" class="topiclink">current business calendar</a>. </p>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">начало внимание</span></p>
|
||
<p class="p_Normal">If the work schedule has changed, processes started based on non-working hours should be published again.</p>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">конец внимание</span></p>
|
||
<h3 class="p_Heading3" style="line-height: 1.20; margin: 19px 0 0 0;"><img alt="events-3" width="976" height="631" style="margin:0;width:976px;height:631px;border:none" src="events-3.png"/></h3>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 19px 0 0 0;"><span style="font-weight: bold;">Create button</span>.<span style="font-weight: bold;"> </span>If you select this option, an employee will be able to start the process from the main page of the system by clicking the <span style="font-weight: bold;">Create</span> button.</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;"><span style="font-weight: bold;">Schedule</span>. This option allows you to run the process on a schedule.</p>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal" style="line-height: 1.20; margin-top: 14px; margin-right: 0; margin-bottom: 0;"><span style="font-weight: bold;">Start process</span>. In this field, the current date and time are filled out automatically. If the process is run repeatedly in certain periods of time, this data is used to calculate each next run.</li><li class="p_Normal" style="line-height: 1.20; margin-top: 14px; margin-right: 0; margin-bottom: 0;"><span style="font-weight: bold;">End</span>. The date and time after which the system will no longer initiate the process.</li><li class="p_Normal" style="line-height: 1.20; margin-top: 14px; margin-right: 0; margin-bottom: 0;"><span style="font-weight: bold;">Repeat</span>. Specify how often the process will be launched:<ul style="list-style-type:circle">
|
||
<li style="line-height: 1.20;"><span style="font-weight: bold;">Once</span>.<span style="font-weight: bold;"> </span>The process will be started once. If you select the additional option <span style="font-weight: bold;">Repeat throughout the day</span>, the system will repeatedly re-initiate the process during the day in certain periods of time.</li><li style="line-height: 1.20;"><span style="font-weight: bold;">Day</span>.<span style="font-weight: bold;"> </span>Select this option if you want to run the process every day or every few days. In the <span style="font-weight: bold;">Repeat every X days</span> field you can specify how often the process must be started. In addition, you can customize the behavior of the system if the event falls on a non-working day.</li><li style="line-height: 1.20;"><span style="font-weight: bold;">Week</span>.<span style="font-weight: bold;"> </span>Select this option if you want to run the process every week or every few days. If necessary, select the day of the week when the process should start. In addition, you can specify how the system must behave if the start falls on a non-working day.<br />
|
||
For example, the weekly reporting process will run every week on Mondays at 11 o'clock in the morning. If the start falls on a non-working day, the process will not be launched this week.<br />
|
||
<img alt="start_event_week" width="827" height="244" style="margin:0;width:827px;height:244px;border:none" src="start_event_week.png"/></li><li style="line-height: 1.20;"><span style="font-weight: bold;">Month</span>. The process will start every month or every few months. Specify days when the system must initiate the process.<br />
|
||
For example, the payroll process will run on the 10th and 20th day of the month. If these dates fall on a non-working day, then the process start will be postponed until the nearest working day.<br />
|
||
<img alt="start_event_month" width="863" height="194" style="margin:0;width:863px;height:194px;border:none" src="start_event_month.png"/></li></ul>
|
||
<li class="p_Normal" style="line-height: 1.20; margin-top: 14px; margin-right: 0; margin-bottom: 0;"><span style="font-weight: bold;">Only on weekdays</span>. This option allows you to configure the behavior of the system if the start falls on a non-working day.<ul style="list-style-type:circle">
|
||
<li style="line-height: 1.20;"><span style="font-weight: bold;">Skip</span>. The process started will be skipped.</li><li style="line-height: 1.20;"><span style="font-weight: bold;">Previous</span>. The process will be started the previous working day.</li><li style="line-height: 1.20;"><span style="font-weight: bold;">Next</span>.<span style="font-weight: bold;"> </span>The process will be started the next working day.</li><li style="line-height: 1.20;"><span style="font-weight: bold;">Nearest working day</span>.<span style="font-weight: bold;"> </span>The process will be started on the nearest working day.</li></ul>
|
||
<li class="p_Normal" style="line-height: 1.20; margin-top: 14px; margin-right: 0; margin-bottom: 0;"><span style="font-weight: bold;">If overdue</span>. This options determines the behavior of the system if the server was unavailable at the moment the process start was scheduled.</li></ul>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">Note that if a process start is scheduled, the<a href="360012496011.html#form_tab" class="topiclink"> start event form</a> must be empty.</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;"><img alt="events-empty-form" width="665" height="442" style="margin:0;width:665px;height:442px;border:none" src="events-empty-form.png"/></p>
|
||
<h3 class="p_Heading3" style="line-height: 1.20; margin: 19px 0 0 0;"><a id="name_template" class="hmanchor"></a><span class="f_Heading3" style="font-size: 19px;">Name tab</span></h3>
|
||
<p class="p_Normal"><img alt="events-4" width="1005" height="448" style="margin:0;width:1005px;height:448px;border:none" src="events-4.png"/></p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 19px 0 0 0;">On this tab, you can add a name template for the process instance. You won’t have to enter the name manually every time you start the process.</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">In the <span style="font-weight: bold;">Template</span><span style="font-weight: bold; color: #ff0000;">*</span> field, enter a name for the process instance, if necessary, add a context variable, for example, the initiator<span style="font-size: 15px; font-family: Inter;">’</span>s full name. The list of available variables is opened by clicking on the <span style="font-weight: bold;">+</span> icon in the right corner of the field.</p>
|
||
<h2 class="p_Heading2" style="line-height: 1.20; margin: 19px 0 0 0;"><a id="timer" class="hmanchor"></a><span class="f_Heading2" style="font-size: 24px;">Timer intermediate event </span></h2>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 19px 0 0 0;"><img alt="3.png" title="3.png" width="53" height="57" style="float:left;margin:0 15px 0 3px;width:53px;height:57px;border:none" src="360011769352-3.png"/></p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">A <span style="font-weight: bold;">timer</span> intermediate event represents a delay in the process for a specific period of time. The number of intermediate events is not limited, they can be located anywhere in the process between the start and end events.</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">In the event settings, you can change its name and specify how the go-off time is calculated.</p>
|
||
<h3 class="p_Heading3" style="line-height: 1.20; margin: 19px 0 0 0;"><span class="f_Heading3" style="font-size: 19px;">Exact time</span></h3>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">If you select this option, you can specify the exact time, after which the process execution will continue. For example, the process will wait for a customer response for two days. Once this period is over, the timer goes off and the process continues.</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">You can specify a deadline according to the <a href="360004890291.html" class="topiclink">current business calendar</a>. In this case, non-working hours will not be included in the waiting period. For example, if a timer start falls on a weekend, the process will continue on the next business day. If the business calendar settings change, you should restart the timer and republish the process again to take into account a new work schedule.</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 19px 0 0 0;"><img alt="events 7" width="837" height="299" style="margin:0;width:837px;height:299px;border:none" src="hmfile_hash_c78c11dc.png"/> </p>
|
||
<h3 class="p_Heading3" style="line-height: 1.20; margin: 19px 0 0 0;"><span class="f_Heading3" style="font-size: 19px;">Variable</span></h3>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">You can specify the day and the time when the process execution will continue using a context variable.</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 19px 0 0 0;"><img alt="events-6" width="802" height="450" style="margin:0;width:802px;height:450px;border:none" src="events-6.png"/></p>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal" style="line-height: 1.20; margin-top: 14px; margin-right: 0; margin-bottom: 0;"><span style="font-weight: bold;">Due date</span>. Select a variable from the list or add a new variable. To do this, click <span style="font-weight: bold;">Create New Variable</span>. In the window that opens, fill in all the required fields: <span style="font-weight: bold;">Display Name</span><span style="font-weight: bold; color: #ff0000;">*</span> and <span style="font-weight: bold;">Property Name</span><span style="font-weight: bold; color: #ff0000;">*</span>.<br />
|
||
When creating a property, you cannot change the type because timer events always use <span style="font-weight: bold;">Date/Time</span> type variables. However, you can specify additional parameters:</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;">Set current date and time</span>.<span style="font-weight: bold;"> </span>The current date and time will be inserted in the field automatically (according to the time zone of the user).</li><li style="line-height: 1.20;"><span style="font-weight: bold;">Do not require to specify time</span>.<span style="font-weight: bold;"> </span>When filling in the<span style="font-weight: bold;"> Date/Time</span> variable, the user is not required to specify the time.</li></ul></li></ul>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal" style="margin-top: 20px; margin-right: 0; margin-bottom: 0;"><span style="font-family: 'Segoe UI',Tahoma,Verdana,Arial,sans-serif; font-weight: bold; color: #374151;">Change time</span><span style="font-family: 'Segoe UI',Tahoma,Verdana,Arial,sans-serif; color: #374151;">. This option allows you to add or subtract days, hours, and minutes to the time stored in the variable. Select the </span><span style="font-family: 'Segoe UI',Tahoma,Verdana,Arial,sans-serif; font-weight: bold; color: #374151;">Add</span><span style="font-family: 'Segoe UI',Tahoma,Verdana,Arial,sans-serif; color: #374151;"> or </span><span style="font-family: 'Segoe UI',Tahoma,Verdana,Arial,sans-serif; font-weight: bold; color: #374151;">Subtract</span><span style="font-family: 'Segoe UI',Tahoma,Verdana,Arial,sans-serif; color: #374151;"> option, enter the adjustment amount, and specify whether the business calendar needs to be used. The deadline after which the process will resume will increase or decrease by the amount of time you specify.</span></li></ul>
|
||
<h2 class="p_Heading2" style="line-height: 1.20; margin: 19px 0 0 0;"><a id="end-event" class="hmanchor"></a><span class="f_Heading2" style="font-size: 24px;">End event</span><span class="f_Heading2" style="font-size: 13px; font-family: Verdana,Geneva,Arial,sans-serif;"> </span></h2>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 19px 0 0 0;"><img alt="2.png" title="2.png" width="53" height="57" style="float:left;margin:0 15px 0 3px;width:53px;height:57px;border:none" src="360011749291-2.png"/>An <span style="font-weight: bold;">end event</span> indicates where a process or one of its branches ends. End events cannot have outgoing connectors. The number of such events in the process is unlimited. To improve the readability of the process diagram, you can specify the name of the end event in its settings.</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;"><img alt="events_3" width="672" height="391" style="margin:0;width:672px;height:391px;border:none" src="events_3.png"/></p>
|
||
|
||
<div class="bottom-nav">
|
||
|
||
<a id="prev-link" class="topic__navi_prev" href="360012495911.html">
|
||
<span class="bottom-nav__arrow bottom-nav__arrow--prev"></span> <span
|
||
class="bottom-nav__link">360012495911.html</span>
|
||
</a>
|
||
|
||
|
||
<a id="next-link" class="topic__navi_next" href="360012263032.html">
|
||
<span class="bottom-nav__link">360012263032.html</span> <span
|
||
class="bottom-nav__arrow bottom-nav__arrow--next"></span>
|
||
</a>
|
||
|
||
</div>
|
||
<!-- добавляет на страницу строку блок Была ли статья полезной? -->
|
||
<div class="feedback" id="feedback"><div class="feedback-help"><span><b>Was this helpful?</b></span><form action="" method="POST" class="feedback-form" id="feedback-form"><div class="feedback__popup feedback__popup-response" id="feedback__popup_thx" style="display: none;">Thanks for your feedback!</div><div class="feedback__popup" id="feedback__popup_why" style="display: none;"><div class="feedback__popup-header">Please specify why:</div><input type="radio" name="category" id="bad_recommendation" value="bad_recommendation"><label for="bad_recommendation">Recommendations did not help me</label><input type="radio" name="category" id="difficult_text" value="difficult_text"><label for="difficult_text">Article is hard to understand</label><input type="radio" name="category" id="no_answer" value="no_answer"><label for="no_answer">Didn`t answer my question</label><input type="radio" name="category" id="bad_header" value="bad_header"><label for="bad_header">Content does not match the topic</label><input type="radio" name="category" id="other_reason" value="other_reason"><label for="other_reason">Other</label></div><div class="feedback__popup" id="feedback__popup-other" style="display: none;"><div class="feedback__popup-header">How we can improve it?</div><textarea class="feedback__textarea" name="other" id=""></textarea><input type="submit" class="feedback__other-btn" value="Submit"></div><div class="feedback-form__btn-group"><input type="radio" name="useful" id="feedback__useful_yes" value="true"><label for="feedback__useful_yes"><img src="like.svg" class="small-img" alt="like"><spanclass="feedback-form__btn-group_yes-btn">Yes</spanclass="feedback-form__btn-group_yes-btn"></label><input type="radio" name="useful" id="feedback__useful_no" value="false"><label for="feedback__useful_no"><img src="dislike.svg" class="small-img" alt="dislike"><spanclass="feedback-form__btn-group_no-btn">No</spanclass="feedback-form__btn-group_no-btn"></label></div><select name="category"><option disabled="">Please specify why</option><option value="bad_recommendation" selected="">Recommendations did not help me</option><option value="difficult_text">Article is hard to understand</option><option value="no_answer">Didn`t answer my question</option><option value="bad_header">Content does not match the topic</option><option value="other_reason">Other</option></select><input type="submit"></form></div><div class="found_typo"><p style="margin: 0px; margin-top: 16px !important;"><span><b>Found a typo?</b></span> Select it and press <i>Ctrl+Enter</i> to send us feedback</p></div></div>
|
||
|
||
</section>
|
||
</div>
|
||
<aside class="article__sidebar" style="display:none">
|
||
<input type="checkbox" />
|
||
<div class="article__arrow"></div>
|
||
<div class="table-of-contents elma365-right" id="toc2Content">
|
||
<h3 class="h3-toc">In this topic</h3>
|
||
<nav id="toc2"></nav>
|
||
</div>
|
||
</aside>
|
||
</div>
|
||
</article>
|
||
</main>
|
||
<footer class="footer">
|
||
<div class="footer-container">
|
||
<div class="footer-mobile">
|
||
|
||
<ul class="footer-mobile__list"><li><a href="https://brix365.com/en/" target="_blank">BRIX</a></li><li><a href="https://tssdk.brix365.com/en/latest/" target="_blank">SDK</a></li><li><a href="https://api.brix365.com/en/" target="_blank">API</a></li></ul><ul class="footer-mobile__list"><li><a href="https://brix365.com/en/help/platform/get-trial.html">Platform</a></li><li><a href="https://brix365.com/en/help/ecm/ecm-functions.html">ECM</a></li><li><a href="https://brix365.com/en/help/service/service-functions.html">Service</a></li><li><a href="https://brix365.com/en/help/projects/projects-functions.html">Projects</a></li></ul>
|
||
|
||
|
||
</div>
|
||
<div class="footer-wrap">
|
||
|
||
<div><span class="mobile-question-popup">Send feedback</span><form method="POST" action class="question__popup question-xs" id="question__popup"><div class="question-wrap"><span class="close"></span><span class="title">Ask a question</span><label for="help_question" style="display: none;"></label><textarea name="help_question" id="help_question"></textarea><input type="submit" value="Send"></div></form><div class="hidden fade-in question-success-xs">Sent</div></div>
|
||
|
||
<div class="footer-flex-b">
|
||
<span class="footer-copy">© 2025 BRIX</span>
|
||
<ul class="footer-list">
|
||
|
||
<li class="footer-item">
|
||
<a href="#" class="arrow-top" style="display: block;"></a>
|
||
</li>
|
||
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
</footer>
|
||
<iframe name="hmnavigation" style="display:none!important"></iframe>
|
||
<script src="./jquery-ui.js"></script>
|
||
<!--script src="//cdn.jsdelivr.net/npm/featherlight@1.7.14/release/featherlight.min.js" type="text/javascript" charset="utf-8"></script-->
|
||
<script src="./jquery.tocify.min.js"></script>
|
||
<script src="./TypoReporter.min.js"></script>
|
||
<script src="./google-search.js"></script>
|
||
<script src="./main.js"></script>
|
||
</body>
|
||
|
||
</html>
|