Skip to content

Basic nodes ​

The three nodes you reach for in almost every process: the entry point, the exit point, and the work in between.

Start ​

The start node defines the start of a process. There can be multiple start nodes. It is not mandatory, a process may begin with any node, but explicit start nodes make the intent of the diagram unambiguous.

Alternative terms you might use when describing one: entry, kickoff, beginning.

In BPMN a start event is drawn as a circle with a thin single-line border. It is an event, something that happens at the very beginning of a process, and not work that is performed. Its thin border is what distinguishes it visually from an intermediate event (double border) or an end event (thick border).

Input

pml
START 'text input' NEXT

Input suggestion

pml
START 'Start' NEXT

Icon

Start icon

Tips

  • If you do not explicitly mention a start, assistants such as the in-editor AI will create one for you unless instructed otherwise.
  • A START line always carries NEXT: a bare NEXT connects it to the next node, NEXT <target> to a named one.

End ​

The end node defines the end of a process. There can be multiple end nodes. Use them to close a dead branch and make the end of a flow explicit. An end node cannot have a NEXT.

Alternative terms you might use when describing one: finish, close, stop.

In BPMN an end event is drawn as a circle with a thick solid border. Its thick border distinguishes it from a start event (thin border) or an intermediate event (double border). An end event signals that a path of the process has completed; a process is only fully finished once every active path has reached an end event.

Input

pml
END 'text input'

Input suggestion

pml
END 'End'

Icon

End icon

Tips

  • If a branch ends without an explicit end, assistants such as the in-editor AI will add an END unless instructed otherwise.
  • Because end nodes cannot have a NEXT, they are always terminal in the flow.

Terminate end ​

The terminate end node ends the whole process at once. Every other active path stops when a path reaches it.

In BPMN a terminate end event is drawn as a circle with a thick solid border and a filled circle inside.

Input

pml
END-TERMINATE 'text input'

Input suggestion

pml
END-TERMINATE 'End'

Icon

Terminate end icon

Activity ​

The activity node defines activities executed within a process, something that needs to happen and has a duration. It is the most common node in Instant Process. Use ACTIVITY for general tasks unless you specifically need an event, a gateway, or one of the boundary nodes.

Alternative terms you might use: task, step, action.

In BPMN an activity is drawn as a rounded rectangle. It is the standard notation for a unit of work executed by a participant: the process performs it, rather than simply observing that it happened. When you need to emphasise that something occurs rather than is performed, use an event instead.

Input

pml
ACTIVITY 'text input'

Input suggestion

pml
ACTIVITY 'Task' NEXT

Icon

Activity icon

Tips

  • Use ACTIVITY as the default for any work step. Only reach for EVENT variants when the emphasis is on an occurrence.
  • Activities can carry data by sitting adjacent to attachments.

Task types ​

A task type says what kind of work an activity is. Write the task type keyword where you write ACTIVITY. A task type node is an activity in every other way: it links, sits in a lane and carries markers as ACTIVITY does.

Send task ​

A send task sends a message to another party. The task type icon sits in the top-left corner of the rectangle.

Input

pml
ACTIVITY-SEND 'text input'

Input suggestion

pml
ACTIVITY-SEND 'Send invoice' NEXT

The Dutch keyword is ACTIVITEIT-VERZENDEN.

Icon

Send task icon

Receive task ​

A receive task waits for a message from another party. The task type icon sits in the top-left corner of the rectangle.

Input

pml
ACTIVITY-RECEIVE 'text input'

Input suggestion

pml
ACTIVITY-RECEIVE 'Receive payment' NEXT

The Dutch keyword is ACTIVITEIT-ONTVANGEN.

Icon

Receive task icon

User task ​

A user task is work a person does with the help of software. The task type icon sits in the top-left corner of the rectangle.

Input

pml
ACTIVITY-USER 'text input'

Input suggestion

pml
ACTIVITY-USER 'Review order' NEXT

The Dutch keyword is ACTIVITEIT-GEBRUIKER.

Icon

User task icon

Manual task ​

A manual task is work a person does without software. The task type icon sits in the top-left corner of the rectangle.

Input

pml
ACTIVITY-MANUAL 'text input'

Input suggestion

pml
ACTIVITY-MANUAL 'Pack order' NEXT

The Dutch keyword is ACTIVITEIT-HANDMATIG.

Icon

Manual task icon

Business rule task ​

A business rule task applies a decision rule. The task type icon sits in the top-left corner of the rectangle.

Input

pml
ACTIVITY-BUSINESS-RULE 'text input'

Input suggestion

pml
ACTIVITY-BUSINESS-RULE 'Determine discount' NEXT

The Dutch keyword is ACTIVITEIT-BEDRIJFSREGEL.

Icon

Business rule task icon

Service task ​

A service task is work a system does automatically. The task type icon sits in the top-left corner of the rectangle.

Input

pml
ACTIVITY-SERVICE 'text input'

Input suggestion

pml
ACTIVITY-SERVICE 'Reserve stock' NEXT

The Dutch keyword is ACTIVITEIT-SERVICE.

Icon

Service task icon

Script task ​

A script task runs a script. The task type icon sits in the top-left corner of the rectangle.

Input

pml
ACTIVITY-SCRIPT 'text input'

Input suggestion

pml
ACTIVITY-SCRIPT 'Calculate total' NEXT

The Dutch keyword is ACTIVITEIT-SCRIPT.

Icon

Script task icon

Transaction ​

A transaction is a set of activities that succeed or fail together. It is drawn as an activity with a double border. A transaction in Instant Process is collapsed: it holds no steps of its own.

Input

pml
TRANSACTION 'text input'

Input suggestion

pml
TRANSACTION 'Book trip' NEXT

The Dutch keyword is TRANSACTIE.

Event sub-process ​

An event sub-process starts when its trigger occurs, outside the order of the other steps. It is drawn as an activity with a dotted border. It carries no NEXT, no NEXT points at it, and a bare NEXT on the line before it links past it to the next step. A NEXT at an event sub-process is a finding of the rule An event sub-process has no sequence flow. An event sub-process in Instant Process is collapsed: it holds no steps of its own.

Input

pml
EVENT-SUBPROCESS 'text input'

Input suggestion

pml
START 'Order placed' NEXT
ACTIVITY-SEND 'Ship order' NEXT
END 'Order shipped'
EVENT-SUBPROCESS 'Handle cancellation'

The Dutch keyword is EVENT-SUBPROCES.

Activity markers ​

A marker says how an activity runs. Write markers after the description, and after the PROCESS clause of a subprocess, before the links. A node carries several markers in any order. They are drawn in one row at the bottom centre of the activity, in the order compensation, loop, ad hoc.

  • A marker follows an ACTIVITY, a task type, a TRANSACTION, an EVENT-SUBPROCESS or a SUBPROCESS. A marker on any other node is an error.
  • An activity carries at most one of LOOP, MULTI-PARALLEL and MULTI-SEQUENTIAL.
  • A marker is written once per node.

Loop ​

A loop activity repeats while a condition holds.

Input

pml
ACTIVITY 'Check document' LOOP NEXT

The Dutch keyword is HERHALEN.

Icon

Loop icon

Parallel multi-instance ​

A parallel multi-instance activity runs several times at once, once per item.

Input

pml
ACTIVITY-SERVICE 'Notify supplier' MULTI-PARALLEL NEXT

The Dutch keyword is MEERVOUDIG-PARALLEL.

Icon

Parallel multi-instance icon

Sequential multi-instance ​

A sequential multi-instance activity runs several times one after the other, once per item.

Input

pml
ACTIVITY-USER 'Approve line' MULTI-SEQUENTIAL NEXT

The Dutch keyword is MEERVOUDIG-SEQUENTIEEL.

Icon

Sequential multi-instance icon

Ad hoc ​

An ad hoc event sub-process runs its steps in any order. AD-HOC stands on an EVENT-SUBPROCESS only; on any other node it is a finding of the rule Ad hoc marks an event sub-process.

Input

pml
EVENT-SUBPROCESS 'Gather evidence' AD-HOC

The Dutch keyword is AD-HOC.

Icon

Ad hoc icon

Compensation ​

A compensation activity undoes the work of another activity.

Input

pml
ACTIVITY 'Refund payment' COMPENSATION NEXT

The Dutch keyword is COMPENSATIE.

Icon

Compensation icon

Identifiers ​

A node is referenced by its description. When that is not enough, see Explicit identifiers.