Skip to main content

Glossary

Explanation of key terms and concepts

Attributes

Attributes are components that can be added to a document for entering information. Attributes can be various document elements, such as a project name, product price, document signing date, or a hyperlink to a company website. There are three types of attributes:

  • Custom Attributes — attributes created by a user, grouped into folders according to the folder structure in the Attribute Library.
  • Role Attributes — attributes used to define and manage user roles and access rights in the system.

For more information about attributes and working with them, see the Attribute Library and Designer sections.

Business Process

A business process is a set of tasks and elements represented as a diagram. The goal of a process is to achieve a specific business objective or result. For example, a business process may include receiving a customer order, processing the order, delivering the goods, and issuing an invoice. Processes are created based on a business process definition, which serves as a template.


Example: you can create a business process definition "Leave Request Approval". Later, based on this definition, you can create a process for a specific employee — "Leave Request Approval for Ivan Shpak". See the Create a Process Instance Based on a Business Process Definition and Working with Processes sections.

Output Variable

An output variable is a variable of an AI scenario that stores the result of the scenario execution or its individual steps. These variables are used to save the data received (for example, the AI model's response, extracted data, or processing results), which can be used in subsequent scenario steps or saved in the system. The variable type (input or output) is defined during creation using the Is Output Variable toggle. For more details, see Create a Variable.

Example: In the system scenario sys_doc_recognize, the variable result is an output variable. It stores the response received during the execution of the LLM Request step, which contains the document recognition result.

Nested Attributes

Nested attributes are attributes embedded within other attributes contained inside custom directories. You can create a shortcut whose grid displays any attribute of a custom directory, or a child attribute of that attribute, at any level of nesting. This functionality is available only for custom attributes.

Example: you have a Counterparty attribute that references a counterparty directory with fields such as Name, EDRPOU Code, and Address. In this case:

  • Counterparty is the root attribute
  • Name, EDRPOU Code, Address are nested attributes
Input Variable

An input variable is a variable of an AI scenario used to pass data into the scenario when it is launched. These variables contain context or initial data that the scenario uses during step execution (for example, the document text, query parameters, or system reference data). The variable type (input or output) is defined during creation using the Is Output Variable toggle. For more details, see Create a Variable.

Example: In the system scenario sys_doc_recognize, the variable documentTypes is an input variable. It passes information about the document types that exist in the system into the scenario, so the AI model can use this data during document recognition.

Definition (Business Process or Task)

A definition (business process or task) is a formal description of something — in other words, a template. For example, a business process definition is a template based on which business processes are subsequently created.

Example: you can create a business process definition "Leave Request Approval". Later, based on this definition, you can create a process for a specific employee — "Leave Request Approval for Ivan Shpak". See the Create a Business Process Definition and Task Definitions sections.

Additional Packages

Additional packages — the platform allows you to extend its functionality using additional packages. To learn more about the available packages and request installation, contact Nectainium support at info@inbase.com.ua.

Methods

Methods are procedures that perform certain operations on data.

Example: you can call the "setRichText" method of the dfx_Document entity to set a value in a Rich Text-type attribute on a document form. By calling this method, data from the dfx_Document document is automatically passed into the Rich Text attribute on the document form.

Label

A label is the name of an attribute displayed on a document form. By default, the attribute label matches the attribute name in the Attribute Library, unless an administrator changed it during document type configuration. Do not confuse the attribute label with document tags — the latter is a separate mechanism that allows adding keywords to documents for additional classification.

Modeler

The Modeler is an editor in which you can build a business process diagram. See the Create a Business Process Definition and Edit a Business Process Definition sections.

Document Image

Document Image is a visual representation of the document itself, which can be used for convenient viewing. The platform includes a standard Document Image attribute that allows viewing the document as a graphical image — useful for reviewing document content without opening it separately.

Organizational Units

Organizational units can be our organizations, departments, positions, or executor groups. You can create and manage organizational units in the Org. Structure workspace.

Registry

A registry is an ordered list of items of a specific type in the system (for example, documents, folders, messages) that displays key information about those items in a table format. A registry can be opened via the corresponding shortcuts in the platform and used to view, search, and work with the required items.

Examples of registries: Task Registry, Document Registry.

Administration Subject

Administration subjects can be user groups, roles, or users. You can create and manage administration subjects in the Administration workspace.

Entity

An entity is an object that represents a specific business unit or object in your system. An entity can be a task, user, custom directory, or document. Each entity can have various attributes that describe its properties, such as name, creation date, status, and so on.

Tabular Attributes
File Attributes

File attributes are attributes that allow storing document files of various formats (.doc, .docx, .xls, .xlsx, .pdf, .txt, etc.) and viewing their contents using the built-in viewer (for PDF files, Microsoft Office documents, and images). The platform includes the following file attributes:

DMN

DMN (Decision Model and Notation) is one of the three standards for modeling business process aspects used in the Nectainium platform. It allows describing and modeling repeatable decisions. The notation is understandable to both business and IT users. BPMN focuses on processes and workflows, while DMN focuses on decisions and business rules. DMN is most commonly used to create and automate decision-making rules, providing clear and understandable decision logic. See the DMN Notation Overview and Execute DMN sections.