Maestro user guide

Last updated Jun 24, 2025

Data and artifacts

BPMN provides several elements for modeling how data flows through a process and for annotating diagrams. In Maestro, these elements help document inputs, outputs, documents, and contextual information, but most of them are used for modeling clarity only and do not directly influence execution.

This section explains how to use BPMN data objects and artifacts for effective, readable models in Maestro.

Data objects

Data objects represent information that is created, updated, or consumed during the process. They are associated with tasks or events to clarify how data is used.

Use case	Modeling behavior	Execution
Invoice, form, document	Shown as a paper icon near task	Visual only

Use to indicate which documents or data structures are involved.
Use data associations (dotted arrows) to connect data objects to activities

Important: Maestro does not automatically link these to process variables — they are for modeling purposes only.

Data input and output

Used at the process or task level to indicate expected input (into a process or activity) and output (produced result).

Often modeled on start or end events.
Input/output markers may represent external APIs, system data, or human-provided input.

Type	Use case	Execution
Input	Declares what is needed to begin	Visual only
Output	Declares what is produced	Visual only

Important: Execution-time input/output is defined using variable mapping and is not linked to these visual elements.

Data stores

Data stores represent persistent data repositories such as databases or file systems.

Visualized as a cylinder
Use when modeling read/write operations across multiple process instances

Example	Modeling purpose	Execution
`Customer DB`	Document external system interaction	Visual only

Data associations

Data associations are dashed lines with arrowheads, connecting data objects to activities.

Use to clarify which task consumes or produces which data.
Direction indicates input (to task) or output (from task).

Important: These do not replace actual data bindings configured in the process.

Text annotations

Text annotations are used to add descriptive comments to any element in the process.

Use for business notes, assumptions, or rationale.
Placed outside the flow and connected by a dashed line.

Example: Escalation path applies only for Premium tier customers.

Groups

Groups are used to visually organize related elements without affecting the flow.

Represented by a dashed rectangle.
Use to highlight sub-processes, responsibilities, or logical blocks.

Example: Group all Manual Review steps in a single visual block.

Summary

Table 1.
Element	Purpose	Execution in Maestro
Data Object	Documents data used in tasks	Visual only
Data Input/Output	Indicates input/output parameters	Visual only
Data Store	Models external storage	Visual only
Data Association	Shows input/output linkage	Visual only
Text Annotation	Adds comments	Visual only
Group	Visual organization	Visual only