koziavin
00717a92fb
All checks were successful
Deploy Static Site / deploy (push) Successful in 6m6s
209 lines
26 KiB
HTML
209 lines
26 KiB
HTML
<!DOCTYPE html>
|
||
<html lang="en">
|
||
|
||
<head>
|
||
<title>Work with contract fields</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="When you work with a contract, you work with items from source apps added to it. These can be BRIX apps from any workspaces or solutions. To add a new source and configure the..." />
|
||
<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="contract.html">Contract</a> / Work with contract fields</p>
|
||
</div>
|
||
|
||
</div>
|
||
<div class="topic__title"><h1 class="p_Heading1"><span class="f_Heading1">Work with contract fields</span></h1>
|
||
</div>
|
||
|
||
</header>
|
||
<section class="article__content">
|
||
<div class="scroll-top-inner">
|
||
<a href="#h1-article" class="scroll-top"></a>
|
||
</div>
|
||
<!-- Placeholder for topic body. -->
|
||
<p style="line-height: 1.20; margin: 0 0 11px 0;"><span style="font-size: 15px; font-family: Inter;">When you work with a contract, you work with items from <a href="add-contract-source.html" class="topiclink">source apps</a> added to it. These can be BRIX apps from any workspaces or solutions. To add a new source and configure the way its fields are displayed on a contract’s page, you need to match the source app’s fields with the contract’s fields. After that, values of the app’s fields will be passed to the contract</span><span style="font-family: Inter;">’s</span><span style="font-size: 15px; font-family: Inter; font-weight: bold;"> </span><span style="font-size: 15px; font-family: Inter;">fields. You will be able to use them as variables in business processes and scripts.</span></p>
|
||
<p style="line-height: 1.20; margin: 0 0 11px 0;"><span style="font-size: 15px; font-family: Inter;">There are two groups of fields used in contracts:</span></p>
|
||
<ul style="list-style-type:disc">
|
||
<li style="line-height: 1.20; margin-top: 0; margin-right: 0; margin-bottom: 11px;"><span style="font-family: Inter; font-weight: bold;">System fields</span><span style="font-family: Inter;">. These are properties added to each contract by default. Most of them correspond to fields that exist in each BRIX app: </span><span style="font-family: Inter; font-weight: bold;">ID</span><span style="font-family: Inter;">, </span><span style="font-size: 15px; font-family: Inter; font-weight: bold;">Created on</span><span style="font-size: 15px; font-family: Inter;">, </span><span style="font-size: 15px; font-family: Inter; font-weight: bold;">Author</span><span style="font-size: 15px; font-family: Inter;">, </span><span style="font-size: 15px; font-family: Inter; font-weight: bold;">Changed</span><span style="font-size: 15px; font-family: Inter;">, </span><span style="font-size: 15px; font-family: Inter; font-weight: bold;">Editor</span><span style="font-size: 15px; font-family: Inter;">, </span><span style="font-size: 15px; font-family: Inter; font-weight: bold;">Deleted</span><span style="font-size: 15px; font-family: Inter;">, and </span><span style="font-size: 15px; font-family: Inter; font-weight: bold;">Name</span><span style="font-size: 15px; font-family: Inter;">. There is also a special field added only to contracts: </span><span style="font-size: 15px; font-family: Inter; font-weight: bold;">Link to original</span><span style="font-size: 15px; font-family: Inter;">. This field helps to link the contract item with the original app item. This field is convenient when you need to access the original app item in business processes or scripts.</span></li></ul>
|
||
<p style="line-height: 1.20; margin: 0 0 11px 34px;"><span style="font-family: Inter;">System fields cannot be deleted. When you add a new source to the contract, the app’s and the contract’s system fields are matched automatically.</span></p>
|
||
<ul style="list-style-type:disc">
|
||
<li style="line-height: 1.20; margin-top: 0; margin-right: 0; margin-bottom: 11px;"><span style="font-family: Inter; font-weight: bold;">Custom fields</span><span style="font-family: Inter;">. To let other app properties (apart from system fields) be passed to the contract, you need to add fields to link them to the contract’s context. Note that to let contract and source fields be properly matched and linked, their <a href="360009707032.html" class="topiclink">types</a> need to be the same. Before you add a new source, make sure the app includes fields that can be matched with each field of the contract. Otherwise, it will be impossible to link the app to the contract.</span></li></ul>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Add contract fields</span></h2>
|
||
<p style="line-height: 1.20; margin: 0 0 11px 0;"><span style="font-size: 15px; font-family: Inter;">You can add custom fields to a contract while creating it, in the </span><span style="font-size: 15px; font-family: Inter; font-weight: bold;">Form Settings </span><span style="font-size: 15px; font-family: Inter;">window. If you skipped this step or if you need to change the contract’s properties, you can do it in contract settings</span><span style="font-size: 15px; font-family: Inter; font-weight: bold;">.</span></p>
|
||
<p style="line-height: 1.20; margin: 0 0 11px 0;"><span style="font-size: 15px; font-family: Inter;">When you add fields, keep in mind that each source app that is going to be linked with the contract needs to include a field of the same type for each field of the contract. Otherwise, it will be impossible to link them.</span></p>
|
||
<p style="line-height: 1.20; margin: 0 0 11px 0;"><span style="font-size: 15px; font-family: Inter;">To open the contract settings:</span></p>
|
||
<ol style="list-style-type:upper-roman">
|
||
<li value="1" style="line-height: 1.20; margin-top: 0; margin-right: 0; margin-bottom: 11px;"><span style="font-size: 15px; font-family: Inter;">Click the gear icon to the right of the contract’s name.</span></li><li value="2" style="line-height: 1.20; margin-top: 0; margin-right: 0; margin-bottom: 11px;"><span style="font-size: 15px; font-family: Inter;">In the menu that opens, select </span><span style="font-size: 15px; font-family: Inter; font-weight: bold;">Contract Fields</span><span style="font-size: 15px; font-family: Inter;">.</span></li><li value="3" style="line-height: 1.20; margin-top: 0; margin-right: 0; margin-bottom: 11px;"><span style="font-size: 15px; font-family: Inter;">The </span><span style="font-size: 15px; font-family: Inter; font-weight: bold;">Contract Settings</span><span style="font-size: 15px; font-family: Inter;"> page with a list of all added properties opens. Click </span><span style="font-size: 15px; font-family: Inter; font-weight: bold;">+Add</span><span style="font-size: 15px; font-family: Inter;">.</span></li></ol>
|
||
<p style="line-height: 1.20; margin: 0 0 11px 34px;"><img alt="set-up-contract-fields-1" width="739" height="506" style="margin:0;width:739px;height:506px;border:none" src="set-up-contract-fields-1.png"/></p>
|
||
<ol style="list-style-type:upper-roman">
|
||
<li value="4" style="line-height: 1.20; margin-top: 0; margin-right: 0; margin-bottom: 11px;"><span style="font-size: 15px; font-family: Inter;">In the window that opens, select the </span><span style="font-size: 15px; font-family: Inter; font-weight: bold;">Type</span><span style="font-size: 15px; font-family: Inter; font-weight: bold; color: #ff0000;">*</span><span style="font-size: 15px; font-family: Inter;"> property and specify the </span><span style="font-size: 15px; font-family: Inter; font-weight: bold;">Display Name</span><span style="font-size: 15px; font-family: Inter; font-weight: bold; color: #ff0000;">*</span><span style="font-size: 15px; font-family: Inter;">. Specify other field settings that may vary depending on the <a href="360009707032.html" class="topiclink">property type</a>.</span></li><li value="5" style="line-height: 1.20; margin-top: 0; margin-right: 0; margin-bottom: 11px;"><span style="font-size: 15px; font-family: Inter;">Click </span><span style="font-size: 15px; font-family: Inter; font-weight: bold;">Create</span><span style="font-size: 15px; font-family: Inter;">. If you need to add another field, click </span><span style="font-size: 15px; font-family: Inter; font-weight: bold;">Create & Add New</span><span style="font-size: 15px; font-family: Inter;">. The new field will be displayed in the list of properties.</span></li><li value="6" style="line-height: 1.20; margin-top: 0; margin-right: 0; margin-bottom: 11px;"><span style="font-size: 15px; font-family: Inter;">Enable the <a href="360028941112.html#searchandsortbyfield" class="topiclink">Search and sort by field</a> option option for the property to search for items on the contract page by it. The <a href="360028941112.html#fulltextsearch" class="topiclink">Full text search</a> option is also available for fields of string type.</span></li></ol>
|
||
<p style="line-height: 1.20; margin: 0 0 11px 0;"><span style="font-size: 15px; font-family: Inter;">The new field will be displayed in the list of properties. To delete a property, select it in the list, click the </span><span style="font-size: 15px; font-family: Inter; font-weight: bold;">Delete</span><span style="font-size: 15px; font-family: Inter;"> button above the list on the right, and confirm the operation. Note that you cannot delete system fields from a contract.</span><a id="searchingbycontractfields" class="hmanchor"></a></p>
|
||
<p style="line-height: 1.20; margin: 0 0 11px 0;"><span style="font-size: 15px; font-family: Inter;">The property created in the contract is added to the source context. If it already contains a property with the same name and type, the contract and source fields will be automatically linked.</span></p>
|
||
<p style="line-height: 1.20; margin: 0 0 11px 0;"><span style="font-size: 15px; font-family: Inter;">Please note, that if a property with the same name but a different type is added to the source context, the contract-source link will be lost. Go to the <a href="add-contract-source.html#create-source" class="topiclink">contract source settings</a> and manually re-establish the link by matching fields of the same type.</span></p>
|
||
<p style="line-height: 1.20; margin: 0 0 11px 0;"><span style="font-size: 15px;">To delete a property from a contract, select it in the list, click the Delete button above the list on the right, and confirm the operation. Note that you cannot delete system fields from a contract.</span></p>
|
||
<h2 class="p_Heading2"><span class="f_Heading2">Example of mapping field</span></h2>
|
||
<p style="line-height: 1.20; margin: 0 0 11px 0;"><span style="font-size: 15px;">Let’s consider an example of how contract fields and source fields interact.</span></p>
|
||
<p style="text-align: justify; line-height: 1.20; margin: 0 0 11px 0;">Let’s say you created the <span style="font-weight: bold;">Contractor Documents </span>contract, and you want to link it with two apps, <span style="font-weight: bold;">Outgoing Contracts</span> and <span style="font-weight: bold;">Incoming Invoices</span>.</p>
|
||
<p style="text-align: justify; line-height: 1.20; margin: 0 0 11px 0;">A <span style="font-weight: bold;">Contract</span> is an empty interface that items from other apps are passed to. To link a contract with apps, you need to add custom properties to the contract’s context. Data from apps, such as contractor or amount information, will be passed to them. Please note, that an app cannot be properly linked with a contract if the contract doesn’t include fields of the same type.</p>
|
||
<p style="text-align: justify; line-height: 1.20; margin: 0 0 11px 0;">Go to <span style="font-weight: bold;">Contract Settings</span> <span style="font-weight: bold;">> Contract Fields</span> as described above. Click <span style="font-weight: bold;">+Add</span> and create a property with the name <span style="font-weight: bold;">Company</span> and <span style="color: #0000ff;"><a href="360009707032.html#app" class="topiclink">App</a></span> type. In its settings, select the <span style="color: #0000ff;"><a href="360012584980.html" class="topiclink">Companies</a></span> app from the <span style="font-weight: bold;">CRM</span> workspace. Add the <span style="font-weight: bold;">Amount</span> property with the <span style="color: #0000ff;"><a href="360009707032.html" class="topiclink">Money</a></span> type in the same way.</p>
|
||
<p style="text-align: justify; line-height: 1.20; margin: 0 0 11px 0;">Now you can go to <span style="font-weight: bold;">Source Settings</span> and add the <span style="font-weight: bold;">Outgoing Contracts</span> and <span style="font-weight: bold;">Incoming Invoices </span>apps to the contract. As you add these source apps, match the <span style="font-weight: bold;">Company</span> contract field with the <span style="font-weight: bold;">Contractor </span>field from both apps. Then link the <span style="font-weight: bold;">Amount</span> field with the <span style="font-weight: bold;">Contract amount </span>and<span style="font-weight: bold;"> Invoice amount </span>fields.</p>
|
||
<p style="text-align: justify; line-height: 1.20; margin: 0 0 11px 0;">Contract and source fields that match in name and type will be linked automatically.</p>
|
||
<p style="text-align: justify; line-height: 1.20; margin: 0 0 11px 0;">You can create an additional property of <span style="font-weight: bold;">App</span> type in the contract to write the value of the <span style="font-weight: bold;">Contract type</span> field from the <span style="font-weight: bold;">Outgoing Contracts</span> app into it. However, in this case, the contract’s link with the <span style="font-weight: bold;">Incoming Invoices</span> app may be lost if this source has a field with the same name but a different type. On the <span style="font-weight: bold;">Source Settings</span> page, this source will be highlighted in red.</p>
|
||
<p style="text-align: justify; line-height: 1.20; margin: 0 0 11px 0;">If there is no name match, a new field will be automatically created in the <span style="font-weight: bold;">Incoming Invoices</span> app.</p>
|
||
<p style="text-align: justify; line-height: 1.20; margin: 0 0 11px 0;"><span style="font-size: 13px; color: #000000;"> </span></p>
|
||
|
||
<div class="bottom-nav">
|
||
|
||
<a id="prev-link" class="topic__navi_prev" href="add-contract-source.html">
|
||
<span class="bottom-nav__arrow bottom-nav__arrow--prev"></span> <span
|
||
class="bottom-nav__link">add-contract-source.html</span>
|
||
</a>
|
||
|
||
|
||
<a id="next-link" class="topic__navi_next" href="contract-proccess.html">
|
||
<span class="bottom-nav__link">contract-proccess.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>
|