koziavin
00717a92fb
All checks were successful
Deploy Static Site / deploy (push) Successful in 6m6s
786 lines
36 KiB
HTML
786 lines
36 KiB
HTML
<div class="glossary-abc">
|
||
<div class="glossary-abc__nav-wrap">
|
||
<div class="glossary-abc__nav-wrap-inner">
|
||
<ul class="glossary-abc__nav">
|
||
<li><a href="#A">A</a></li>
|
||
<li><a href="#B">B</a></li>
|
||
<li><a href="#C">C</a></li>
|
||
<li><a href="#D">D</a></li>
|
||
<li><a href="#E">E</a></li>
|
||
<li><a href="#F">F</a></li>
|
||
<li><a href="#G">G</a></li>
|
||
<li><a href="#I">I</a></li>
|
||
<li><a href="#J">J</a></li>
|
||
<li><a href="#K">K</a></li>
|
||
<li><a href="#L">L</a></li>
|
||
<li><a href="#M">M</a></li>
|
||
<li><a href="#N">N</a></li>
|
||
<li><a href="#O">O</a></li>
|
||
<li><a href="#P">P</a></li>
|
||
<li><a href="#R">R</a></li>
|
||
<li><a href="#S">S</a></li>
|
||
<li><a href="#T">T</a></li>
|
||
<li><a href="#U">U</a></li>
|
||
<li><a href="#V">V</a></li>
|
||
<li><a href="#W">W</a></li>
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
<div class="glossary-abc__table-wrapper">
|
||
<table class="glossary-abc__table">
|
||
<caption>Eng</caption>
|
||
<tbody id="A">
|
||
<tr>
|
||
<th>A</th>
|
||
<td>Activity stream</td>
|
||
<td>The #Activity stream displays all the latest news from the news channels you are a member of, and system alerts.
|
||
In the #Activity stream you can view messages, comment, share files, and assign tasks to your coworkers.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>A</th>
|
||
<td>Additional parameters</td>
|
||
<td>Parameters for scripting within business processes.
|
||
Unlike context variables, whose value changes from instance to instance, the parameter remains the same for all process instances.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>A</th>
|
||
<td>Administrator</td>
|
||
<td>A BRIX user with the ability to create and modify user accounts, change settings, and assign access rights in the system.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>A</th>
|
||
<td>Advanced Mode</td>
|
||
<td>Advanced mode allows you to create and configure custom forms for the create, view, and edit pages of an app item. In particular,
|
||
you will be able to arrange form fields in the desired sequence, change their appearance, or specify which fields are mandatory and which are
|
||
read-only. You can also create a form template in Advanced Mode and set up the display of app items.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>A</th>
|
||
<td>Advanced search</td>
|
||
<td>A function that allows you to search for system objects by a set of parameters.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>A</th>
|
||
<td>App</td>
|
||
<td>BRIX component designed to create and store app and business process items.
|
||
For example, the <b>Companies</b> app is used to store data about specific legal entities, their addresses, phone numbers, etc.
|
||
Each specific company added to the <b>Companies</b> app and will be an item of it.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>A</th>
|
||
<td>App data export</td>
|
||
<td>Download the data stored in the app as a <b>.xlsx</b> or <b>.csv</b> file.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>A</th>
|
||
<td>App export</td>
|
||
<td>Download the app to an <b>.e365</b> file. When exporting an app, the following components are exported with it: business processes, customized statuses and filters,
|
||
counters, groups and roles, forms and context variables used in business processes,
|
||
button settings, pages, and separators.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>A</th>
|
||
<td>App item</td>
|
||
<td>A page in an app that displays certain information.
|
||
The app item is created by users and stores the data entered by them.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>A</th>
|
||
<td>App item page</td>
|
||
<td>The page that opens when you create, view, or edit an app item.
|
||
The pages have fields to fill in, such as name, contact person, phone number, etc.
|
||
In addition, tables, lists, and toggles can be added to the form to allow the user to select an option.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>A</th>
|
||
<td>App item/task/process start form</td>
|
||
<td>A form refers to the appearance of an app or task item page, as well as
|
||
the process start window. When setting up a form, you specify what data will be displayed on it and
|
||
what data will be available for editing.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>A</th>
|
||
<td>App status</td>
|
||
<td>Statuses are designed to track the current state of an app item.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>A</th>
|
||
<td>App visibility</td>
|
||
<td>The visibility settings determine which users will see
|
||
the app in the Workspace menu. The app can be hidden or
|
||
visible to specific employees, administrators, or user groups.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>A</th>
|
||
<td>Approval</td>
|
||
<td>The <b>Approval</b> graphical element is used to draw
|
||
document routes. It is placed at the point in the process where an employee,
|
||
such as a supervisor, must approve or reject a document.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>A</th>
|
||
<td>Assign Value</td>
|
||
<td>The <b>Assign Value</b> graphical element is used to automatically pass
|
||
data to the business process and establish a correspondence
|
||
between app fields and context variables.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>A</th>
|
||
<td>Associated activity stream</td>
|
||
<td>The activity stream displayed on the task, file, and app item pages.
|
||
In addition to messages from users, this activity stream displays the
|
||
event history of the associated object.</td>
|
||
</tr>
|
||
</tbody>
|
||
<tbody id="B">
|
||
<tr>
|
||
<th>B</th>
|
||
<td>BRIX Store</td>
|
||
<td>Catalog of ready-made solutions for BRIX.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>B</th>
|
||
<td>BRIX Store component</td>
|
||
<td>An off-the-shelf solution (a package of workspaces, apps, and processes) designed
|
||
to extend the basic capabilities of BRIX.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>B</th>
|
||
<td>Business process</td>
|
||
<td>A regularly repeated sequence of interrelated activities aimed at
|
||
creating a particular product or service for consumers. Besides,
|
||
consumers can be not only external customers but also internal customers.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>B</th>
|
||
<td>Business process associated with an app</td>
|
||
<td>A business process that is created within an app. When working with such a process,
|
||
the user can set up the form and app statuses without leaving the process designer.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>B</th>
|
||
<td>Business process associated with a workspace</td>
|
||
<td>Business processes at the workspace level describe the logic of its operation and can link multiple apps of a given workspace.
|
||
For example, for the <b>CRM</b> workspace, you can add a business process for order placement,
|
||
which will involve two apps: <b>Customers</b> and <b>Contract</b>.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>B</th>
|
||
<td>Business process associated with an app</td>
|
||
<td>A business process bound to the <b>Save</b> button on the app page. As soon
|
||
as the user adds a new item, the bound process is launched with its data.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>B</th>
|
||
<td>Business process context</td>
|
||
<td>All data that is created, modified, and stored during the execution of a particular process. For example, participant information, files, performer comments,
|
||
counterparts, forms, etc. This data is stored in variables whose
|
||
values are either set by the employees themselves during the process or determined
|
||
automatically by the system.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>B</th>
|
||
<td>Business process instance</td>
|
||
<td>An instance is created every time someone starts a published process in BRIX.</td>
|
||
</tr>
|
||
</tbody>
|
||
<tbody id="C">
|
||
<tr>
|
||
<th>C</th>
|
||
<td>Calendar event</td>
|
||
<td>A record of a non-periodic event.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>C</th>
|
||
<td>Channel</td>
|
||
<td>A tool for sharing information within teams and departments. With the help of channels, you can synchronize the work of employees,
|
||
share company news, notify your coworkers about a business trip or vacation, or introducte a new employee.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>C</th>
|
||
<td>Chat</td>
|
||
<td>Chats are used for personal interaction between employees, timely exchange of important
|
||
data, coordination of activities, and quick resolution of issues.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>C</th>
|
||
<td>Check list</td>
|
||
<td>A list of actions to be taken. A check list allows you to break down large tasks into steps and
|
||
plan your work step-by-step. Checklists can be created for
|
||
tasks, files, and app items.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>C</th>
|
||
<td>Company</td>
|
||
<td>BRIX workspace, which contains basic information about your
|
||
organization on separate pages: structure, employees,
|
||
absence schedule, substitutions, executive discipline, etc.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>C</th>
|
||
<td>Connector</td>
|
||
<td>A graphical element used to connect tasks, events, gateways, and other operations in a process flow chart. <b>The connector</b>
|
||
specifies the order in which actions are performed and defines the sequence of events in the process. Transition captions increase
|
||
the visibility of the flow chart and also serve as button names on task forms.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>C</th>
|
||
<td>Context variable</td>
|
||
<td>A value that changes its meaning from one process instance to another. For example, the <b>Initiator</b>
|
||
variable stores information about the specific user who started the business process
|
||
instance. The value of such a variable will be unique for each new instance.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>C</th>
|
||
<td>Contractor</td>
|
||
<td>A company with which the enterprise cooperates.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>C</th>
|
||
<td>Counters</td>
|
||
<td>A set of rules that are used to generate sequential numbers for app items.
|
||
For example, to assign a number to a document during registration.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>C</th>
|
||
<td>Custom form</td>
|
||
<td>A form designed and configured with a form builder for specific user or
|
||
company needs.</td>
|
||
</tr>
|
||
</tbody>
|
||
<tbody id="D">
|
||
<tr>
|
||
<th>D</th>
|
||
<td>Data/Field type</td>
|
||
<td>A characteristic of a data set that defines the range of its possible values, the
|
||
list of allowed operations, and the way the data set is stored.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>D</th>
|
||
<td>Deal</td>
|
||
<td>A BRIX object that stores information about an agreement that a company
|
||
has entered into with a specific counterparty.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>D</th>
|
||
<td>Deal Dynamics</td>
|
||
<td>A tool to get information about the current status of deals in the selected sales
|
||
pipeline. You can use it to track the status of transactions for a certain period.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>D</th>
|
||
<td>Department</td>
|
||
<td>An item of the organizational structure that designates one department of a
|
||
company and allows for the creation of groups and individual job positions
|
||
within it.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>D</th>
|
||
<td>Document</td>
|
||
<td>Document type app for creating documents in BRIX, such as contracts,
|
||
statements, invoices, etc.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>D</th>
|
||
<td>Document lifecycle</td>
|
||
<td>All stages (statuses) that a document goes through in the company from
|
||
creation to sending it to the archive or deletion.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>D</th>
|
||
<td>Document route</td>
|
||
<td>The path of document movement during document processing. Each stage of the
|
||
route has its own executor, specific tasks, and deadlines.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>D</th>
|
||
<td>Document template</td>
|
||
<td>A <b>.docx</b> or <b>.xlsx</b> file containing a specific set of variables. Variable values are
|
||
automatically filled in from data stored in the business process context.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>D</th>
|
||
<td>Document type app</td>
|
||
<td>The <b>Document</b> type app is intended for creating documents in BRIX, e.g.
|
||
contracts, apps, invoices, etc.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>D</th>
|
||
<td>Dynamic forms</td>
|
||
<td>Task forms or pages, the appearance of which can change depending on the
|
||
data entered by the user in the system during the work process. This allows
|
||
you not to overload your forms with fields and buttons but to show them only
|
||
when necessary.</td>
|
||
</tr>
|
||
</tbody>
|
||
<tbody id="E">
|
||
<tr>
|
||
<th>E</th>
|
||
<td>End Approval</td>
|
||
<td>The <b>End Approval</b> graphical element is used as an auxiliary for the
|
||
<b>Approval</b> item when building document movement routes. It is placed at the
|
||
point where a document needs to be finalized and a resolution needs to be
|
||
issued without waiting for the business process to end.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>E</th>
|
||
<td>End Event</td>
|
||
<td>Performs the termination of the process instance. When it is reached, the
|
||
process is considered complete.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>E</th>
|
||
<td>Event</td>
|
||
<td>Events affect the flow of a process or the timing of its individual steps.
|
||
They can start a process, suspend its execution, and terminate a particular branch. In
|
||
the flow chart, events are depicted as a circle. There are three basic types
|
||
of events: <b>Start</b>, <b>Intermediate</b>, and <b>End</b>.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>E</th>
|
||
<td>Event status</td>
|
||
<td>Increases the visibility of the calendar and allows you to quickly navigate to
|
||
scheduled events. If there are a large number of events, they can be sorted, for example, by <b>Open</b>, <b>Canceled</b>, or
|
||
<b>Closed,</b> status, which makes it easy to control the schedule.
|
||
</td>
|
||
</tr>
|
||
<tr>
|
||
<th>E</th>
|
||
<td>Event type app</td>
|
||
<td>With this type of app you can create calendars in different workspaces of the system.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>E</th>
|
||
<td>Exclusive Gateway</td>
|
||
<td>Activates process operation for only one of the outgoing connectors. It is
|
||
mandatory to set a default connector for this gateway.</td>
|
||
</tr>
|
||
</tbody>
|
||
<tbody id="F">
|
||
<tr>
|
||
<th>F</th>
|
||
<td>File</td>
|
||
<td><b>.docx</b>, <b>.xlsx</b>, and <b>.pdf documents</b>, images, audio, and video uploaded to BRIX
|
||
from the user<65>s computer or created directly in the system.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>F</th>
|
||
<td>Filter</td>
|
||
<td>Saved set of advanced object search parameters.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>F</th>
|
||
<td>Flow chart</td>
|
||
<td>A visual scheme that depicts the entire process: participants, tasks, events,
|
||
operations, and connectors between them. The process flow charts modeled in
|
||
BRIX are executable. This means that all tasks, notifications, etc. will automatically
|
||
come to the appropriate employees at the right stage after the flow chart is published.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>F</th>
|
||
<td>Folder</td>
|
||
<td>Folders are used to store and organize files. You can create and edit new folders and
|
||
manage access rights to them.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>F</th>
|
||
<td>Form builder</td>
|
||
<td>A tool that allows you to design and modify forms to create, edit, and view
|
||
apps, tasks, and events.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>F</th>
|
||
<td>Form template</td>
|
||
<td>Form templates are used when the functionality of a standard form is insufficient. The template
|
||
allows you to add new buttons and widgets, change field layout, etc. You can create form templates for
|
||
tasks, events, process instance pages, and apps.</td>
|
||
</tr>
|
||
</tbody>
|
||
<tbody id="G">
|
||
<tr>
|
||
<th>G</th>
|
||
<td>Gateway</td>
|
||
<td>Gateways represent decision points in the process. They are used to
|
||
direct the process along one branch or another, depending on certain conditions.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>G</th>
|
||
<td>Generate from template</td>
|
||
<td>The <b>Generate by template</b> graphical element is used to model the process flow chart. It allows
|
||
you to create documents using templates uploaded to BRIX. Generation is done at runtime,
|
||
with data from the process context automatically substituted into the generated document.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>G</th>
|
||
<td>Group</td>
|
||
<td>An item of an organizational structure that represents a group of users
|
||
with common job responsibilities.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>G</th>
|
||
<td>Group chat</td>
|
||
<td>A chat with at least three users. It allows you to synchronize work within your team, stay up-to-date on the latest events,
|
||
share files, and quickly resolve work issues.</td>
|
||
</tr>
|
||
</tbody>
|
||
<tbody id="I">
|
||
<tr>
|
||
<th>I</th>
|
||
<td>Inclusive OR-gateway</td>
|
||
<td>Activates the process of all outgoing connectors for which the transition condition is met.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>I</th>
|
||
<td>Instance summary page</td>
|
||
<td>The page that opens when you click on the process name in the
|
||
<b>Tasks > Assigned by me</b> workspace. It displays the start and end date,
|
||
process version, initiator name, and a process map showing the progress
|
||
of tasks in real time. If necessary, you can interrupt the execution of
|
||
an instance from its page.</td>
|
||
</tr>
|
||
</tbody>
|
||
<tbody id="J">
|
||
<tr>
|
||
<th>J</th>
|
||
<td>Job position</td>
|
||
<td>An item of the organizational structure denoting one employee of a company.
|
||
Examples of job positions: director, chief accountant, secretary, etc.</td>
|
||
</tr>
|
||
</tbody>
|
||
<tbody id="K">
|
||
<tr>
|
||
<th>K</th>
|
||
<td>Kanban board</td>
|
||
<td>A visual tool for tracking the current status of business processes. Each
|
||
column of the board corresponds to a certain stage of work. As the business process
|
||
is executed, items automatically move across the board from left to right,
|
||
showing the progress of execution.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>K</th>
|
||
<td>Key variable</td>
|
||
<td>A variable involved in the automatic generation of the app item name.</td>
|
||
</tr>
|
||
</tbody>
|
||
<tbody id="L">
|
||
<tr>
|
||
<th>L</th>
|
||
<td>Link</td>
|
||
<td>A link is added to the left menu of a page or workspace and
|
||
allows you to quickly navigate to a third-party Internet
|
||
resource or open a web document.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>L</th>
|
||
<td>Link to a folder</td>
|
||
<td>Links to folders help you organize your information and quickly
|
||
find folders you need or use frequently. A link can be
|
||
created in any folder.</td>
|
||
</tr>
|
||
</tbody>
|
||
<tbody id="M">
|
||
<tr>
|
||
<th>M</th>
|
||
<td>Main page</td>
|
||
<td>BRIX main page that is displayed immediately after the user logs into the
|
||
system or when you click on the main menu button.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>M</th>
|
||
<td>Manage Status</td>
|
||
<td>The <b>Manage Status</b> graphical element is applied only in those business processes
|
||
that use apps with customized statuses. With this graphical element you can automatically
|
||
change the status of the app at a particular stage of the process and control the
|
||
execution of work.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>M</th>
|
||
<td>Mentions</td>
|
||
<td>A convenient way to draw your colleagues<65> attention to a file, task,
|
||
or comment in a chat or channel. If you mention a person using the
|
||
<b>@</b> symbol, they receive a pop-up notification of your message.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>M</th>
|
||
<td>Multiple execution</td>
|
||
<td>A setting that allows you to assign a task simultaneously to all employees designated as executors of the swimlane.</td>
|
||
</tr>
|
||
</tbody>
|
||
<tbody id="N">
|
||
<tr>
|
||
<th>N</th>
|
||
<td>Notifications</td>
|
||
<td>The <b>Notifications</b> graphical element is used when modeling a business process
|
||
and is located in those areas where users need to be informed about important events,
|
||
for example, about approval or rejection of a document, payment of an invoice, etc.</td>
|
||
</tr>
|
||
</tbody>
|
||
<tbody id="O">
|
||
<tr>
|
||
<th>O</th>
|
||
<td>Organizational Chart</td>
|
||
<td>Presents the structure of the organization in the form of
|
||
a flow chart that reflects the entire hierarchy of the enterprise
|
||
(position, department, and division).</td>
|
||
</tr>
|
||
<tr>
|
||
<th>O</th>
|
||
<td>Org chart item</td>
|
||
<td>Component of the graphical model of the organizational
|
||
structure (department, job position, and group).</td>
|
||
</tr>
|
||
</tbody>
|
||
<tbody id="P">
|
||
<tr>
|
||
<th>P</th>
|
||
<td>Page</td>
|
||
<td>A component of the system on which you can place widgets to display
|
||
desired information. You can create a page either within a workspace or in the
|
||
left menu of the main page.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>P</th>
|
||
<td>Parallel Gateway</td>
|
||
<td>Activates process operation for all outgoing connectors.
|
||
Required to run a process on multiple routes at the same time.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>P</th>
|
||
<td>Parent task</td>
|
||
<td>A task that is decomposed into subtasks, i.e. from which page subtasks are created.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>P</th>
|
||
<td>Personal calendar</td>
|
||
<td>A workspace of the system that allows you to schedule work activities:
|
||
create events and meetings and view the calendars of subordinates. It also displays
|
||
events from the calendars of other workspaces with which the current user
|
||
is related in any way.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>P</th>
|
||
<td>Process debugging</td>
|
||
<td>The stage of business process development during which errors are detected and corrected. During debugging,
|
||
the process is reproduced step-by-step in real time. This way you can check the logic of operations, evaluate
|
||
how convenient and clear the task forms are set up, and make sure that all scripts work correctly.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>P</th>
|
||
<td>Process designer</td>
|
||
<td>A section of the system designed for modeling business processes.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>P</th>
|
||
<td>Process map</td>
|
||
<td>A graphical representation of a process that shows the progress of a
|
||
process instance and the current operations on it.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>P</th>
|
||
<td>Process monitor</td>
|
||
<td>An analytical tool for system administrators to monitor the status
|
||
of processes in real time.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>P</th>
|
||
<td>Process participant</td>
|
||
<td>Executor of a swimlane.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>P</th>
|
||
<td>Process publishing</td>
|
||
<td>For a process to become executable, it must be published.
|
||
After that, the process will run automatically. Tasks will be
|
||
assigned to executors, notifications will be sent, and the process
|
||
will be suspended according to its flow chart.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>P</th>
|
||
<td>Process task</td>
|
||
<td>A task assigned as part of a business process. Executing
|
||
a process task ensures that the process instance is completed and
|
||
the required result is achieved.</td>
|
||
</tr>
|
||
</tbody>
|
||
<tbody id="R">
|
||
<tr>
|
||
<th>R</th>
|
||
<td>Registration</td>
|
||
<td>The <b>Registration</b> graphical element helps to organize document
|
||
accounting and control within the company by assigning a registration number (index)
|
||
to the document.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>R</th>
|
||
<td>Revenue Forecast</td>
|
||
<td>Report on planned cash receipts: amount, status, planned date, etc.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>R</th>
|
||
<td>Role</td>
|
||
<td>Roles are used to set up access to files, documents, apps, app items, workspaces, and to define
|
||
performers in business process swimlanes. Only one user or job position from the organizational structure
|
||
can have a role. </td>
|
||
</tr>
|
||
</tbody>
|
||
<tbody id="S">
|
||
<tr>
|
||
<th>S</th>
|
||
<td>Sales pipeline</td>
|
||
<td>The principle of allocating deals to stages of the sales process.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>S</th>
|
||
<td>Schedule compliance</td>
|
||
<td>The ratio of the number of tasks completed on time to the total number of assigned tasks. It is
|
||
calculated as a percentage and includes tasks that are currently closed since the beginning of the month.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>S</th>
|
||
<td>Script</td>
|
||
<td>TypeScript code that allows you to access business process data, create, request, modify, delete app items
|
||
and interact with external systems over HTTP.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>S</th>
|
||
<td>Separator</td>
|
||
<td>A separator is used to group apps within a workspace. It visually
|
||
separates apps from each other with a dividing line.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>S</th>
|
||
<td>Start Event</td>
|
||
<td>Initiates the start of the process and specifies at what point it begins. A process
|
||
can contain only one <b>Start Event</b>.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>S</th>
|
||
<td>Start Process</td>
|
||
<td>In modeling, the Start Process item is used to decompose and make flow charts more visual. It allows
|
||
you to call a subprocess within the parent process. A subprocess is essentially an independent business
|
||
process whose functionality is part of a larger parent process.</td>
|
||
<tr>
|
||
<th>S</th>
|
||
<td>Substitution</td>
|
||
<td>Temporary fulfillment of the duties of an absent employee by another employee. There are three
|
||
types of substitution in BRIX: informing, task reassignment, and completing transfer of access
|
||
permissions. They differ by the set of rights that are transferred.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>S</th>
|
||
<td>Supervisor</td>
|
||
<td>The system role to which the user who created the company in BRIX is assigned by default. The
|
||
supervisor has full rights and receives tasks for the business process in case the executor
|
||
could not be identified automatically.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>S</th>
|
||
<td>Swimlane</td>
|
||
<td>Determines the performer of tasks placed in a swimlane.</td>
|
||
</tr>
|
||
</tbody>
|
||
<tbody id="T">
|
||
<tr>
|
||
<th>T</th>
|
||
<td>Tables</td>
|
||
<td>A special type of app field. By adding it to the app form, you will be able
|
||
to structure data by rows and columns, change its appearance, and insert
|
||
special formulas that will perform calculations.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>T</th>
|
||
<td>Task</td>
|
||
<td>One of the tools for organizing work within a company. Employees can set
|
||
deadlines and track tasks, share necessary information and documents to
|
||
achieve desired results on time.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>T</th>
|
||
<td>Task page</td>
|
||
<td>The page that opens when you click on the task name. It displays all the information you need to complete the task: description,
|
||
attachments, deadlines, participants, task initiator, and completion percentage.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>T</th>
|
||
<td>Task participant</td>
|
||
<td>A user that works on the task but is not
|
||
responsible for its execution.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>T</th>
|
||
<td>Timer intermediate event</td>
|
||
<td>Suspends the process for a certain amount of time. The number of intermediate events is
|
||
unlimited: they can be located at any interval between the initial and final events.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>T</th>
|
||
<td>Token</td>
|
||
<td>A token is used to authorize API requests , for example, to retrieve app
|
||
items or run a business process from an external system.</td>
|
||
</tr>
|
||
</tbody>
|
||
<tbody id="U">
|
||
<tr>
|
||
<th>U</th>
|
||
<td>User account</td>
|
||
<td>User login and password required to log in to the BRIX system and provide
|
||
access to personal data and settings.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>U</th>
|
||
<td>User group</td>
|
||
<td>Groups are used to customize access to files, documents, apps,
|
||
app items, workspaces, and define executors in swimlanes in business processes.</td>
|
||
</tr>
|
||
</tbody>
|
||
<tbody id="V">
|
||
<tr>
|
||
<th>V</th>
|
||
<td>Version of a business process</td>
|
||
<td>Represents one version of a business process. Versions differ by
|
||
sequence number, status, date of creation, version creator, and description.</td>
|
||
</tr>
|
||
</tbody>
|
||
<tbody id="W">
|
||
<tr>
|
||
<th>W</th>
|
||
<td>Webhook</td>
|
||
<td>The <b>Webhook</b> graphical element is used to model a
|
||
process. It allows the automatic transfer of process
|
||
instance information from BRIX to an external system.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>W</th>
|
||
<td>Widget</td>
|
||
<td>An interface element or a small auxiliary app with specific functionality for
|
||
tasks such as uploading a file, displaying instructions, activity stream,
|
||
user list, performing automatic calculations, etc.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>W</th>
|
||
<td>Workspace</td>
|
||
<td>A workspace brings together one or more apps linked by a common theme. For example,
|
||
apps such as <b>Contract</b>, <b>Order</b>, <b>Memo</b> and <b>Report</b> can be compiled within the <b>Documents</b>
|
||
workspace. The function of workspaces is primarily organizational.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>W</th>
|
||
<td>Workspace calendar</td>
|
||
<td>A calendar created using an <b>Event</b> type app in a specific workspace.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>W</th>
|
||
<td>Workspace export</td>
|
||
<td>Unload the workspace with all apps.</td>
|
||
</tr>
|
||
<tr>
|
||
<th>W</th>
|
||
<td>Workspace visibility</td>
|
||
<td>The visibility settings determine which users will see the workspace in the
|
||
left menu of the home page. The workspace can be hidden or made visible to specific
|
||
employees, administrators, or user groups.</td>
|
||
</tr>
|
||
</tbody>
|
||
</table>
|
||
</div>
|
||
</div> |