270 lines
32 KiB
HTML
270 lines
32 KiB
HTML
<!DOCTYPE html>
|
||
<html lang="en">
|
||
|
||
<head>
|
||
<title>Update a solution</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 feature is used to import changes to an already installed solution. If you have edited components of the solution, you can update it in two ways:" />
|
||
<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>Low-code designer > <a href="solution.html">Solution</a> / Update a solution</p>
|
||
</div>
|
||
|
||
</div>
|
||
<div class="topic__title"><h1 class="p_Heading1"><span class="f_Heading1">Update a solution</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.38;">The feature is used to import changes to an already installed solution. If you have edited components of the solution, you can update it in two ways:</p>
|
||
<ul style="list-style-type:disc">
|
||
<li style="line-height: 1.38;">Install the fully updated version without saving your customizations.</li><li style="line-height: 1.38;">Select the <a href="update_solution.html#soft_update" class="topiclink">soft update</a> option. Then the components that have been changed will not be updated. Components whose settings you did not change will be updated.</li></ul>
|
||
<p style="line-height: 1.38;"><span style="font-size: 13px; color: #000000;"> </span></p>
|
||
<p style="line-height: 1.20; margin: 7px 0 16px 0;">The original or updated version of a solution may include new components such as additional workspaces, apps, or modules. </p>
|
||
<p style="line-height: 1.20; margin: 7px 0 16px 0;">To ensure the integrity of the solution, we do not recommend removing components from it. This can lead to inconsistency of workspaces, optional dependencies, and links in structures within the solution. For example, workspace duplication may occur after an update. Because of integrity issues, errors may occur during its further export, import, and update processes.</p>
|
||
<p style="line-height: 1.20; margin: 7px 0 16px 0;">If you need to delete a workspace or a module from the solution, consider the following:</p>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="1" style="line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 16px;">Before deleting, check if the solution has internal to the workspace or module to be deleted.</li><li value="2" style="line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 16px;">Consider the effect of the deletion on the created <a href="optional-dependencies.html" class="topiclink">optional dependencies</a> from other solutions.</li><li value="3" style="line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 16px;">If you need to re-add a workspace or module to the solution, we recommend that you do not delete these components and instead <a href="360007799052.html" class="topiclink">hide the workspace from the left menu</a> or <a href="connect-extention.html#disable" class="topiclink">disable the module</a>.</li></ol>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Update start</span></h2>
|
||
<p style="line-height: 1.38;">To perform an update:</p>
|
||
<ol style="list-style-type:upper-roman">
|
||
<li value="1" style="text-align: justify; line-height: 1.20; margin-top: 0; margin-right: 0; margin-bottom: 19px;">Proceed in one of the two ways:</li></ol>
|
||
<ul style="list-style-type:disc">
|
||
<li style="text-align: justify; line-height: 1.20; margin-top: 0; margin-right: 0; margin-bottom: 19px;">If the solution was imported from BRIX Store, you can update it by <a href="import_solution.html" class="topiclink">re-installing it from the catalog</a>. </li></ul>
|
||
<p style="text-align: justify; line-height: 1.20; margin: 0 0 19px 34px;">On the solutions<span style="color: #202122; background-color: #ffffff;">’</span>s page, on the <span style="font-weight: bold;">Versions</span> tab, you can find the list of updates and download the <span style="font-weight: bold;">.e365</span> file of the most recent version.</p>
|
||
<ul style="list-style-type:disc">
|
||
<li style="text-align: justify; line-height: 1.20; margin-top: 0; margin-right: 0; margin-bottom: 19px;"><a href="upload-solution-file.html" class="topiclink">Upload an .e365 file</a> from your PC or from the system files and click <span style="font-weight: bold;">Next</span>.</li></ul>
|
||
<p style="text-align: justify; line-height: 1.20; margin: 0 0 19px 34px;"><span style="font-weight: bold;">Important</span>: if you upload a solution that was created or modified in a newer version of the system (for example, 2024.4) than your current version (for example, 2024.1), a warning notification appears. The update may fail or the solution may not work properly because the newer version may have changes that are incompatible with yours. Select whether to cancel or continue the update process.</p>
|
||
<ol style="list-style-type:upper-roman" start="2">
|
||
<li value="2" style="text-align: justify; line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;">This will start the checking process for the components of the solution version from the uploaded file. If errors are found, for example, identical pages are found or <a href="export-solution-file.html#add-dependencies" class="topiclink">dependencies from another solution are added</a> to the version, you will not be able to complete the update.</li></ol>
|
||
<p style="text-align: justify; line-height: 1.20; margin: 7px 0 7px 34px;">If the new solution version has apps, widgets, or business processes whose fields reference apps from <a href="active_licences.html" class="topiclink">licensed system solutions</a>, you will see a notification about it. You can complete the solution update, but you will need to activate the license of the system solution you are using for it to work correctly.</p>
|
||
<p style="text-align: justify; line-height: 1.20; margin: 7px 0 7px 34px;">If the solution is successfully checked, click <span style="font-weight: bold;">Next</span>.</p>
|
||
<p style="line-height: 1.20; margin: 0 0 0 36px;"><img alt="update_solution02" width="594" height="311" style="margin:0;width:594px;height:311px;border:none" src="update_solution02.png"/></p>
|
||
<ol style="list-style-type:upper-roman" start="3">
|
||
<li value="3" class="p_Normal" style="line-height: 1.20;">The uploaded version is then compared to the existing solution in the system. If you have made changes to the solution components, for example, changing the app form or changing a business process, a list of conflicts is displayed. Select a further action:</li></ol>
|
||
<ul style="list-style-type:disc"><ul style="list-style-type:circle">
|
||
<li class="p_Normal">Confirm the solution update. Then the new version of the solution will completely replace the existing one. Your changes will not be saved.</li><li class="p_Normal">Perform a <a href="update_solution.html#soft_update" class="topiclink">soft update</a>.</li><li class="p_Normal"><a id="conflicts" class="hmanchor"></a>Cancel the update.</li></ul></li></ul>
|
||
<p style="line-height: 1.20; margin: 7px 0 7px 0;"><img alt="update_solution03" width="987" height="344" style="margin:0;width:987px;height:344px;border:none" src="update_solution03.png"/></p>
|
||
<ol style="list-style-type:upper-roman" start="4">
|
||
<li value="4" style="line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;">If the target site has edited permissions for a workspace, app, or page within the solution, you will see a list of inconsistencies with the permissions configured in the uploaded version of the solution. </li></ol>
|
||
<p style="line-height: 1.20; margin: 7px 0 7px 34px;">Select which permission settings you want to update, that is, apply the permissions configured in the uploaded version of the solution. You can leave all permissions as they are set in the existing version.</p>
|
||
<p style="line-height: 1.20; margin: 7px 0 7px 0;"><img alt="update_solution04" width="601" height="385" style="margin:0;width:601px;height:385px;border:none" src="update_solution04.png"/></p>
|
||
<p style="line-height: 1.20;"><span style="font-weight: bold;"><a class="dropdown-toggle" style="font-style: normal; font-weight: bold; color: #000000; background-color: transparent; text-decoration: none;" href="javascript:HMToggle('toggle','TOGGLE0186A1')">“False” access setting conflicts may occur during update</a></span></p>
|
||
<div id="TOGGLE0186A1" class="dropdown-toggle-body" style="text-align: left; text-indent: 0; line-height: 1.0; page-break-inside: avoid; padding: 0 0 0 0; margin: 0 0 0 0;"><table style="border:none; border-spacing:0;">
|
||
<tr>
|
||
<td style="vertical-align:top; padding:0; border:none"><p class="p_Normal"> <br />
|
||
The change history of access rights is saved starting with system version 2024.1 and may not be present in existing solutions. In this case, the conflict line will display the value <span style="font-weight: bold;"><Unknown></span>, i.e. there is no change history for the current rights records. In such a line you can either update or not update the rights settings, i.e. ignore them. To prevent the “false” conflict from occurring again, export the solution in system version 2024.1 or higher. During the export process, the change history will be recorded to the access rights structure of the existing solution in the system.</p>
|
||
</td>
|
||
</tr>
|
||
</table>
|
||
</div>
|
||
<h2 class="p_Heading2"><a id="soft_update" class="hmanchor"></a><span class="f_Heading2">Soft update of the solution</span></h2>
|
||
<p style="text-align: justify; line-height: 1.20; margin: 7px 0 16px 0;">You can use this update option if there are conflicts between the installed and the new version of the solution. The option allows you to save the changes you have made to components such as business processes, apps, forms, pages, and widgets. During the soft update process:</p>
|
||
<ol style="list-style-type:upper-roman" start="5"><ul style="list-style-type:disc">
|
||
<li style="text-align: justify; line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 16px;">Components with conflicts will not be updated, your changes will be saved.</li><li style="text-align: justify; line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 16px;">Other solution components will be updated if they are not in the conflict list and they don’t contain links to components with conflicts.</li><li style="text-align: justify; line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 16px;">New solution components will be added if they do not contain links to components with conflicts.</li></ul></li></ol>
|
||
<p style="text-align: justify; line-height: 1.20; margin: 7px 0 16px 0;">Let’s look at some examples.</p>
|
||
<h3 class="p_Heading3"><span class="f_Heading3">Case 1. Conflict in the solution component</span></h3>
|
||
<p style="line-height: 1.20; margin: 7px 0 16px 0;">You have added property <span style="font-weight: bold;">A</span> to the context of an app that is part of a solution. In the new version of the solution:</p>
|
||
<ul style="list-style-type:disc">
|
||
<li style="line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;">Property <span style="font-weight: bold;">B</span> is added to the context of this app.</li><li style="line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;">Widget <span style="font-weight: bold;">C</span> is placed on the app creation form.</li></ul>
|
||
<p style="line-height: 1.20; margin: 7px 0 16px 0;">The result of the soft update:</p>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="1" style="text-align: justify; line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;">There will be a conflict in the app, it will not be updated. Property <span style="font-weight: bold;">B</span> will not be added to its context, property <span style="font-weight: bold;">A</span> will remain.</li><li value="2" style="text-align: justify; line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;">The app creation form will be updated, it will not have a conflict. Widget <span style="font-weight: bold;">C</span> will be added.</li></ol>
|
||
<p style="text-align: justify; line-height: 1.20; margin: 7px 0 7px 0;"><img alt="Рисунок 1" width="998" height="246" style="margin:0;width:998px;height:246px;border:none" src="hmfile_hash_dec987e0.png"/></p>
|
||
<h3 class="p_Heading3"><span class="f_Heading3">Case 2: Reference to a component with a conflict</span></h3>
|
||
<p style="text-align: justify; line-height: 1.20; margin: 7px 0 16px 0;">The initial solution contains:</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;">The app in the context of which you have added property <span style="font-weight: bold;">A</span>.</li><li style="text-align: justify; line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;">A business process that has a variable that refers to this app.</li></ul>
|
||
<p style="text-align: justify; line-height: 1.20; margin: 7px 0 16px 0;">In the new version of the solution, property <span style="font-weight: bold;">B</span> is added to the app context, and a task is added to the process diagram.</p>
|
||
<p style="text-align: justify; line-height: 1.20; margin: 7px 0 16px 0;">The result of the soft update:</p>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="1" style="text-align: justify; line-height: 1.28; margin-top: 0; margin-right: 0; margin-bottom: 11px;">There will be a conflict in the app, it will not be updated. Property <span style="font-weight: bold;">B</span> will not be added to its context, property <span style="font-weight: bold;">A</span> will remain.</li><li value="2" style="text-align: justify; line-height: 1.28; margin-top: 0; margin-right: 0; margin-bottom: 11px;">The business process will not be updated because it refers to the app in which the conflict occurred.</li></ol>
|
||
<p style="text-align: justify; line-height: 1.28; margin: 0 0 11px 0;"><img alt="Рисунок 2" width="998" height="361" style="margin:0;width:998px;height:361px;border:none" src="hmfile_hash_931540fd.png"/></p>
|
||
<h3 class="p_Heading3"><span class="f_Heading3">Case 3. A new solution component contains a reference to a component with a conflict</span></h3>
|
||
<p style="text-align: justify; line-height: 1.20; margin: 7px 0 16px 0;">You have added property <span style="font-weight: bold;">A</span> to the context of an app that is part of a solution.</p>
|
||
<p style="text-align: justify; line-height: 1.20; margin: 7px 0 16px 0;">In the new version of the solution:</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;">Property <span style="font-weight: bold;">B</span> is added to the app context.</li><li style="text-align: justify; line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;">A new process is added that refers to this app.</li></ul>
|
||
<p style="text-align: justify; line-height: 1.20; margin: 7px 0 16px 0;">The result of the soft update:</p>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="1" style="text-align: justify; line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;">There will be a conflict in the app, it will not be updated. Property <span style="font-weight: bold;">B</span> will not be added to its context, property <span style="font-weight: bold;">A</span> will remain.</li><li value="2" style="text-align: justify; line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;">A new business process will not be added because it refers to the app with the conflict.</li></ol>
|
||
<p style="text-align: justify; line-height: 1.20; margin: 7px 0 7px 0;"><img alt="Рисунок 3" width="998" height="362" style="margin:0;width:998px;height:362px;border:none" src="hmfile_hash_847fac5b.png"/></p>
|
||
<h3 class="p_Heading3"><span class="f_Heading3">Soft update of a locked workspace</span></h3>
|
||
<p style="text-align: justify; line-height: 1.20; margin: 7px 0 16px 0;">If the solution contains a locked workspace, the soft update ignores dependencies between this workspace and the unlocked workspace where conflicts are found. In this case, the components of the locked workspace (apps, processes, widgets) will be updated.</p>
|
||
<p style="text-align: justify; line-height: 1.20; margin: 7px 0 16px 0;">Let’s consider the specifics of such an update. Components of a locked workspace:</p>
|
||
<ol style="list-style-type:upper-roman" start="5"><ul style="list-style-type:disc">
|
||
<li style="text-align: justify; line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 16px;">Will be updated if they refer to components of an unlocked workspace in which conflicts are found.</li><li style="text-align: justify; line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 16px;">Will be updated if they are referred by components of an unlocked workspace in which conflicts are found.</li><li style="text-align: justify; line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 16px;">Will NOT be updated if they contain conflicts.</li><li style="text-align: justify; line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 16px;">Will NOT be updated if there are dependencies between them and components of another locked workspace where conflicts are found.</li></ul></li></ol>
|
||
<p style="text-align: justify; line-height: 1.20; margin: 7px 0 16px 0;">Let’s analyze the case on the example of the HR solution that contains a locked <span style="font-weight: bold;">HR</span> workspace and an <span style="font-weight: bold;">HR Settings</span> workspace available for changes:</p>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="1" style="text-align: justify; line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;">In the installed version of the solution, within the <span style="font-weight: bold;">HR Settings</span> workspace, add a task to the process that references the locked <span style="font-weight: bold;">HR</span> workspace app.</li><li value="2" style="text-align: justify; line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;">Let’s assume that in the new version of the solution:</li></ol>
|
||
<ul style="list-style-type:disc">
|
||
<li style="text-align: justify; line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;">Within the <span style="font-weight: bold;">HR</span> workspace, property <span style="font-weight: bold;">A</span> is added to the context of the app that is associated with the changed process.</li><li style="text-align: justify; line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;">Within the <span style="font-weight: bold;">HR</span> <span style="font-weight: bold;">Settings</span> workspace, property <span style="font-weight: bold;">B</span> is added to the context of the process we have changed.</li></ul>
|
||
<ol style="list-style-type:decimal" start="3">
|
||
<li value="3" style="text-align: justify; line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;">Let’s run the solution update.</li><li value="4" style="text-align: justify; line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;">During its checking phase, it will <span style="color: #0000ff;"><a href="update_solution.html#conflicts" class="topiclink">show conflicts</a></span> in the process that is changed within the <span style="font-weight: bold;">HR Settings</span> workspace. In this conflict, we will see dependencies with the app in the locked <span style="font-weight: bold;">HR</span> workspace.</li><li value="5" style="text-align: justify; line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;">Let’s apply a soft update to the solution and get the following result:</li></ol>
|
||
<ul style="list-style-type:disc">
|
||
<li style="text-align: justify; line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;">The app within the locked <span style="font-weight: bold;">HR</span> workspace will be updated, and property <span style="font-weight: bold;">A</span> will be added to the app context. Dependencies found in the conflict will be ignored.</li><li style="text-align: justify; line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;">The process within the unlocked <span style="font-weight: bold;">HR Settings</span> workspace will not be updated. The task in it will be saved, property <span style="font-weight: bold;">B</span> will not be added to the process context.</li></ul>
|
||
<p style="text-align: justify; line-height: 1.20; margin: 7px 0 7px 0;"><img alt="Рисунок 4" width="998" height="461" style="margin:0;width:998px;height:461px;border:none" src="hmfile_hash_586bda3d.png"/></p>
|
||
|
||
<div class="bottom-nav">
|
||
|
||
<a id="prev-link" class="topic__navi_prev" href="block_solution.html">
|
||
<span class="bottom-nav__arrow bottom-nav__arrow--prev"></span> <span
|
||
class="bottom-nav__link">block_solution.html</span>
|
||
</a>
|
||
|
||
|
||
<a id="next-link" class="topic__navi_next" href="solution_password.html">
|
||
<span class="bottom-nav__link">solution_password.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>
|