koziavin
00717a92fb
All checks were successful
Deploy Static Site / deploy (push) Successful in 6m6s
338 lines
54 KiB
HTML
338 lines
54 KiB
HTML
<!DOCTYPE html>
|
||
<html lang="en">
|
||
|
||
<head>
|
||
<title>2024.11</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="Here is the list of changes that you can explore right now by activating the BRIX trial version." />
|
||
<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>New releases > BRIX SaaS / 2024.11</p>
|
||
</div>
|
||
|
||
</div>
|
||
<div class="topic__title"><h1 class="p_Heading1"><span class="f_Heading1">2024.11</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"><span style="background-color: #ffffff;">Here is the list of changes that you can explore right now by activating the BRIX trial version.</span></p>
|
||
<p class="p_Normal"><span style="background-color: #ffffff;">After December 16, 2024, all changes will become available to our clients in their active companies. Please note, the list may be expanded after the release.</span></p>
|
||
<p class="p_Normal">To enhance the update process and increase your awareness about significant changes, we are introducing the new <span style="font-weight: bold; color: #800000;">#BreakingChangeAlert</span> tag. This tag will be used to mark critical changes that could impact the operation of your system. Please pay special attention to any updates marked with this tag, as they may require additional actions on your part to adapt or adjust your current configuration.</p>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Processes</span></h2>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="1" class="p_Normal" style="line-height: 1.20;">TEAM-9565 Added search on the process and instance monitor page. You can now search by main and system fields, and use EQL queries.</li></ol>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 0 0 0 19px;">Added display settings for the process hierarchy.</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 0 0 0 19px;">In On-Premises, search is available after activating the <code><b>enableSearchInProcessMonitor</b></code> feature flag.</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 0 0 0 19px;"><span style="font-weight: bold; color: #800000;">#BreakingChangeAlert</span></p>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="2" class="p_Normal">TEAM-26859 The <span style="font-weight: bold;">Process Monitor</span> and <span style="font-weight: bold;">Business Processes</span> page now displays process instances for free locked modules.</li><li value="3" class="p_Normal">TEAM-31030 Shortened the time for publishing processes. The feature itself has not changed.</li><li value="4" class="p_Normal">TEAM-30454 Scripts are now executed on behalf of a user from the swimlane where the <span style="font-weight: bold;">Script</span> activity, script gateway, or business process action (script) is directly placed.</li></ol>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal">If there is no executor in the swimlane, the script is executed on behalf of the supervisor.</li><li class="p_Normal">For multiple swimlanes, the script is executed on behalf of one of the executors.</li></ul>
|
||
<p class="p_Normal"><span style="font-weight: bold; color: #800000;">#BreakingChangeAlert</span></p>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">CRM</span></h2>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="1" class="p_Normal">TEAM-26540 Added the <span style="font-weight: bold;">Engagement</span> gateway to the customer journey maps. It is placed after the <span style="font-weight: bold;">Email</span> activity and adds several branches to the map depending on user actions:</li></ol>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal">Email opened/unopened.</li><li style="line-height: 1.28; margin-top: 0; margin-right: 0; margin-bottom: 11px;">Link in the email clicked/not clicked.</li></ul>
|
||
<p class="p_Normal" style="margin: 0 0 0 19px;">You can add several gateways like this to a single map.</p>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="2" class="p_Normal">TEAM-31479 Updated the<span style="font-weight: bold;"> Linked Emails</span> widget. Now the data is displayed in a structured way:</li></ol>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal">From, To, Copy.</li><li class="p_Normal">Attached files.</li><li class="p_Normal">Partial content of the email.</li></ul>
|
||
<p style="line-height: 1.28; margin: 0 0 11px 0;">A transition to the email page for viewing full information was added.</p>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">API and TS SDK</span></h2>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="1" class="p_Normal">TEAM-27554 Added methods for working with file streams. It is now possible to create a <span style="font-weight: bold;">File</span> item from a stream:</li></ol>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">fileItem.createFromStream(readableStream);</span></p>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="2" class="p_Normal">TEAM-28479 <span style="background-color: #ffffff;">To public API of app metadata description, we added the return of category options</span>. Data example:</li></ol>
|
||
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">"data":</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">{</span><br />
|
||
<span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">"enumItems":</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">[</span><br />
|
||
<span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">{</span><br />
|
||
<span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">"code":</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">"a",</span><br />
|
||
<span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">"name":</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">"a",</span><br />
|
||
<span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">"default":</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample" style="font-weight: bold;">false</span><br />
|
||
<span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">},</span><br />
|
||
<span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">{</span><br />
|
||
<span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">"code":</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">"b",</span><br />
|
||
<span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">"name":</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">"b",</span><br />
|
||
<span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">"default":</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample" style="font-weight: bold;">true</span><br />
|
||
<span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">},</span><br />
|
||
<span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">{</span><br />
|
||
<span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">"code":</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">"c",</span><br />
|
||
<span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">"name":</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">"c",</span><br />
|
||
<span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">"default":</span><span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample" style="font-weight: bold;">false</span><br />
|
||
<span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">}</span><br />
|
||
<span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">]</span><br />
|
||
<span class="f_CodeExample" style="color: #ffffff;"> </span><span class="f_CodeExample">}</span></p>
|
||
<p class="p_Normal"> </p>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Calendars</span></h2>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="1" class="p_Normal">TEAM-28140 Implemented the new <span style="font-weight: bold;">Multiple business calendars</span> setting available with the <code><b>allowMultipleWorkCalendars</b></code> feature flag.</li></ol>
|
||
<p class="p_Normal" style="margin: 0 0 0 19px;">The flag will be enabled by default for the On-Premises edition immediately after the 2024.11 release, and for SaaS the functionality will become available a little later, but also as part of this release.</p>
|
||
<p class="p_Normal" style="margin: 0 0 0 48px;">1. It has become possible to separately customize working hours and breaks for each working day.</p>
|
||
<p class="p_Normal" style="margin: 0 0 0 48px;">2. The duration of a standard workday has been added to support existing business calendar bindings.</p>
|
||
<p class="p_Normal" style="margin: 0 0 0 48px;">3. Work calendar settings are now displayed on the business calendar item.</p>
|
||
<p class="p_Normal" style="margin: 0 0 0 48px;">4. Added the ability to bind the business calendar to a user profile.</p>
|
||
<p class="p_Normal" style="margin: 0 0 0 48px;">5. Working time calculation methods now take into account scheduled changes in business calendars.</p>
|
||
<p class="p_Normal" style="margin: 0 0 0 48px;">6. Added business calendar locking, which is opened in the editing mode.</p>
|
||
<p class="p_Normal" style="margin: 0 0 0 48px;">7. Corrected the texts of possible errors when working with business calendars.</p>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="2" class="p_Normal">TEAM-30160 Added a warning in the work calendar settings:</li></ol>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal">If a break time is specified earlier than the start or later than the end of the working time, a notification will appear.</li><li class="p_Normal">This schedule cannot be saved.</li></ul>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Widget designer</span></h2>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="1" class="p_Normal">TEAM-26431 Added the ability to place the same field on the form multiple times with value synchronization.</li></ol>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal">When a value is changed in one place, it is automatically updated in all other places on the form.</li><li class="p_Normal">It works for both editable and read-only fields.</li><li class="p_Normal">It solves the problem of unsynchronized values that previously caused confusion for users.</li></ul>
|
||
<p class="p_Normal" style="margin: 0 0 0 19px;">Usage example:</p>
|
||
<p class="p_Normal" style="margin: 0 0 0 19px;">A field is displayed on a tab and on the sidebar. When filled on the tab, the value is also updated on the sidebar.</p>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="2" class="p_Normal">TEAM-28484 Added checking for link type (multiple or single) when linking fields in widget settings.</li></ol>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal">Fields with different link types cannot be linked now.</li><li class="p_Normal">Multiple fields can only be linked to multiple fields.</li><li class="p_Normal">Fields that cannot be linked are highlighted in gray.</li></ul>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Document management</span></h2>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="1" class="p_Normal">TEAM-2646 Added the <span style="font-weight: bold;">Details</span> button in the <span style="font-weight: bold;">Signatures archive</span> to allow you to view detailed information about the signature and certificate.</li><li value="2" class="p_Normal">TEAM-20329 Implemented support for <span style="font-weight: bold;">.avif</span> images.</li><li value="3" class="p_Normal">TEAM-21707 Added support for <span style="font-weight: bold;">.tiff</span> and <span style="font-weight: bold;">.tif</span> files to the <span style="font-weight: bold;">File Preview</span> widget.</li><li value="4" class="p_Normal">TEAM-25392 Added option to select the <span style="font-weight: bold;">All users</span> group in <span style="font-weight: bold;">App signature</span> settings</li><li value="5" class="p_Normal">TEAM-26117 Added the <span style="font-weight: bold;">Error Handling</span> setting for the <span style="font-weight: bold;">Approval</span> and <span style="font-weight: bold;">Send Document/App Item</span> activities. Added escalation connector with ignore conditions.</li><li value="6" class="p_Normal">TEAM-30433 Added the <span style="font-weight: bold;">Registration number</span> field to the <span style="font-weight: bold;">Document</span> type apps to search for items by registration number.</li><li value="7" class="p_Normal">TEAM-31218 Added <span style="font-weight: bold;">.pdf</span> format selection for the <span style="font-weight: bold;">Generate from Template</span>, <span style="font-weight: bold;">Generate from File</span>, <span style="font-weight: bold;">Insert Watermark</span>, and <span style="font-weight: bold;">Convert to PDF</span> activities.</li></ol>
|
||
<p class="p_Normal" style="margin: 0 0 0 19px;">Available format choices:</p>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal" style="margin-top: 0; margin-right: 0; margin-bottom: 0;"><span style="font-weight: bold;">.pdf1.7</span>.</li><li class="p_Normal" style="margin-top: 0; margin-right: 0; margin-bottom: 0;"><span style="font-weight: bold;">.pdf/a-1a</span> (default for processor blocks).</li><li class="p_Normal" style="margin-top: 0; margin-right: 0; margin-bottom: 0;"><span style="font-weight: bold;">.pdf/a-1b</span>.</li></ul>
|
||
<p class="p_Normal" style="margin: 0 0 0 19px;">For scripts:</p>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal" style="margin-top: 0; margin-right: 0; margin-bottom: 0;">Insert Watermark: <span style="font-weight: bold; background-color: #ffffff;">.pdf/a-1a</span><span style="background-color: #ffffff;">.</span></li><li class="p_Normal" style="margin-top: 0; margin-right: 0; margin-bottom: 0;"><span style="background-color: #ffffff;">Convert to PDF: </span><span style="font-weight: bold; background-color: #ffffff;">.pdf/a-1a</span><span style="background-color: #ffffff;">.</span></li><li class="p_Normal" style="margin-top: 0; margin-right: 0; margin-bottom: 0;"><span style="background-color: #ffffff;">Preview and Print form: </span><span style="font-weight: bold; background-color: #ffffff;">.pdf1.7</span><span style="background-color: #ffffff;">.</span></li></ul>
|
||
<ol style="list-style-type:decimal" start="8">
|
||
<li value="8" class="p_Normal"><span style="background-color: #ffffff;">TEAM-31228 Added </span><span style="font-weight: bold; background-color: #ffffff;">.docx </span><span style="background-color: #ffffff;">and</span><span style="font-weight: bold; background-color: #ffffff;"> .xlsx</span><span style="background-color: #ffffff;"> documents display in the </span><span style="font-weight: bold; background-color: #ffffff;">Files</span><span style="background-color: #ffffff;"> workspace when MS Office module is not present.</span></li><li value="9" class="p_Normal"><span style="background-color: #ffffff;">TEAM-31325 Added warning when there are conditions in escalation connector when validating and publishing a process.</span></li></ol>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal"><span style="background-color: #ffffff;">Conditions in escalation connector are now ignored but not removed.</span></li><li class="p_Normal"><span style="background-color: #ffffff;">The user receives a notification when conflicting conditions are present.</span></li></ul>
|
||
<p class="p_Normal" style="margin: 0 0 0 19px;"><span style="background-color: #ffffff;">Operation example:</span></p>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="1" class="p_Normal" style="margin-top: 0; margin-right: 0; margin-bottom: 0;"><span style="background-color: #ffffff;">Create a process with the </span><span style="font-weight: bold; background-color: #ffffff;">Approval</span><span style="background-color: #ffffff;"> activity.</span></li><li value="2" class="p_Normal" style="margin-top: 0; margin-right: 0; margin-bottom: 0;">Configure outgoing transitions for the <span style="font-weight: bold;">Approval</span> activity<span style="background-color: #ffffff;"> with conditions and escalation.</span></li><li value="3" class="p_Normal" style="margin-top: 0; margin-right: 0; margin-bottom: 0;"><span style="background-color: #ffffff;">When publishing a process and starting a task with escalation, the transition is performed according to the escalation settings, ignoring conditions.</span></li></ol>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Projects</span></h2>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="1" class="p_Normal">TEAM-27914 Added the <span style="font-weight: bold;">Linked project tasks</span> widget to display a list of linked tasks on project task pages.</li><li value="2" class="p_Normal">TEAM-27930 Added the <span style="font-weight: bold;">Participants</span> (multiple) field to project tasks. Participants are granted rights to view tasks and are automatically added to the field of the same name when the calendar is published.</li><li value="3" class="p_Normal">TEAM-28241 Improved calendar import:</li></ol>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal">Unsupported field types are ignored.</li><li class="p_Normal">Empty critical fields are autofilled with the values: <span style="font-weight: bold;">Type = Task</span>, <span style="font-weight: bold;">Control = Notify when the task is completed</span>.</li></ul>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="4" class="p_Normal">TEAM-28727 Added the ability to set color schemes for Gantt chart in Project Settings.</li><li value="5" class="p_Normal">TEAM-31039 Notifications to the project activity stream when the <span style="font-weight: bold;">Generate from template</span> process starts are disabled by default. Logging can be enabled in the process settings.</li><li value="6" class="p_Normal">TEAM-31094 Auto-scrolling when dragging and dropping tasks has been added to the Gantt chart in project plans.</li></ol>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Chats and messages</span></h2>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="1" class="p_Normal">TEAM-15410 Added the ability to forward messages in chats and live chats. Find a message, click <span style="font-weight: bold;">Forward</span>, select a chat and send it.</li></ol>
|
||
<p class="p_Normal" style="margin: 0 0 0 24px;">Additionally:</p>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal">You can add a comment to the forwarded message.</li><li class="p_Normal">The search for forwarding chats starts with three characters.</li><li class="p_Normal">Only 10 most recently active chats are displayed.</li><li class="p_Normal">Forwarding forwarded messages is not yet available.</li></ul>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="2" class="p_Normal">TEAM-28102 Implemented dynamic loading of 10 items when scrolling through chats and #Activity stream objects.</li></ol>
|
||
<p class="p_Normal" style="margin: 0 0 0 19px;">Tech support chat is fixed at the bottom of the list when scrolling.</p>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="3" class="p_Normal">TEAM-28604 Expanded reaction options.</li></ol>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal">Added new emoji for reactions.</li><li class="p_Normal">Frequently used reactions are displayed separately, above the list.</li></ul>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="4" class="p_Normal">TEAM-30382 The group chat list is now updated without reloading the page after deleting a user.</li></ol>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">App items display</span></h2>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="1" class="p_Normal">TEAM-28200 Added the <span style="font-weight: bold;">Open app item page after creation option</span><span style="font-size: 15px; font-family: Calibri,Vectora,'Droid Sans','Open Sans',Frutiger,sans-serif;">,</span> in the <span style="font-weight: bold;">Save </span>button settings. It can be enabled for buttons on the create form, opens the item page automatically after saving.</li><li value="2" class="p_Normal">TEAM-29632 Added eager fetching of related item data on the app page when displayed as a table, tiles, or kanban board. In this case, the item page displays the <span style="font-weight: bold;">more items</span> text instead of the number of linked objects.</li></ol>
|
||
<p class="p_Normal" style="margin: 0 0 0 19px;">Activation requires the <code><b>eagerLoadAppItemsEnabled</b></code> feature flag to be enabled.</p>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="3" class="p_Normal">TEAM-30569: Differentiated display settings for the app list for administrators and users. The option to switch between user and global app settings has been added for the administrator. The button is available for <span style="font-weight: bold;">Tile</span>, <span style="font-weight: bold;">Table</span>, and <span style="font-weight: bold;">Board</span> modes and only on the main app page. For users, the <span style="font-weight: bold;">Default</span> button is now available, which resets the custom settings for <span style="font-weight: bold;">Tiles</span>, <span style="font-weight: bold;">Table</span>, and <span style="font-weight: bold;">Board</span> to the settings made by the administrator.</li></ol>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Modules</span></h2>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="1" class="p_Normal">TEAM-29543 <span style="font-weight: bold;">MyDSS</span> module is hidden from the basic edition. If needed, the customers can follow the link from the BRIX Store and enable it.</li></ol>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Administration</span></h2>
|
||
<p class="p_Normal">TEAM-26134 Added version number display to the <span style="font-weight: bold;">Administration</span> workspace main page.</p>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Mobile application</span></h2>
|
||
<p class="p_Normal">TEAM-25899 The new <span style="font-weight: bold;">Home</span> page has been added to the company settings in <span style="font-weight: bold;">Administration > Company Settings > Mobile app start page</span>.</p>
|
||
<p class="p_Normal">Administrators can now select <span style="font-weight: bold;">Home</span> as the start page of the mobile application.</p>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">External portal</span></h2>
|
||
<p class="p_Normal">TEAM-13060 Added pages 403 and 412 for the <span style="font-weight: bold;">External portal</span>.</p>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Bugs fixed</span></h2>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="1" class="p_Normal">TEAM-30300 The <code><b>delete()</b></code> method has been removed from the available list for <code><b>DefaultWorkCalendar</b></code>. It is now unavailable for execution and is excluded from Help because the company<span style="color: #202122; background-color: #ffffff;">’</span>s base work calendar should not be deleted.</li><li value="2" class="p_Normal"><span style="background-color: #ffffff;">TEAM-31418</span><span style="color: #394149; background-color: #ffffff;"> </span>Fixed an issue where when performing a search by field of the <span style="font-weight: bold;">Report</span> type in the <span style="font-weight: bold;">SD Reports</span> widget on the <span style="font-weight: bold;">Service Desk Reports</span> page. It occurred during page initialization and caused a failure when loading data. After the fix, the search runs correctly and the issue no longer occurs.</li><li value="3" class="p_Normal">TEAM-31497 Fixed an issue where a business process was missing from the initial workspace after an export/import within the same company. The issue occurred due to incorrect copying of the process, which also prevented the business process from running when the start button was clicked on the app page.</li><li value="4" class="p_Normal">TEAM-31512 Fixed an issue where the user search bar from the <span style="font-weight: bold;">Administration > Users</span> workspace would not disappear when going to <span style="font-weight: bold;">Error Monitor</span>.</li><li value="5" class="p_Normal">TEAM-27513 Improved the <span style="font-weight: bold;">Await Status</span> activity to take into account possible object replacement during process execution. Previously, the activity froze if a subscription was formed for one object, but in the process it was changed to another object due to a mismatch between their IDs. Now we have implemented correct handling of such situations, including manual changes of an object, changes via scripts, custom extensions and other process activities. The <span style="font-weight: bold;">Await Status</span> activity is re-subscribed to the new object, and error handling for empty variable values with the possibility to restore the process, script, custom extensions and other process blocks is also provided.</li><li value="6" class="p_Normal">TEAM-26395 Fixed an issue where a widget or page was not exported if the scripts contained only an interface declaration with no additional code.</li><li value="7" class="p_Normal">TEAM-27578 Fixed an issue where an incorrectly entered password caused incorrect account lockout for an external user and error 412 in the interface. Now when the limit of unsuccessful login attempts is reached, the system correctly locks the user and displays the <span style="font-weight: bold;">“Failed to retrieve user data”</span> message.</li><li value="8" class="p_Normal">TEAM-30076 Fixed an issue that caused existing app processes to not be suggested when accessing processes via <code><b>.fields</b></code>. The issue occurred after the 2024.7 update and made it difficult to use scripts that access processes via <code><b>.fields</b></code>.</li><li value="9" class="p_Normal">TEAM-30230 Fixed an issue that caused the default value for a <span style="font-weight: bold;">Yes/No</span> type variable to not be set to <code><b>false</b></code>. As a result, when customizing the display of third-party items that depend on the value of this variable, a situation occurred where the variable value remained <code><b>undefined</b></code> and the item was not displayed correctly. After the fix, the variable is set to <code><b>false</b></code> by default.</li><li value="10" class="p_Normal">TEAM-30693 Fixed an issue that caused a required field of the <span style="font-weight: bold;">Money</span> type to pass validation after a value was removed from it. Now when the field is cleared, the system correctly displays the validation error and does not allow you to save or create an item before the field is filled in.</li><li value="11" class="p_Normal">TEAM-31422 The ability to re-import external users that were incorrectly created during the initial import has been added. Such users are now automatically assigned the <span style="font-weight: bold;">Data does not match</span> status and are displayed in the import interface for further correction. Additionally, the import operation is now atomic: either all required user entities (account, profile and bindings) are successfully created, or none are created.</li><li value="12" class="p_Normal">TEAM-31503 The issue of a missing warning about unsaved changes when exiting the <span style="font-weight: bold;">Event Handler</span> designer has been fixed. Now when the <span style="font-weight: bold;">Back</span> button is clicked, if changes were made in the Event Handler and they are not saved, the system correctly displays a warning about possible data loss.</li><li value="13" class="p_Normal">TEAM-31587 Fixed incorrect behavior of event handlers: now they react correctly to changes in publication status (enabling, disabling, de-publishing) without the need to reload the module, including handlers with dynamic filtering.</li><li value="14" class="p_Normal">TEAM-31624 The missing <code><b>elma365_telemetry_script_execution_duration_milliseconds_bucket</b></code> metric for script execution time monitoring has been added. Now with the <code><b>global.monitoring.lowcode.metricExportEnabled</b></code> parameter enabled, Prometheus displays all telemetry metrics including HTTP requests, SQL requests and script execution.</li><li value="15" class="p_Normal">TEAM-31644 Fixed an issue where the <span style="font-weight: bold;">“Namespace is not defined”</span> error occurred when calling an <span style="font-weight: bold;">API module</span> method. The issue occurred when trying to access module settings via <code><b>Namespace.params.data.my_setting</b></code>.</li><li value="16" class="p_Normal">TEAM-31660 A workspace import issue that occurred when changing the subtype of a property of the <span style="font-weight: bold;">Phone</span> type from <span style="font-weight: bold;">Main</span> to <span style="font-weight: bold;">Multiple</span> has been fixed. Now, when re-importing a workspace, the property settings are correctly updated, and an error like <span style="font-weight: bold;">“Unable to update the ... field because the field view settings are different”</span> does not occur anymore.</li><li value="17" class="p_Normal">TEAM-31833 Fixed an issue that caused business process activities from a module called via <code><b>Imports</b></code> to fail to work and result in the <span style="font-weight: bold;">“TypeError: Cannot read properties of undefined (reading ‘action’)”</span> error.</li><li value="18" class="p_Normal">TEAM-27234 Fixed an issue that caused workspace updates to not add new library files to widgets.</li><li value="19" class="p_Normal">TEAM-31561 Fixed an issue that caused validation to trigger for hidden fields on the create form. Mandatory fields hidden by a condition are now correctly ignored by validation as described in the help. The user can save the item if the field is not displayed on the form and validation does not interfere with the completion of the operation.</li><li value="20" class="p_Normal">TEAM-23162 Fixed an issue where the start and end dates of tasks did not match the plan. The problem occurred due to lack of work calendar accounting, especially for tasks with start and finish dates in previous periods. The export and import functions now include correct accounting of working days and days off in accordance with the working calendar set in the system.</li><li value="21" class="p_Normal">TEAM-23932 Fixed an issue in displaying watermark when signing an app of the <span style="font-weight: bold;">Document</span> type. In previous versions, the watermark was applied to both the <span style="font-weight: bold;">Document</span> type app and all fields with the <span style="font-weight: bold;">File</span> type located on the document page. Now the watermark is applied only to the <code><b>__file</b></code> field itself, it is not applied to other fields with the <span style="font-weight: bold;">File</span> type.</li><li value="22" class="p_Normal">TEAM-26229 In <span style="font-weight: bold;">Projects</span>, the logic of granting additional permissions for a specific user from the <span style="font-weight: bold;">Supervisor</span> field has been removed. By default, access rights are set within the app item, for the <span style="font-weight: bold;">Supervisor</span> field these are <span style="font-weight: bold;">View</span>, <span style="font-weight: bold;">Load</span>, <span style="font-weight: bold;">Edit</span>. The changes affect only new clients. Settings on the existing companies will be changed.</li><li value="23" class="p_Normal">TEAM-26910 The logic of project tasks execution has been improved. Now, when completing a task, the system checks for any preceding linked tasks that are unfinished (including milestones). If such tasks are found, the following warning message is displayed to the user: <span style="font-weight: bold;">“</span><span style="font-weight: bold;">Unfinished linked tasks found. Are you sure you want to complete the task?</span><span style="font-weight: bold;">”</span></li><li value="24" class="p_Normal">TEAM-27681 Fixed an issue with the project plan display in the Gantt Chart widget. Now, if a user does not have the access permissions to the <span style="font-weight: bold;">Project Task</span> app, they continue to see the Gantt chart and task list on the project view form, but cannot open the view form of a specific task if they do not have access to it.</li><li value="25" class="p_Normal">TEAM-28873 Fixed an issue that caused the file modification date to be updated when editing a project page, even if the file itself was not modified. Now the file modification date is changed only when the file contents are actually updated, and editing a project no longer affects this parameter.</li><li value="26" class="p_Normal">TEAM-28904 Fixed an issue with starting tasks of the <span style="font-weight: bold;">Process</span> type linked by the “End-Start” principle. Now, when the previous task is finished, the next task of the <span style="font-weight: bold;">Process</span> type is started automatically, taking into account the start date. If the start date is scheduled for the future, the task will start according to the calendar plan; if necessary, the user can force start it from the task view form.</li><li value="27" class="p_Normal">TEAM-30125 Fixed an issue that caused overdue project tasks notifications to occur even if the tasks were not overdue.</li><li value="28" class="p_Normal">TEAM-30444 Incorrect field names and order in the <span style="font-weight: bold;">Hierarchical Structure</span> widget have been fixed. New field names and their order are now as follows:</li></ol>
|
||
<p class="p_Normal" style="margin: 0 0 0 48px;">1. Root item.</p>
|
||
<p class="p_Normal" style="margin: 0 0 0 48px;">2. Field for creating hierarchy.</p>
|
||
<p class="p_Normal" style="margin: 0 0 0 48px;">3. Field for linking.</p>
|
||
<p class="p_Normal" style="margin: 0 0 0 48px;">4. Associated app items*.</p>
|
||
<p class="p_Normal" style="margin: 0 0 0 48px;">5. Fields of associated app to be displayed.</p>
|
||
<p class="p_Normal" style="margin: 0 0 0 48px;">6. Show structure without associated app items*.</p>
|
||
<ol style="list-style-type:decimal" start="29">
|
||
<li value="29" class="p_Normal">TEAM-30753 Fixed an issue where the item creation button remained available in the contract for users without access permissions. Now:</li></ol>
|
||
<p class="p_Normal" style="margin: 0 0 0 48px;">1. The source selection window for item creation <span style="font-weight: bold;">does not display apps</span> to which the user does not have permissions.</p>
|
||
<p class="p_Normal" style="margin: 0 0 0 48px;">2. The issue of freezing when trying to create an item has been fixed: after the access restriction warning, the endless loading no longer occurs.</p>
|
||
<p class="p_Normal" style="margin: 0 0 0 48px;">3. The item creation button is hidden for users without corresponding permissions.</p>
|
||
<ol style="list-style-type:decimal" start="29">
|
||
<li value="30" class="p_Normal">TEAM-30823 Added a restriction for selecting a completion date for a <span style="font-weight: bold;">Send Document/App Item</span> task. <span style="font-weight: bold;">Approval</span> or <span style="font-weight: bold;">Send Document/App Item</span> tasks are not created if the completion date is in the past.</li><li value="31" class="p_Normal">TEAM-30865 Fixed the contracts display in the mobile application.</li><li value="32" class="p_Normal">TEAM-31334 The interruption of the approval process when a user is locked out and the <span style="font-weight: bold;">Permission inheritance based on org chart subordination</span> option is disabled has been fixed. Now the <span style="font-weight: bold;">Approval</span> activity takes into account the organizational chart settings:</li></ol>
|
||
<p class="p_Normal" style="margin: 0 0 0 48px;">1. If the approving user is locked, the task is automatically transferred to the supervisor of the locked employee (according to organizational structure).</p>
|
||
<p class="p_Normal" style="margin: 0 0 0 48px;">2. The process continues to run and the supervisor is able to approve the task instead of the locked user.</p>
|
||
<ol style="list-style-type:decimal" start="29">
|
||
<li value="33" class="p_Normal">TEAM-31829 Fixed styles in the task list table header in the Gantt chart widget.</li><li value="34" class="p_Normal">TEAM-29058 Fixed an issue that allowed adding multiple users to a group of the <span style="font-weight: bold;">Role</span> type by editing the user page. Now, if you try to add more than one user to such a group, the system displays a correct <span style="font-weight: bold;">warning</span> and prohibits saving changes, keeping the setting that <span style="font-weight: bold;">Role</span> can contain only one user or position from the organizational chart.</li><li value="35" class="p_Normal">TEAM-30368 Support for exporting and importing groups for the <span style="font-weight: bold;">Add filter</span> option (<span style="font-weight: bold;">User</span> type field) has been finalized. Now:</li></ol>
|
||
<p class="p_Normal" style="margin: 0 0 0 48px;">1. Groups in property filters are written in the <code><b>${namespace}${code}</b></code> format instead of their id, preventing them from being lost during import.</p>
|
||
<p class="p_Normal" style="margin: 0 0 0 48px;">2. Implemented displaying a warning during export if the selected group is not part of the package and is not a system group.</p>
|
||
<p class="p_Normal" style="margin: 0 0 0 48px;">3. After import, filters correctly display groups if they are present on the target site.</p>
|
||
<p class="p_Normal" style="margin: 0 0 0 24px;">The support is implemented for:</p>
|
||
<ul style="list-style-type:disc">
|
||
<li class="p_Normal" style="margin-top: 0; margin-right: 0; margin-bottom: 0;">App properties.</li><li class="p_Normal" style="margin-top: 0; margin-right: 0; margin-bottom: 0;">Contract properties.</li><li class="p_Normal" style="margin-top: 0; margin-right: 0; margin-bottom: 0;">Process context.</li><li class="p_Normal" style="margin-top: 0; margin-right: 0; margin-bottom: 0;">Business process actions context.</li><li class="p_Normal" style="margin-top: 0; margin-right: 0; margin-bottom: 0;">Module settings.</li><li class="p_Normal" style="margin-top: 0; margin-right: 0; margin-bottom: 0;">Widget context.</li></ul>
|
||
<ol style="list-style-type:decimal" start="29">
|
||
<li value="36" class="p_Normal">TEAM-31155 Fixed an issue that caused the user page not to open when clicking on the user<span style="background-color: #ffffff;">’</span>s name in the notification about changing the task executor. Now the user page is loaded correctly and the <span style="font-weight: bold;">__id is required</span> error no longer occurs.</li><li value="37" class="p_Normal">TEAM-31472 Fixed an issue that caused the counter of unread posts in the activity stream to be reset when reloading page. Now the counter saves the number of unread messages and comments correctly even after page refresh, and the current value is displayed when new messages are received.</li><li value="38" class="p_Normal">TEAM-31555 Fixed an issue in the context menu of the message activity stream. The menu item is now called <span style="font-weight: bold;">Hide Process from List</span> for all business process objects. The previous name Do not show tasks in the list was incorrect, which caused confusion.</li><li value="39" class="p_Normal">TEAM-31555 Fixed an issue in the context menu of the message activity stream. The menu item is now called <span style="font-weight: bold;">Hide Process from List</span> for all business process objects. The previous name <span style="font-weight: bold;">Hide Tasks from List</span> was incorrect, which caused confusion.</li><li value="40" class="p_Normal">TEAM-31766 The ability to edit substitutions via TS SDK has been implemented. The <code><b>.save()</b></code> method now works correctly both for updating existing substitutions and for creating new ones via <code><b>System.replacements.create()</b></code>. The fix has eliminated an error occurring when trying to save changes in a substitution and ensured stable script execution in client and server scripts.</li></ol>
|
||
|
||
<div class="bottom-nav">
|
||
|
||
<a id="prev-link" class="topic__navi_prev" href="2025_1.html">
|
||
<span class="bottom-nav__arrow bottom-nav__arrow--prev"></span> <span
|
||
class="bottom-nav__link">2025_1.html</span>
|
||
</a>
|
||
|
||
|
||
<a id="next-link" class="topic__navi_next" href="2024_10.html">
|
||
<span class="bottom-nav__link">2024_10.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>
|