maestro
latest
false
- 简介
- 流程建模
- 流程实施
- 流程运营
- 流程监控
- 流程优化
- 许可
- 参考信息
重要 :
新发布内容的本地化可能需要 1-2 周的时间才能完成。

Maestro 用户指南
上次更新日期 2025年10月30日
Markers annotate BPMN tasks and call activities to convey intent, such as repetition or compensation. In Maestro, markers are for modeling clarity, except multi‑instance, which Maestro interprets at runtime.
Use a multi‑instance marker when an activity should run once per item in a collection (list or array).
| 类型 | What it means | Runtime note |
|---|---|---|
| 顺序 | One item at a time, in order. | Preserves order; next item starts after the previous finishes |
| 并行 | Many items at once. | Items run concurrently. Order is not guaranteed. |
Important: The task or call activity annotated with a multi‑instance marker must reference a collection (a variable or an expression that evaluates to a list). If the activity returns a result per item and you need a single combined output, configure Aggregation to combine those results (for example, collect as a list or reduce with an expression).
|
|
|
Marks an activity as eligible for compensation (undo logic) in the diagram. Maestro does not execute compensation automatically at runtime. Implement any undo logic explicitly in your model.
- Use markers to clarify design intent, especially for stakeholders who are not aware of execution constraints.
- Only the multi‑instance marker changes runtime behavior in Maestro; other markers are visualization aids.
- Document the loop logic and any compensation approach elsewhere in the process model.
- Prefer named collections and clear item schemas to improve readability.
Read Multi‑instance implementation for how to configure and run multi‑instance work.
For more details about the BPMN elements supported in Maestro, read BPMN support.