284 lines
33 KiB
HTML
284 lines
33 KiB
HTML
<!DOCTYPE html>
|
||
<html lang="en">
|
||
|
||
<head>
|
||
<title>Binding and other aspects of business process activities</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="In a custom module, you can create a business process activity. If you place it on the process flow chart, it will perform a certain operation: a customized script, a process..." />
|
||
<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><a href="360024498352.html">Modules</a> > <a href="extentions.html">Custom modules</a> > <a href="extention-activities.html">Business process activities</a> / Binding and other aspects of business process activities</p>
|
||
</div>
|
||
|
||
</div>
|
||
<div class="topic__title"><h1 class="p_Heading1"><span class="f_Heading1">Binding and other aspects of business process activities</span></h1>
|
||
</div>
|
||
|
||
</header>
|
||
<section class="article__content">
|
||
<div class="scroll-top-inner">
|
||
<a href="#h1-article" class="scroll-top"></a>
|
||
</div>
|
||
<!-- Placeholder for topic body. -->
|
||
<p style="line-height: 1.20; margin: 7px 0 16px 0;"><span style="font-size: 13px; font-family: Inter; color: #394149;">In a custom module, you can create a business process activity. If you place it on the process flow chart, it will perform a certain operation: a customized script, a process call, or a delegated activity. When the module is enabled, the graphical element appears in the business process designer on the </span><span style="font-size: 13px; font-family: Inter; font-weight: bold; color: #394149;">Integrations</span><span style="font-size: 13px; font-family: Inter; color: #394149;"> tab and can be used in any custom process. The activity configured in the graphical element works only with the module enabled. If you run a process instance with the module disabled, the user will receive an error notification at the activity execution stage.</span></p>
|
||
<p style="line-height: 1.20; margin: 7px 0 16px 0;"><span style="font-size: 13px; font-family: Inter; color: #394149;">Keep in mind that:</span></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-size: 13px; font-family: Inter; color: #394149;">The attributes of the graphical element in which the activity is configured are <a href="activities-features.html#binding" class="topiclink">mapped with the context variables of the process</a></span></li><li style="line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 16px;"><span style="font-size: 13px; font-family: Inter; color: #394149;">A graphical element of the </span><span style="font-size: 13px; font-family: Inter; font-weight: bold; color: #394149;">Call Process</span><span style="font-size: 13px; font-family: Inter; color: #394149;"> type is <a href="activities-features.html#call-vs-start-process" class="topiclink">different</a> from a graphical element of the </span><span style="font-size: 13px; font-family: Inter; font-weight: bold; color: #394149;">Start Process</span><span style="font-size: 13px; font-family: Inter; color: #394149;"> type</span></li><li style="line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 16px;"><span style="font-size: 13px; font-family: Inter; color: #394149;">Activities created in the module <a href="activities-features.html#update-activity" class="topiclink">can be updated</a>. At the same time, outdated graphical elements will remain working in already created processes</span></li></ul>
|
||
<h2 class="p_Heading2"><a id="binding" class="hmanchor"></a><span class="f_Heading2">Map the activity and process contexts (bindings)</span></h2>
|
||
<p class="p_Normal">To perform a custom activity, bind its context with the context of the process in which it is applied. When the activity is configured in the module, on the <span style="font-weight: bold;">Context</span> tab, create input and output attributes. Then, bind these attributes with the variables of the process where you want to add the graphical element with the configured activity.</p>
|
||
<p class="p_Normal">First, create attributes in the context of the activity created in the module:</p>
|
||
<ol style="list-style-type:upper-roman">
|
||
<li value="1" class="p_Normal">Go to the module settings on the <span style="font-weight: bold;">Business Process Activities</span> tab and add a new activity or open the one created earlier by clicking its name</li><li value="2" class="p_Normal">In the activity settings on the <span style="font-weight: bold;">Context</span> tab, set input and output parameters:</li></ol>
|
||
<ul style="list-style-type:disc">
|
||
<li style="line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;"><span style="font-size: 13px; font-family: Inter; font-weight: bold; color: #394149;">Input parameters</span><span style="font-size: 13px; font-family: Inter; color: #394149;"> are the parameters that are filled in before the activity is executed. You can use them to pass the values of context variables of the process that contains the business process activity.</span></li><li style="line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;"><span style="font-size: 13px; font-family: Inter; font-weight: bold; color: #394149;">Output parameters</span><span style="font-size: 13px; font-family: Inter; color: #394149;"> are the parameters that are filled after the business process activity is completed. They are passed to the context of the process that contains the activity or directly to the fields of the app associated with this process.</span></li></ul>
|
||
<ol style="list-style-type:upper-roman" start="3">
|
||
<li value="3" class="p_Normal">Mark variables as input or output by checking the corresponding boxes.</li></ol>
|
||
<ol style="list-style-type:upper-roman" start="4">
|
||
<li value="4" class="p_Normal">Save the context and publish the activity.</li></ol>
|
||
<p class="p_Normal">After adding the activity to the business process diagram, you can map these variables to the process context. To do that:</p>
|
||
<ol style="list-style-type:upper-roman">
|
||
<li value="1" class="p_Normal">Double-click on the custom action or add a new one from the right panel.</li><li value="2" class="p_Normal">On the <span style="font-weight: bold;">General</span> tab, in the <span style="font-weight: bold;">Bind output attributes to</span> field, specify where to record the results of the module activity:</li></ol>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal">Context variables of the business process</li><li class="p_Normal">Fields of the app added to the business process context</li></ul>
|
||
<p class="p_Normal">Learn more about how to configure the graphical element in the business process designer in the <a href="module-action.html" class="topiclink">Business Process Activity</a> article.</p>
|
||
<ol style="list-style-type:upper-roman" start="3">
|
||
<li value="3" class="p_Normal">Click the <span style="font-weight: bold;">Inputs and Outputs</span> tab.</li><li value="4" class="p_Normal">A window with a mapping form will open. Select a process variable for each input and output attribute of the graphical element. Then the values from the activity created in the module will be passed to these variables. The input variables will include the data for executing the action configured in the graphical element, and the output variables will contain the result of this action. For mapping, variables should be of the <a href="360009707032.html" class="topiclink">same type</a>.</li><li value="5" class="p_Normal">Click <span style="font-weight: bold;">Save</span> to finish binding.</li></ol>
|
||
<h3 class="p_Heading3"><a id="custom-form" class="hmanchor"></a><span class="f_Heading3">Change the binding form</span></h3>
|
||
<p class="p_Normal">You can create your own binding form. To do this, click the <span style="font-weight: bold;">Create</span> <span style="font-weight: bold;">form</span> button on the <span style="font-weight: bold;">Context</span> tab of the <a href="script-activity.html" class="topiclink">script</a>, <a href="call-process-activity.html" class="topiclink">call process</a>, or <a href="delegated-activities.html" class="topiclink">delegated activity</a>. Important: Once the customized binding form is created, you cannot go back to the standard form. You will see a warning and you can either continue or cancel the change of the standard form.</p>
|
||
<p class="p_Comment"><img alt="bp_activities_02" width="397" height="180" style="margin:0;width:397px;height:180px;border:none" src="bp_activities_02.png"/></p>
|
||
<p class="p_Normal">Click <span style="font-weight: bold;">OK</span> to go to the <a href="interface_designer.html" class="topiclink">interface designer</a> to create the form.</p>
|
||
<p class="p_Normal">When the form is created, the <span style="font-weight: bold;">Activity Settings</span> tab will appear in the business process designer instead of the <span style="font-weight: bold;">Inputs and Outputs</span> tab. This will display the form you have configured.</p>
|
||
<h3 class="p_Heading3"><a id="arbitrary-type" class="hmanchor"></a><span class="f_Heading3">Creating input and output variables using a script</span></h3>
|
||
<p class="p_Normal">Input and output variables of a custom activity can be created on the mapping form using a script. </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;"><span style="font-size: 15px; font-family: Calibri,Vectora,'Droid Sans','Open Sans',Frutiger,sans-serif;">Creating variables using a script is only possible for custom activities of the <a href="script-activity.html" class="topiclink">Script</a> type .</span></p>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">конец внимание</span></p>
|
||
<p class="p_Normal">To create variables using a script:</p>
|
||
<ol style="list-style-type:upper-roman">
|
||
<li value="1" class="p_Normal">On the <span style="font-weight: bold;">Business process activities</span> tab of the custom module, create a <span style="font-weight: bold;">Script</span> type activity or select an activity you added earlier. </li><li value="2" class="p_Normal">Create a custom binding form for the activity as described <a href="activities-features.html#custom-form" class="topiclink">above</a> and open it.</li><li value="3" class="p_Normal">On the <span style="font-weight: bold;">Template</span> tab, drag the <span style="font-weight: bold;">Dynamic binding</span> widget from the right-side panel to the canvas.</li><li value="4" class="p_Normal">On the <span style="font-weight: bold;">Context</span> tab of the form, create a variable selecting <a href="360009707032.html#arbitrary-type" class="topiclink">Arbitrary type</a> as the type. It will store input and output variables.</li><li value="5" class="p_Normal">Save and publish the form.</li><li value="6" class="p_Normal">To make a context variable available in a script, close the form and open it again by clicking <span style="font-weight: bold;">Edit form</span> on the <span style="font-weight: bold;">Context</span> tab of the activity's settings.</li><li value="7" class="p_Normal">Open the <span style="font-weight: bold;">Dynamic binding</span> widget’s settings. On the <span style="font-weight: bold;">Main</span> tab, in the <span style="font-weight: bold;">Dynamic fields</span> setting, select the variable created in step <span style="font-weight: bold;">4</span>. Save the widget settings.</li></ol>
|
||
<p style="line-height: 1.28; margin: 0 0 11px 0;"><img alt="bp_activities_03" width="995" height="318" style="margin:0;width:995px;height:318px;border:none" src="bp_activities_03.png"/></p>
|
||
<ol style="list-style-type:upper-roman" start="8">
|
||
<li value="8" style="line-height: 1.28; margin-top: 0; margin-right: 0; margin-bottom: 11px;"><span style="font-family: 'Times New Roman',Times,Georgia,serif;">On the Scripts tab of the form, write a script that will create input and output variables and save them in the previously created </span><span style="font-family: 'Times New Roman',Times,Georgia,serif; font-weight: bold;">Arbitrary type</span><span style="font-family: 'Times New Roman',Times,Georgia,serif;"> variable:</span></li></ol>
|
||
<p class="p_CodeExample" style="white-space: normal; page-break-inside: avoid;"><span class="f_CodeExample">async </span><span class="f_CodeExample" style="font-weight: bold;">function</span><span class="f_CodeExample"> FillOut(): Promise<</span><span class="f_CodeExample" style="font-weight: bold;">void</span><span class="f_CodeExample">> {</span><br />
|
||
<span class="f_CodeExample"> ViewContext.data.bindings = </span><br />
|
||
<span class="f_CodeExample"> {</span><br />
|
||
<span class="f_CodeExample"> 'field1': {name: 'Field 1', type: DynamicFieldType.String, input: </span><span class="f_CodeExample" style="font-weight: bold;">true</span><span class="f_CodeExample">,},</span><br />
|
||
<span class="f_CodeExample"> 'field2': {name: 'Field 2', type: DynamicFieldType.String, output: </span><span class="f_CodeExample" style="font-weight: bold;">true</span><span class="f_CodeExample">,},</span><br />
|
||
<span class="f_CodeExample"> 'field3': {name: 'Field 3', type: DynamicFieldType.File, input: </span><span class="f_CodeExample" style="font-weight: bold;">true</span><span class="f_CodeExample">, output: </span><span class="f_CodeExample" style="font-weight: bold;">true</span><span class="f_CodeExample">,},</span><br />
|
||
<span class="f_CodeExample"> }</span><br />
|
||
<span class="f_CodeExample">}</span></p>
|
||
<ol style="list-style-type:upper-roman" start="9">
|
||
<li value="9" class="p_Normal">Set up the script start parameters. A script can be started using a control on a form, for example, a button, or upon a specific event. </li><li value="10" class="p_Normal">Save and publish the binding form.</li><li value="11" class="p_Normal">As soon as you define a variable for dynamic binding, you can access it on the <span style="font-weight: bold;">Scripts</span> tab in the business process activity. For example, you can assign a value to it: </li></ol>
|
||
<p class="p_CodeExample" style="white-space: normal; page-break-inside: avoid;"><span class="f_CodeExample">async </span><span class="f_CodeExample" style="font-weight: bold;">function</span><span class="f_CodeExample"> action(): Promise {</span><br />
|
||
<span class="f_CodeExample"> Context.data['bindings.field2'] = `Variable value`;</span><br />
|
||
<span class="f_CodeExample">}</span></p>
|
||
<p class="p_Normal">When you open the activity settings in the business process designer and go to the Activity Settings tab, dynamic fields with input and output parameters will be created automatically. Alternatively, you can run a script to generate them. Read more about it in <a href="https://tssdk.brix365.com/en/index.html" target="_blank" class="weblink">BRIX TS SDK</a>.</p>
|
||
<p class="p_Normal"><img alt="bp_activities_04" width="959" height="482" style="margin:0;width:959px;height:482px;border:none" src="bp_activities_04.png"/></p>
|
||
<h2 class="p_Heading2"><a id="call-vs-start-process" class="hmanchor"></a><span class="f_Heading2">Call process vs Start process</span></h2>
|
||
<p style="line-height: 1.20; margin: 7px 0 16px 0;"><span style="font-size: 13px; font-family: Inter; color: #394149;">The</span><span style="font-size: 13px; font-family: Inter; font-weight: bold; color: #394149;"> Call process</span><span style="font-size: 13px; font-family: Inter; color: #394149;"> activity type and the standard</span><span style="font-size: 13px; font-family: Inter; font-weight: bold; color: #394149;"> Start Process</span><span style="font-size: 13px; font-family: Inter; color: #394149;"> activity are similar, but there is a number of differences between them. They are shown in the table below.</span></p>
|
||
<div 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; border-collapse:collapse;">
|
||
<tr>
|
||
<td style="vertical-align:top; width:201px; background-color:#FFFFFF; padding:1px; border:solid thin #000000;"><p style="line-height: 1.20;"><span style="font-size: 13px; color: #000000;"> </span></p>
|
||
</td>
|
||
<td style="vertical-align:top; width:235px; background-color:#FFFFFF; padding:1px; border:solid thin #000000;"><p style="line-height: 1.20; margin: 0 1px 0 0;"><span style="font-family: Inter; font-weight: bold;">Call process</span></p>
|
||
<p style="line-height: 1.20; margin: 7px 0 7px 0;"><span style="font-family: Inter;">custom activity</span></p>
|
||
</td>
|
||
<td style="vertical-align:top; width:200px; background-color:#FFFFFF; padding:1px; border:solid thin #000000;"><p style="line-height: 1.20; margin: 7px 0 7px 0;"><span style="font-family: Inter; font-weight: bold;">Start Process</span></p>
|
||
<p style="line-height: 1.20; margin: 7px 0 7px 0;"><span style="font-family: Inter;">system activity</span></p>
|
||
</td>
|
||
</tr>
|
||
<tr>
|
||
<td style="vertical-align:top; width:201px; background-color:#FFFFFF; padding:1px; border:solid thin #000000;"><p style="line-height: 1.20; margin: 7px 0 7px 0;"><span style="font-family: Inter;">Tracked in the Process Monitor</span></p>
|
||
</td>
|
||
<td style="vertical-align:top; width:235px; background-color:#FFFFFF; padding:1px; border:solid thin #000000;"><p style="line-height: 1.20; margin: 7px 0 7px 0;"><span style="font-family: Inter;">No</span></p>
|
||
</td>
|
||
<td style="vertical-align:top; width:200px; background-color:#FFFFFF; padding:1px; border:solid thin #000000;"><p style="line-height: 1.20; margin: 7px 0 7px 0;"><span style="font-family: Inter;">Yes</span></p>
|
||
</td>
|
||
</tr>
|
||
<tr>
|
||
<td style="vertical-align:top; width:201px; background-color:#FFFFFF; padding:1px; border:solid thin #000000;"><p style="line-height: 1.20; margin: 7px 0 7px 0;"><span style="font-family: Inter;">The history of each step is available to users</span></p>
|
||
</td>
|
||
<td style="vertical-align:top; width:235px; background-color:#FFFFFF; padding:1px; border:solid thin #000000;"><p style="line-height: 1.20; margin: 7px 0 7px 0;"><span style="font-family: Inter;">No</span></p>
|
||
</td>
|
||
<td style="vertical-align:top; width:200px; background-color:#FFFFFF; padding:1px; border:solid thin #000000;"><p style="line-height: 1.20; margin: 7px 0 7px 0;"><span style="font-family: Inter;">Yes</span></p>
|
||
</td>
|
||
</tr>
|
||
<tr>
|
||
<td style="vertical-align:top; width:201px; background-color:#FFFFFF; padding:1px; border:solid thin #000000;"><p style="line-height: 1.20; margin: 7px 0 7px 0;"><span style="font-family: Inter;">Asynchronous start</span></p>
|
||
</td>
|
||
<td style="vertical-align:top; width:235px; background-color:#FFFFFF; padding:1px; border:solid thin #000000;"><p style="line-height: 1.20; margin: 7px 0 7px 0;"><span style="font-family: Inter;">No</span></p>
|
||
<p style="line-height: 1.20; margin: 7px 0 7px 0;"><span style="font-family: Inter;">The transition to the next step of the business process is possible only after the business process activity of the </span><span style="font-family: Inter; font-weight: bold;">Call process</span><span style="font-family: Inter;"> type is completed.</span></p>
|
||
</td>
|
||
<td style="vertical-align:top; width:200px; background-color:#FFFFFF; padding:1px; border:solid thin #000000;"><p style="line-height: 1.20; margin: 7px 0 7px 0;"><span style="font-family: Inter;">Yes</span></p>
|
||
<p style="line-height: 1.20; margin: 7px 0 7px 0;"><span style="font-family: Inter;">You can continue running the main process without waiting for the subprocess to finish.</span></p>
|
||
</td>
|
||
</tr>
|
||
<tr>
|
||
<td style="vertical-align:top; width:201px; background-color:#FFFFFF; padding:1px; border:solid thin #000000;"><p style="line-height: 1.20; margin: 7px 0 7px 0;"><span style="font-family: Inter;">Display</span></p>
|
||
</td>
|
||
<td style="vertical-align:top; width:235px; background-color:#FFFFFF; padding:1px; border:solid thin #000000;"><p style="line-height: 1.20; margin: 7px 0 7px 0;"><span style="font-family: Inter;">Activity does not appear in the list of processes in the </span><span style="font-family: Inter; font-weight: bold;">Administration</span><span style="font-family: Inter;"> workspace. You cannot start it directly in the BRIX interface by clicking the </span><span style="font-family: Inter; font-weight: bold;">Start Process</span><span style="font-family: Inter;"> button. It can be executed only by an activity of the </span><span style="font-family: Inter; font-weight: bold;">Call process</span><span style="font-family: Inter;"> type</span></p>
|
||
</td>
|
||
<td style="vertical-align:top; width:200px; background-color:#FFFFFF; padding:1px; border:solid thin #000000;"><p style="line-height: 1.20; margin: 7px 0 7px 0;"><span style="font-family: Inter;">Independent business process. Displayed in</span><span style="font-family: Inter; font-weight: bold;"> Administration > Business Processes</span><span style="font-family: Inter;">.</span></p>
|
||
</td>
|
||
</tr>
|
||
</table>
|
||
</div>
|
||
<h2 class="p_Heading2"><a id="update-activity" class="hmanchor"></a><span class="f_Heading2">Update a business process activity</span></h2>
|
||
<p style="line-height: 1.20; margin: 7px 0 16px 0;"><span style="font-size: 13px; font-family: Inter; color: #394149;">When a module is updated, business process activities may also be updated. Outdated activities cannot be used on new process diagrams. They will no longer be available on the right-side panel of the business process designer. However, outdated activities will continue to work as usual in previously created processes. When you modify the logic of a process with an outdated activity, for instance, change its participants, you will see a warning that the process contains outdated activities when you publish the process.</span></p>
|
||
|
||
<div class="bottom-nav">
|
||
|
||
<a id="prev-link" class="topic__navi_prev" href="delegated-activities.html">
|
||
<span class="bottom-nav__arrow bottom-nav__arrow--prev"></span> <span
|
||
class="bottom-nav__link">delegated-activities.html</span>
|
||
</a>
|
||
|
||
|
||
<a id="next-link" class="topic__navi_next" href="extention-processes.html">
|
||
<span class="bottom-nav__link">extention-processes.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>
|