Modeling

Model a process with BPMN

Use explicit events, tasks and routing for repeatable business processes.

Priostack integration guideReviewed 5 Oct 2026

Choose elements by responsibility

Element	Use it for
Start / end event	The entry and completion boundaries of a process.
Service task	Work done by a job worker that activates the task's job type.
User task	A step that requires human input, completed from the task list.
Exclusive gateway	Choosing a conditional path with a defined fallback.
Parallel gateway	Splitting and joining concurrent work.
Boundary event	Responding to an event, such as a timer, while an activity is active.

Keep XML well formed

XML fragment · namespaces belong on the enclosing definitions element

<sequenceFlow id="review" sourceRef="route" targetRef="manual">
  <conditionExpression xsi:type="tFormalExpression">
    = amount &lt; 1000
  </conditionExpression>
</sequenceFlow>

Escape comparison characters inside XML text: the engine rejects a raw < with a 422. Declare every namespace prefix on the enclosing model and give every sequence flow an id. A fragment is not a complete deployable process.

Deploy and test on Priostack

Deploy BPMN with POST /api/v1/process-definitions. Redeploying changed bytes under the same process id creates the next version; running instances keep the version they started on. Importing XML does not prove every modeled behavior is supported, so test routing, variable mapping, timers and error handling before moving a production process.

BPMN elements reference

Machine-readable contracts: MCP tools JSON · OpenAPI JSON. See the contract notes for older examples.

CONTINUE READINGModel a decision with DMN →