| A | Activity stream | 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. |
|---|---|---|
| A | Additional parameters | 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. |
| A | Administrator | A BRIX user with the ability to create and modify user accounts, change settings, and assign access rights in the system. |
| A | Advanced Mode | 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. |
| A | Advanced search | A function that allows you to search for system objects by a set of parameters. |
| A | App | BRIX component designed to create and store app and business process items. For example, the Companies app is used to store data about specific legal entities, their addresses, phone numbers, etc. Each specific company added to the Companies app and will be an item of it. |
| A | App data export | Download the data stored in the app as a .xlsx or .csv file. |
| A | App export | Download the app to an .e365 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. |
| A | App item | A page in an app that displays certain information. The app item is created by users and stores the data entered by them. |
| A | App item page | 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. |
| A | App item/task/process start form | 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. |
| A | App status | Statuses are designed to track the current state of an app item. |
| A | App visibility | 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. |
| A | Approval | The Approval 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. |
| A | Assign Value | The Assign Value graphical element is used to automatically pass data to the business process and establish a correspondence between app fields and context variables. |
| A | Associated activity stream | 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. |
| B | BRIX Store | Catalog of ready-made solutions for BRIX. |
| B | BRIX Store component | An off-the-shelf solution (a package of workspaces, apps, and processes) designed to extend the basic capabilities of BRIX. |
| B | Business process | 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. |
| B | Business process associated with an app | 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. |
| B | Business process associated with a workspace | 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 CRM workspace, you can add a business process for order placement, which will involve two apps: Customers and Contract. |
| B | Business process associated with an app | A business process bound to the Save button on the app page. As soon as the user adds a new item, the bound process is launched with its data. |
| B | Business process context | 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. |
| B | Business process instance | An instance is created every time someone starts a published process in BRIX. |
| C | Calendar event | A record of a non-periodic event. |
| C | Channel | 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. |
| C | Chat | Chats are used for personal interaction between employees, timely exchange of important data, coordination of activities, and quick resolution of issues. |
| C | Check list | 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. |
| C | Company | BRIX workspace, which contains basic information about your organization on separate pages: structure, employees, absence schedule, substitutions, executive discipline, etc. |
| C | Connector | A graphical element used to connect tasks, events, gateways, and other operations in a process flow chart. The connector 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. |
| C | Context variable | A value that changes its meaning from one process instance to another. For example, the Initiator 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. |
| C | Contractor | A company with which the enterprise cooperates. |
| C | Counters | 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. |
| C | Custom form | A form designed and configured with a form builder for specific user or company needs. |
| D | Data/Field type | 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. |
| D | Deal | A BRIX object that stores information about an agreement that a company has entered into with a specific counterparty. |
| D | Deal Dynamics | 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. |
| D | Department | 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. |
| D | Document | Document type app for creating documents in BRIX, such as contracts, statements, invoices, etc. |
| D | Document lifecycle | All stages (statuses) that a document goes through in the company from creation to sending it to the archive or deletion. |
| D | Document route | The path of document movement during document processing. Each stage of the route has its own executor, specific tasks, and deadlines. |
| D | Document template | A .docx or .xlsx file containing a specific set of variables. Variable values are automatically filled in from data stored in the business process context. |
| D | Document type app | The Document type app is intended for creating documents in BRIX, e.g. contracts, apps, invoices, etc. |
| D | Dynamic forms | 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. |
| E | End Approval | The End Approval graphical element is used as an auxiliary for the Approval 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. |
| E | End Event | Performs the termination of the process instance. When it is reached, the process is considered complete. |
| E | Event | 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: Start, Intermediate, and End. |
| E | Event status | 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 Open, Canceled, or Closed, status, which makes it easy to control the schedule. |
| E | Event type app | With this type of app you can create calendars in different workspaces of the system. |
| E | Exclusive Gateway | Activates process operation for only one of the outgoing connectors. It is mandatory to set a default connector for this gateway. |
| F | File | .docx, .xlsx, and .pdf documents, images, audio, and video uploaded to BRIX from the user’s computer or created directly in the system. |
| F | Filter | Saved set of advanced object search parameters. |
| F | Flow chart | 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. |
| F | Folder | Folders are used to store and organize files. You can create and edit new folders and manage access rights to them. |
| F | Form builder | A tool that allows you to design and modify forms to create, edit, and view apps, tasks, and events. |
| F | Form template | 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. |
| G | Gateway | Gateways represent decision points in the process. They are used to direct the process along one branch or another, depending on certain conditions. |
| G | Generate from template | The Generate by template 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. |
| G | Group | An item of an organizational structure that represents a group of users with common job responsibilities. |
| G | Group chat | 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. |
| I | Inclusive OR-gateway | Activates the process of all outgoing connectors for which the transition condition is met. |
| I | Instance summary page | The page that opens when you click on the process name in the Tasks > Assigned by me 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. |
| J | Job position | An item of the organizational structure denoting one employee of a company. Examples of job positions: director, chief accountant, secretary, etc. |
| K | Kanban board | 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. |
| K | Key variable | A variable involved in the automatic generation of the app item name. |
| L | Link | 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. |
| L | Link to a folder | 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. |
| M | Main page | BRIX main page that is displayed immediately after the user logs into the system or when you click on the main menu button. |
| M | Manage Status | The Manage Status 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. |
| M | Mentions | A convenient way to draw your colleagues’ attention to a file, task, or comment in a chat or channel. If you mention a person using the @ symbol, they receive a pop-up notification of your message. |
| M | Multiple execution | A setting that allows you to assign a task simultaneously to all employees designated as executors of the swimlane. |
| N | Notifications | The Notifications 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. |
| O | Organizational Chart | 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). |
| O | Org chart item | Component of the graphical model of the organizational structure (department, job position, and group). |
| P | Page | 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. |
| P | Parallel Gateway | Activates process operation for all outgoing connectors. Required to run a process on multiple routes at the same time. |
| P | Parent task | A task that is decomposed into subtasks, i.e. from which page subtasks are created. |
| P | Personal calendar | 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. |
| P | Process debugging | 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. |
| P | Process designer | A section of the system designed for modeling business processes. |
| P | Process map | A graphical representation of a process that shows the progress of a process instance and the current operations on it. |
| P | Process monitor | An analytical tool for system administrators to monitor the status of processes in real time. |
| P | Process participant | Executor of a swimlane. |
| P | Process publishing | 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. |
| P | Process task | 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. |
| R | Registration | The Registration graphical element helps to organize document accounting and control within the company by assigning a registration number (index) to the document. |
| R | Revenue Forecast | Report on planned cash receipts: amount, status, planned date, etc. |
| R | Role | 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. |
| S | Sales pipeline | The principle of allocating deals to stages of the sales process. |
| S | Schedule compliance | 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. |
| S | Script | TypeScript code that allows you to access business process data, create, request, modify, delete app items and interact with external systems over HTTP. |
| S | Separator | A separator is used to group apps within a workspace. It visually separates apps from each other with a dividing line. |
| S | Start Event | Initiates the start of the process and specifies at what point it begins. A process can contain only one Start Event. |
| S | Start Process | 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. |
| S | Substitution | 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. |
| S | Supervisor | 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. |
| S | Swimlane | Determines the performer of tasks placed in a swimlane. |
| T | Tables | 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. |
| T | Task | 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. |
| T | Task page | 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. |
| T | Task participant | A user that works on the task but is not responsible for its execution. |
| T | Timer intermediate event | 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. |
| T | Token | A token is used to authorize API requests , for example, to retrieve app items or run a business process from an external system. |
| U | User account | User login and password required to log in to the BRIX system and provide access to personal data and settings. |
| U | User group | Groups are used to customize access to files, documents, apps, app items, workspaces, and define executors in swimlanes in business processes. |
| V | Version of a business process | Represents one version of a business process. Versions differ by sequence number, status, date of creation, version creator, and description. |
| W | Webhook | The Webhook graphical element is used to model a process. It allows the automatic transfer of process instance information from BRIX to an external system. |
| W | Widget | 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. |
| W | Workspace | A workspace brings together one or more apps linked by a common theme. For example, apps such as Contract, Order, Memo and Report can be compiled within the Documents workspace. The function of workspaces is primarily organizational. |
| W | Workspace calendar | A calendar created using an Event type app in a specific workspace. |
| W | Workspace export | Unload the workspace with all apps. |
| W | Workspace visibility | 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. |
Was this helpful?