BPMN

Available

The visual language behind every Orkovia process, plus variables and data mappings.

BPMN (Business Process Model and Notation) is the visual language used to describe process behavior. A BPMN process answers: what happens, in what order, under which conditions, and who or what performs each step?

Common elements

Element	Purpose
Start Event	Starts a process instance
End Event	Marks the end of a process path
Service Task	Automated work — call an API, run a worker, update a database, publish a message
User Task	Creates work for a person — approval, review, verification, data entry
Exclusive Gateway	Selects one path based on a condition, e.g. amount > 100000 → Manager Approval
Parallel Gateway	Runs multiple branches concurrently
Subprocess	Groups a section of process logic into a reusable / isolated scope
Boundary Event	Responds to an event while an activity is running

Process variables

Process variables carry business data through a workflow. They can be read by service tasks, gateways, forms, workers, connectors, decisions and messages.

{
  "customer": {
    "id": "C1001",
    "name": "John"
  },
  "amount": 5000,
  "approved": false
}

Variables are accessed with FEEL expressions, e.g. customer.name, order.amount, approved. Scope is nested: process scope, optionally a subprocess scope, and task-local scope. Use local variables for temporary or task-specific information, and process-level variables for anything that must be shared across the whole process.

Data mappings

Input and output mappings control how data moves between scopes and activities, keeping service/task implementations independent from the overall process data structure.

Mapping	Flow	Example
Input	Process variable → task-local variable	Source: customer.name → Target: customerName
Output	Task result → process variable	Source: response.customerId → Target: customerId

PreviousFirst deployment Next Forms