All checks were successful
Deploy Static Site / deploy (push) Successful in 6m6s
220 lines
24 KiB
HTML
220 lines
24 KiB
HTML
<!DOCTYPE html>
|
||
<html lang="en">
|
||
|
||
<head>
|
||
<title>Edit App Item</title>
|
||
<meta name="generator" content="Help+Manual" />
|
||
<meta name="keywords" content="" />
|
||
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
|
||
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
|
||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||
<meta name="description" content="The Edit App Item activity is used to edit fields on the app item page during the execution of a business process. With this activity, you can add a file to a contract page,..." />
|
||
<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 / Edit App Item</p>
|
||
</div>
|
||
|
||
</div>
|
||
<div class="topic__title"><h1 class="p_Heading1" style="text-align: center; line-height: 1.20; margin: 19px 0 19px 0;"><span class="f_Heading1" style="font-size: 32px;">Edit App Item</span></h1>
|
||
</div>
|
||
|
||
</header>
|
||
<section class="article__content">
|
||
<div class="scroll-top-inner">
|
||
<a href="#h1-article" class="scroll-top"></a>
|
||
</div>
|
||
<!-- Placeholder for topic body. -->
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;"><img alt="edit-app-item-1" width="99" height="80" style="margin:0;width:99px;height:80px;border:none" src="edit-app-item-1.png"/>The <span style="font-weight: bold;">Edit App Item</span> activity is used to edit fields on the app item page during the execution of a business process. With this activity, you can add a file to a contract page, change the amount in an order, edit the dates of bills and additional agreements, and so on. You can change the item data manually or automatically.</p>
|
||
<h2 class="p_Heading2" style="line-height: 1.20; margin: 19px 0 0 0;"><span class="f_Heading2" style="font-size: 24px;">How to use the Edit App Item activity</span></h2>
|
||
<p style="line-height: 1.20; margin: 19px 0 0 0;">As an example, let’s take a look at the <span style="font-weight: bold;">Contracts</span> app. An employee creates an app item and enters all the related information, such as the total amount, payment dates, discount percentage, and so on. However, the <span style="font-weight: bold;">Contract file</span> field remains empty because the file will be created later on in the course of the process.</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;"><img alt="edit-app-item-2" width="642" height="390" style="margin:0;width:642px;height:390px;border:none" src="edit-app-item-2.png"/></p>
|
||
<p style="line-height: 1.20; margin: 14px 0 0 0;">As soon as the employee saves the app item, a business process is launched. In the course of this process, the finance specialist approves the data entered into the app page. Next, according to this data, a contract file needs to be created. This can be done automatically with the help of the <a href="360026720792.html" class="topiclink">Generate from template</a> activity, or the employee could do it manually within the assigned task. The generated document must be added to the app item page in the <span style="font-weight: bold;">Contract file</span> field. To do this, the <span style="font-weight: bold;">Edit App Item</span> activity is used in the business process. </p>
|
||
<h2 class="p_Heading2" style="line-height: 1.20; margin: 19px 0 0 0;"><span class="f_Heading2" style="font-size: 24px;">Set up the Edit App Item activity</span></h2>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 19px 0 0 0;">Go to the <a href="360012265552.html#create_process" class="topiclink">process page</a> and click the gear icon on the right panel to open the <span style="font-weight: bold;">System elements</span> tab. Drag the <span style="font-weight: bold;">Edit App Item</span> activity to the process diagram and place it where editing an <a href="360016427291.html" class="topiclink">app item</a> will be necessary.</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;"><img alt="edit-app-item-4" width="712" height="301" style="margin:0;width:712px;height:301px;border:none" src="edit-app-item-4.png"/></p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">Double-click on the activity to open the settings. </p>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">General tab</span></h2>
|
||
<p class="p_Normal">Fill in the fields in the opened window:</p>
|
||
<p class="p_Normal"><img alt="edit-app-item-5" width="668" height="427" style="margin:0;width:668px;height:427px;border:none" src="edit-app-item-5.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-weight: bold;">Name</span><span style="font-weight: bold; color: #ff0000;">*</span>. Enter the name of the activity as it will be shown on<span style="font-size: 15px;"> </span>the process diagram<span style="font-size: 15px;">. </span></li><li style="line-height: 1.28; margin-top: 0; margin-right: 0; margin-bottom: 11px;"><span style="font-weight: bold;">Task name</span>. Enable the <span style="font-weight: bold;">Generate name from template</span> option to add <a href="process_context.html" class="topiclink">context variables</a> to the name that the executor will see in the task list and on the task page.<ul style="list-style-type:circle">
|
||
<li style="line-height: 1.28; margin-top: 0; margin-right: 0; margin-bottom: 0;"><span style="font-weight: bold;">Template</span><span style="font-weight: bold; color: #ff0000;">*</span>. Click the<span style="font-weight: bold;"> {+} </span>icon in the right corner of the field and select a variable. You can also <a href="360007679591.html#conditions-and-functions" class="topiclink">add conditions and functions</a> as you would for an item name template. This will help generate a more informative name.</li></ul></li></ul>
|
||
<p style="text-indent: -1px; line-height: 1.28; margin: 6px 0 11px 60px;">If this option is not used, the text specified in the <span style="font-weight: bold;">Name</span><span style="color: #ff0000;">*</span> field will be displayed in the task list and on the form.</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-weight: bold;">Variable</span><span style="font-weight: bold; color: #ff0000;">*</span>. Specify the <a href="360009707032.html#app" class="topiclink">App</a> type variable from the business process context that refers to the app item you wish to edit. If the variable does not yet exist in the process context, click the <span style="font-weight: bold;">Create a new variable</span> button.<br />
|
||
<br />
|
||
When you specify the context variable, you can rename it or add a description. To do this, click the <span style="font-weight: bold;">Change variable settings</span> button. The changes made will be displayed in the context of the process.</li><li style="line-height: 1.28; margin-top: 0; margin-right: 0; margin-bottom: 11px;"><span style="font-weight: bold;">Update type</span>. Specify the way to change the item:<ul style="list-style-type:circle">
|
||
<li style="line-height: 1.28; margin-top: 0; margin-right: 0; margin-bottom: 11px;"><span style="font-weight: bold;">Manually</span>. The user or a <a href="360007146071.html" class="topiclink">group</a> of users specified in the <a href="360012263032.html" class="topiclink">swimlane</a> will be given a task with the form of editing an item. The fields on the page will be filled with the previously specified data, which can be edited. The user can also cancel the editing of an item if a corresponding <a href="360012454020.html#connectors-tab" class="topiclink">connector is configured for the activity</a>.</li></ul></li></ul>
|
||
<p style="line-height: 1.28; margin: 0 0 11px 60px;">If the swimlane with the activity includes a group of users, the task of changing the item will be assigned to all the employees in this group. As soon as someone starts working on the task, it will disappear from the task list of other employees.</p>
|
||
<ul style="list-style-type:disc"><ul style="list-style-type:circle">
|
||
<li style="line-height: 1.28; margin-top: 0; margin-right: 0; margin-bottom: 11px;"><span style="font-weight: bold;">Automatically</span>. The item will be created automatically. Item fields will be filled according to the settings specified on the <span style="font-weight: bold;">Field Values</span> tab.</li></ul></li></ul>
|
||
<ul style="list-style-type:disc">
|
||
<li style="line-height: 1.20;"><span style="font-weight: bold;">Reassignment</span>. The option is displayed if the <span style="font-weight: bold;">Manually</span> update type is selected. Enable this option for the task executor to be able to reassign the task to another user.</li><li style="line-height: 1.20;"><span style="font-weight: bold;">Notification</span>. The option is displayed if the <span style="font-weight: bold;">Manually</span> update type is selected. Select it so that the task executor can receive the notification about its assignment to the <a href="360014162972.html" class="topiclink">#Activity stream</a>. To send an additional notification about the task to the executor’s email, they can enable the option to <a href="360016398552.html#task-alerts" class="topiclink">send notifications about new tasks to their email</a> in the profile settings.</li></ul>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Field Values tab</span></h2>
|
||
<p style="line-height: 1.20; margin: 6px 0 16px 0;">This tab appears after selecting a variable on the <span style="font-weight: bold;">General</span> tab.</p>
|
||
<p class="p_Normal"><img alt="edit-app-item-6" width="631" height="351" style="margin:0;width:631px;height:351px;border:none" src="edit-app-item-6.png"/></p>
|
||
<p style="line-height: 1.20; margin: 14px 0 0 0;">If you selected the <span style="font-weight: bold;">Automatically</span> method, specify the field to be changed in the <span style="font-weight: bold;">App field</span> column. In our case, it is <span style="font-weight: bold;">Contract file</span>. In the <span style="font-weight: bold;">Process variable</span> column, specify the corresponding process variable. We have specified the <span style="font-weight: bold;">File</span> variable because the contract <a href="360026720792.html" class="topiclink">created from a template</a> will be stored in it.</p>
|
||
<p style="line-height: 1.20; margin: 14px 0 0 0;">If you selected the<span style="font-weight: bold;"> Manually </span>method, you can also map fields to variables. For example, if the contract file is still generated from a template, the executor will receive a task of editing the item. The generated file will be stored in the app field you specified in the mapping settings. The employee will be able to check or replace it before saving the changes and closing the task.</p>
|
||
<p style="line-height: 1.20; margin: 14px 0 0 0;">Please note that only app fields and process context variables of the same <a href="360009707032.html" class="topiclink">type</a> can be mapped.</p>
|
||
<h2 class="p_Heading2"><a id="connectors-tab" class="hmanchor"></a><span class="f_Heading2">Connectors tab</span></h2>
|
||
<p class="p_Normal"><img alt="edit-app-item-7" width="654" height="356" style="margin:0;width:654px;height:356px;border:none" src="edit-app-item-7.png"/></p>
|
||
<p style="line-height: 1.20; margin: 14px 0 0 0;">This tab is available when you select the <a href="360019810892.html#360019810892" class="topiclink">Manually</a> item creation method.</p>
|
||
<p style="line-height: 1.20; margin: 14px 0 0 0;">Here you can configure the outgoing <a href="360015835331.html" class="topiclink">connectors</a> of the activity, which will be displayed to the user as buttons in the item editing task.</p>
|
||
<p style="line-height: 1.20; margin: 14px 0 0 0;">Please note that the <span style="font-weight: bold;">Edit App Item</span> can have only two outgoing connectors: to save the item and to cancel its creation. The connector to save the item should be marked as the default one.</p>
|
||
<p style="line-height: 1.20; margin: 14px 0 0 0;">Also, on this tab, you can change button names, add confirmation text, select colors, etc. To go to the settings, click on the connector name. Read more in the <a href="360015835331.html" class="topiclink">Connectors</a> article.</p>
|
||
<p style="line-height: 1.20; margin: 14px 0 0 0;">Once you have specified all the settings, click <span style="font-weight: bold;">Save</span>.</p>
|
||
<p style="line-height: 1.20; margin: 14px 0 0 0;">Now, in the course of the process, as soon as the contract is approved, the created file will be saved to a variable and then displayed in the field on the app item page.</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;"><img alt="eai6" width="669" height="465" style="margin:0;width:669px;height:465px;border:none" src="eai6.png"/></p>
|
||
|
||
<div class="bottom-nav">
|
||
|
||
<a id="prev-link" class="topic__navi_prev" href="360019810892.html">
|
||
<span class="bottom-nav__arrow bottom-nav__arrow--prev"></span> <span
|
||
class="bottom-nav__link">360019810892.html</span>
|
||
</a>
|
||
|
||
|
||
<a id="next-link" class="topic__navi_next" href="assign_permissions.html">
|
||
<span class="bottom-nav__link">assign_permissions.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>
|