- Overview
- Process modeling
- Process implementation
- Process operations
- Process monitoring
- Process optimization
- Reference information

Maestro user guide
Modeling your process
Agentic processes feature a dedicated designer where you can design and configure your long-running enterprise process in an industry-standard BPMN format.
Agentic processes feature interconnected elements (steps) which can be repositioned and deleted. Each element can be configured in the designer or in the Properties panel. Some elements act as events that control process executions, while others act as placeholders for other activities and workflows.
Link elements between that with connectors , in a way that is meaningful to your flow. Then you can add, link, and remove other available elements. Double click on any
element to name it.
Use the marquee tool to select elements in the designer (click and drag) and the hand tool to navigate inside the canvas (Space key, then click and drag).
Every agentic process starts by default with a Start Event element added to the designer. You can add other elements to your project from the left toolbar.
- Gateways
- Tasks
- Events
- Data
- Participants
- Change element - Opens the Change element panel, where you can modify the selected element to a different element.
- Add end event - Appends an End event element to the selected element.
- Add exclusive gateway - Appends an Exclusive gateway element to the selected element.
- Add task - Appends a Task element to the selected element.
- Add intermediate event - Appends an Intermediate event element to the selected element.
- Add text notation - Appends a text annotation to the selected element.
- Delete - Deletes the selected element.
- Connect - Brings up the connector tool, with the selected element as the source step.
- Add text notation - Appends a text annotation to the selected connection.
- Delete - Deletes the selected connection.
The validation panel is a rules engine that validates the agentic process with BPMN rules and best practices. You can access the validation panel from the bottom left of the designer. The panel shows the number of validation issues found in the process. Selecting a warning or error within the panel directs you to the affected element in the designer.
- Warnings: Marked with yellow, they show a validation issue, and offer suggestions.
- Errors: Marked with red, they allow you to test your agentic process, but prevent you from deploying it.
- Zoom in - Focus on a specific part of your process.
- Zoom out - Expand your view of the process.
- Fit to view - Automatically adjusts the size and position of the process.
Inside the mini map, you can also click and drag to pan inside the process, and use the mouse wheel to zoom in and out.
The context menu appears when you right-click the designer or an element in the designer.
- Organize connections - Automatically rearranges all connections in the designer to improve readability.
- Show / hide validation errors - Controls the visibility of validation errors.
- Rename - Renames the element.
- Copy - Copies the element.
- Cut - Removes the element from the designer and stores it in the clipboard.
- Show properties panel - Displays the properties of the element.
- Remove - Deletes the element from the designer.
- Test - Tests the entire agentic process.
- Test step-by-step - Tests each element in the agentic process one at a time.
- Add text annotation: append text annotation to the selected edge with preview.
- Delete: delete the selected edge.
Some elements are execution elements, meaning that they are executable within the context of the business model. They distinctly represent the flow and control of the work or agentic process. Examples of execution elements include tasks, sub-processes, gateways, events, and sequence flows.
The non-execution elements are used for providing extra information about the process and its components but do not have any execution semantics. They are not directly involved in the execution flow of the process. Examples include text and annotation artefacts, group objects, and data objects.
For example, the Receive Task element is executable, meaning that it can be configured to trigger a particular action when a message is received by a mailbox. The Data store element is not executable, it just indicates to the modeler that a particular executable element leverages data from a certain data store.
For a full list of BPMN elements and their definitions, please check the PDF file with the BPMN 2.0 elements descriptions.
For a full list of BPMN elements and their definitions, please check the PDF file with the BPMN 2.0 elements descriptions.
- Official site of BPMN—Object Management Group BPMN BPMN Specification - Business Process Model and Notation
- Business Process Model and Notation (Wikipedia) Business Process Model and Notation.
The canvas is compliant with the BPMN 2.0 standard, and supports the following Start, Intermediate, and End elements:
Type | Normal | Event sub-process | Event subprocess non-interrupting |
---|---|---|---|
None | Yes | No | No |
Message | Yes | Yes | Yes |
Timer | Yes | Yes | Yes |
Error | No | Yes | No |
Signal | No | No | No |
Conditional | No | No | No |
Escalation | No | No | No |
Compensation | No | No | No |
Cancel | No | No | No |
Terminate | No | No | No |
Multiple parallel | No | No | No |
Type | Catch | Boundary | Boundary non-interrupting | Throw |
---|---|---|---|---|
None | No | No | No | Yes |
Message | Yes | Yes | Yes | Yes |
Timer | Yes | Yes | Yes | No |
Error | No | Yes | No | No |
Signal | No | No | No | No |
Conditional | No | No | No | No |
Escalation | No | No | No | No |
Compensation | No | Yes | No | Yes |
Cancel | No | No | No | No |
Terminate | No | No | No | No |
Link | No | No | No | No |
Multiple | No | No | No | No |
Multiple parallel | No | No | No | No |
Type | End |
---|---|
None | Yes |
Message | Yes |
Timer | No |
Error | Yes |
Signal | No |
Conditional | No |
Escalation | No |
Compensation | Yes |
Cancel | No |
Terminate | Yes |
Link | No |
Multiple | No |
Multiple parallel | No |
BPMN construct | Supported in Modeler | Supported in Execution |
---|---|---|
Pool | Yes | No |
Lane | Yes | Yes |
Subprocess | Yes | Yes |
Call Activity | Yes | Yes |
Event Subprocess | Coming
soon | Coming
soon |
Transaction | Yes | No |
Undefined Task | Yes | Yes |
Service Task | Yes | Yes |
User Task | Yes | Yes |
Receive Task | Yes | No |
Send Task | Yes | Yes |
Business Rule Task | Yes | Yes |
Script Task | Yes | Yes |
Manual Task | Yes | Yes |
Exclusive Gateway | Yes | Yes |
Parallel Gateway | Yes | Yes |
Inclusive Gateway | Yes | Yes |
Event Gateway | Yes | Yes |
Complex Gateway | Yes | No |
Multi-instance Parallel | Yes | Yes |
Multi-instance Sequential | Yes | Yes |
Loop | Coming in GA | Coming in GA |
Compensation | Coming in GA | Coming in GA |
Data Object | Yes | No |
Data Store | Yes | No |
Text Annotation | Yes | No |
Group | No | Yes |