221 lines
23 KiB
HTML
221 lines
23 KiB
HTML
<!DOCTYPE html>
|
||
<html lang="en">
|
||
|
||
<head>
|
||
<title>Event statuses</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="Statuses increase the readability of the calendar and allow you to quickly navigate across scheduled events. If you have several appointments in your workspace calendar, you..." />
|
||
<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="360028290132.html">Event type apps</a> / Event statuses</p>
|
||
</div>
|
||
|
||
</div>
|
||
<div class="topic__title"><h1 class="p_Heading1" style="text-align: center; line-height: 1.20; margin: 19px 0 19px 0;"><span class="f_Heading1" style="font-size: 32px;">Event statuses</span></h1>
|
||
</div>
|
||
|
||
</header>
|
||
<section class="article__content">
|
||
<div class="scroll-top-inner">
|
||
<a href="#h1-article" class="scroll-top"></a>
|
||
</div>
|
||
<!-- Placeholder for topic body. -->
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;"><a href="360009920611.html" class="topiclink">Statuses</a> increase the readability of the calendar and allow you to quickly navigate across scheduled events. If you have several appointments in your <a href="360026962272.html" class="topiclink">workspace calendar</a>, you can sort them by the <span style="font-weight: bold;">Open, Canceled, Closed </span>statuses, and quickly find the right event. </p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">Events acquire new statuses either automatically within a business process, or users change them on the event page. Below we will describe both options. </p>
|
||
<h2 class="p_Heading2" style="line-height: 1.20; margin: 19px 0 0 0;"><span class="f_Heading2" style="font-size: 24px;">Set up event statuses and allow users to change them</span></h2>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 19px 0 0 0;">By default events in a workspace calendar have two statuses: <span style="font-weight: bold;">Closed</span> and <span style="font-weight: bold;">Open</span>. When somebody creates an event it acquires the <span style="font-weight: bold;">Open</span> status. To change the status, open the event <a href="360016427291.html#element_page" class="topiclink">page</a> and click <span style="font-weight: bold;">Close</span> at the bottom of the window. </p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 19px 0 0 0;"><img alt="event status 1" width="966" height="722" style="margin:0;width:966px;height:722px;border:none" src="hmfile_hash_3e888836.png"/></p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">After that, the status will change and the event will appear crossed out in the calendar. </p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">You can also create your own statuses for workspace calendars:</p>
|
||
<ol style="list-style-type:decimal">
|
||
<li value="1" class="p_Normal" style="line-height: 1.20; margin-top: 14px; margin-right: 0; margin-bottom: 0;">Click the gear icon next to the calendar name or the current date and select <span style="font-weight: bold;">Status Field</span>.</li><li value="2" class="p_Normal" style="line-height: 1.20; margin-top: 14px; margin-right: 0; margin-bottom: 0;">Enable the <span style="font-weight: bold;">Allow changing app status</span> option.</li><li value="3" class="p_Normal" style="line-height: 1.20; margin-top: 14px; margin-right: 0; margin-bottom: 0;">Set up the statuses by adding new ones or editing the existing ones.</li></ol>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">After that, the <span style="font-weight: bold;">Change</span> link will appear on event page next to the current status. By clicking on it, users will be able to select a new status from the list. The new status will be displayed on the event page.</p>
|
||
<p class="p_Normal">Additionally, you can add the <a href="button-types-settings.html#change_status_button" class="topiclink">Change status</a> button to the event page. To do so, open any event in the workspace calendar and click <img alt="gear icon" width="20" height="21" style="margin:0;width:20px;height:21px;border:none" src="hmfile_hash_8eb4920c.png"/>, then click<span style="font-weight: bold;"> Add "Change status" button</span>.</p>
|
||
<p class="p_Normal">To learn more about changing statuses manually, see <a href="360009920611.html" class="topiclink">Status field</a>.</p>
|
||
<p class="p_Normal">Statuses not only make the calendar easier to read, they also help find events quickly. For example, an HR employee can sort all interviews by the <span style="font-weight: bold;">Canceled</span> status. To do tat, in the <a href="360009669952.html" class="topiclink">search bar</a>, click <img alt="search" width="18" height="18" style="margin:0;width:18px;height:18px;border:none" src="search.png"/>, then click<span style="font-weight: bold;"> Status. </span>Select the status and click<span style="font-weight: bold;"> Search.</span></p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;"><img alt="event status 6" width="761" height="654" style="margin:0;width:761px;height:654px;border:none" src="hmfile_hash_4740f8e3.png"/></p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">The calendar will show all interviews with the <span style="font-weight: bold;">Canceled</span> status. </p>
|
||
<h2 class="p_Heading2" style="line-height: 1.20; margin: 19px 0 0 0;"><span class="f_Heading2" style="font-size: 24px;">Change event statuses automatically</span></h2>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 19px 0 0 0;">The event statuses can change automatically while executing a <a href="360008121732.html" class="topiclink">business process</a>. Such approach ensures that events timely get relevant statuses, and employees don't get distracted by unnecessary actions.</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">As an example, let’s consider the <span style="font-weight: bold;">Hiring</span> business process. During the process, the recruiter searches for candidates and at some point schedules <span style="font-weight: bold;">Interview</span> events that have three possible statuses: <span style="font-weight: bold;">Appointed</span>,<span style="font-weight: bold;"> Rejected</span>, and<span style="font-weight: bold;"> Successful</span>.</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">The process looks as follows:</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;"><img alt="event status 8" width="621" height="600" style="margin:0;width:621px;height:600px;border:none" src="hmfile_hash_23e99681.png"/></p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">The hiring manager chooses a CV of an applicant and conducts a phone interview. </p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">If the result of the interview is positive, the recruiter will schedule a personal interview. To do this, they indicate the date, time and participant of the meeting, the head of the department for which the candidate is selected.</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">The head of the department receives a task to approve the date and time of the interview.</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">As soon as the head of the department approves the time, this event is automatically added to the workspace calendar and assigns it the <span style="font-weight: bold;">Appointed </span>status.</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">Only the participants of this event can view it in their calendars.</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">Next, the hiring manager invites the candidate to the office for the interview. </p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">If, based on the results of the interview, the candidate approached the position, the process of registering a new employee is launched. In this case, the event status changes to <span style="font-weight: bold;">Successful</span>. If the decision was made to refuse the candidate, then the process ends, and the status of the event changes to <span style="font-weight: bold;">Rejected</span>.</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">To configure this business process, create the <a href="360026962272.html" class="topiclink">workspace calendar</a> for<span style="font-weight: bold;"> Interviews</span> and <a href="360009920611.html" class="topiclink">set up its statues</a>.</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">Now you need to bind the calendar and the process, i.e. create a new <a href="process_context.html" class="topiclink">process context variable</a> that will refer to the Interview event.</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">Note that when working with a calendar, the type of variable to use is always the <a href="360009707032.html#app" class="topiclink">App type</a>.</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">In its settings, in the <span style="font-weight: bold;">App</span> field select the <span style="font-weight: bold;">Interview</span> calendar. </p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;"><img alt="event status 9" width="640" height="520" style="margin:0;width:640px;height:520px;border:none" src="hmfile_hash_7ab5e013.png"/></p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">If you want new events to be automatically added to the workspace calendar, use the <a href="360019810892.html" class="topiclink">Create app item</a> activity. The system creates events using the data that the recruiter enters at the previous steps of the process. Thus the day and the time of the interview specified by the user and approved by the head of the department will be automatically added to the new event.</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">Now you need to add the <a href="360012263332.html" class="topiclink">Manage status</a> activity to the process. It will change the interview status at particular process steps.<span class="f_ImageCaption"> </span></p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;"><img alt="event status 10" width="622" height="601" style="margin:0;width:622px;height:601px;border:none" src="hmfile_hash_112aeb04.png"/></p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">Place these activities to those process steps where the event should change its status. Double click on the shape to configure the status settings:</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;"><img alt="event status 11" width="716" height="290" style="margin:0;width:716px;height:290px;border:none" src="hmfile_hash_173c01fc.png"/></p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;"> </p>
|
||
<ul style="list-style-type:disc">
|
||
<li style="line-height: 1.20;">Select the <span style="font-weight: bold;">Interview</span> variable that you created earlier.</li><li style="line-height: 1.20;">Select the status suitable for the particular point of the process.</li></ul>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">To learn more about how to configure status activity, see <a href="360012263332.html" class="topiclink">Manage status</a>.</p>
|
||
<p class="p_Normal" style="line-height: 1.20; margin: 14px 0 0 0;">After you publish the process, the status of the event will change automatically as users perform their tasks.</p>
|
||
|
||
<div class="bottom-nav">
|
||
|
||
<a id="prev-link" class="topic__navi_prev" href="event-element.html">
|
||
<span class="bottom-nav__arrow bottom-nav__arrow--prev"></span> <span
|
||
class="bottom-nav__link">event-element.html</span>
|
||
</a>
|
||
|
||
|
||
<a id="next-link" class="topic__navi_next" href="contract.html">
|
||
<span class="bottom-nav__link">contract.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>
|