📄️ Overview
An activity is work performed within a business process. When a token arrives at an activity, the process waits until the work is completed; the token then continues along the outgoing sequence flow.
🗃️ Tasks
5 items
📄️ Call activity
A Call Activity invokes another, independently deployed process. It lets several processes reuse the same process logic and keeps large models decomposed into separately deployed and versioned pieces. In ZenBPM the called process runs as its own process instance linked to the parent on the same partition; the parent token waits at the Call Activity until the called instance completes.
📄️ Sub process
A Sub process embeds a complete flow — with its own start and end events — inside a parent process. It groups related steps into a single unit with its own variable scope and error handling boundary. In ZenBPM the embedded flow runs as its own child process instance linked to the parent on the same partition; the parent token waits at the Sub process until the embedded flow completes.
📄️ Event sub process
An Event sub process is a Sub process that is not part of the normal flow: it has no incoming or outgoing sequence flows and is started by its own start event instead. While its containing scope is active, the engine keeps the trigger armed — when the event occurs, the embedded flow runs as a child instance of that scope, either interrupting the scope or running alongside it.
📄️ Multi-instance activity
A multi-instance activity runs one activity once per element of a collection — sequentially or in parallel. It is a marker placed on an activity, not a separate element type, and can be applied to any supported Task, Sub process, or Call activity. In ZenBPM the iterations execute inside a dedicated child process instance linked to the parent; the parent token waits at the activity until all iterations have completed.