Appearance
BPMN modelling rules
These rules are InstantProcess's reading of BPMN 2.0: what a process written in Instant Process code follows to be a sound BPMN model that a BPMN tool accepts and a reader understands. The standard itself is the OMG BPMN 2.0 specification. Each rule has a stable id. A checked rule is checked each time an AI agent compiles or saves a process, and a break of it is a finding with that id. A guidance rule is a convention that nothing checks. A finding never blocks a save.
Rules
| Id | Rule | Severity | Checked |
|---|---|---|---|
bpmn-message-flow-between-pools | A message flow connects two pools | violation | yes |
bpmn-message-flow-source | A message flow leaves a node that sends | violation | yes |
bpmn-message-flow-target | A message flow arrives at a node that receives | violation | yes |
bpmn-sequence-flow-within-pool | A sequence flow stays inside its pool | warning | compiler |
bpmn-message-flow-label | A message flow names its message | suggestion | yes |
bpmn-start-event-no-incoming | A start event has no incoming sequence flow | violation | yes |
bpmn-event-type-placement | An event type stands where BPMN allows it | violation | yes |
bpmn-event-gateway-targets | An event-based gateway leads to catching events | violation | yes |
bpmn-event-subprocess-no-sequence-flow | An event sub-process has no sequence flow | violation | yes |
bpmn-ad-hoc-placement | Ad hoc marks an event sub-process | violation | yes |
bpmn-exclusive-split-parallel-join | An exclusive split never meets a parallel join | violation | yes |
bpmn-gateway-pairing | A split and its join are of the same kind | warning | yes |
bpmn-gateway-branch-labels | Every branch of a decision is labelled | warning | yes |
bpmn-gateway-split-or-join | A gateway splits or joins, not both | warning | yes |
bpmn-split-with-gateway | Parallel work splits at a gateway | warning | yes |
bpmn-start-event-required | Every pool with steps has a start event | warning | yes |
bpmn-end-event-required | Every pool with steps has an end event | warning | yes |
bpmn-path-reaches-end | Every path reaches an end event | warning | yes |
no-unreachable-node | Every step is reached | warning | yes |
no-dead-end | Every step leads somewhere | warning | yes |
no-single-branch-gateway | A gateway decides between branches | warning | yes |
no-self-referencing-subprocess | A subprocess references another process | violation | yes |
no-empty-lane | Every lane holds a step | suggestion | yes |
no-unnecessary-explicit-id | An explicit id only where it is needed | suggestion | yes |
bpmn-activity-naming | An activity is named verb plus object | guidance | no |
bpmn-event-naming | An event is named as a state | guidance | no |
bpmn-gateway-naming | A decision is named as a question | guidance | no |
bpmn-merge-with-gateway | Alternative paths merge at a gateway | guidance | no |
bpmn-pools-are-participants | Pools are parties, lanes are roles | guidance | no |
Severities
| Severity | Meaning |
|---|---|
violation | The process breaks a BPMN 2.0 rule. A BPMN tool rejects or flags the exported model. |
warning | The process is valid BPMN 2.0 and is ambiguous, incomplete or against a modelling convention. |
suggestion | The process is sound. The change makes it easier to read. |
guidance | A convention on this page. Nothing checks it and it never produces a finding. |
A finding carries ruleId, severity, nodeId, message and ruleUrl. nodeId is always present: the node identifier, the pool identifier for a finding on a pool, the lane name for no-empty-lane, and null for a finding on the whole of a process without POOL.
Message flows
A message flow connects two pools
A message flow carries information between two parties, and every party is a pool. Inside one pool, the link between two steps is a sequence flow.
In process code. NEXT-MESSAGE links nodes of two different POOLs, or a node and another pool. A process without POOL is one pool, and every NEXT-MESSAGE in it is a finding, between lanes or not. Within one pool the link is NEXT.
Severity. violation, checked.
Correct
pml
POOL Customer
START 'Need product' NEXT
ACTIVITY 'Place order' NEXT-MESSAGE 'Order received' 'Order form' NEXT
END 'Order placed'
POOL Shop
EVENT-MESSAGE 'Order received' NEXT
ACTIVITY 'Process order' NEXT
END 'Order processed'Incorrect
pml
LANE Customer
START 'Need product' NEXT
ACTIVITY 'Place order' NEXT-MESSAGE 'Process order' 'Order form' NEXT
END 'Order placed'
LANE Shop
ACTIVITY 'Process order' NEXT
END 'Order processed'A message flow leaves a node that sends
A message is sent by work or by a party, never by a decision or by the start or end of a flow.
In process code. A NEXT-MESSAGE leaves an ACTIVITY, a SUBPROCESS, a POOL, or an EVENT-MESSAGE that sends: an intermediate message event without an incoming message flow, or a message event that ends a flow. It never leaves a gateway, START, EVENT, another EVENT-* type, a message event that receives, or a DATA, DATABASE or TEXT. NEXT-MESSAGE on an END or END-TERMINATE line is a compile error.
Severity. violation, checked.
Correct
pml
POOL Shop
START 'Order received' NEXT
GATEWAY 'In stock?' NEXT 'Ship order' 'Yes' AND 'Notify customer' 'No'
ACTIVITY 'Ship order' NEXT 'Order handled'
ACTIVITY 'Notify customer' NEXT 'Order handled' NEXT-MESSAGE Customer 'Out of stock'
GATEWAY-EXCLUSIVE 'Order handled' NEXT
END 'Order done'
POOL CustomerIncorrect
pml
POOL Shop
START 'Order received' NEXT
GATEWAY 'In stock?' NEXT 'Ship order' 'Yes' AND 'Close order' 'No' NEXT-MESSAGE Customer 'Out of stock'
ACTIVITY 'Ship order' NEXT 'Order handled'
ACTIVITY 'Close order' NEXT 'Order handled'
GATEWAY-EXCLUSIVE 'Order handled' NEXT
END 'Order done'
POOL CustomerA message flow arrives at a node that receives
A message is received by work, by a party, or by an event that waits for it.
In process code. A NEXT-MESSAGE reaches an ACTIVITY, a SUBPROCESS, a POOL, or an EVENT-MESSAGE that receives: a message event that starts a flow, or an intermediate message event, also one that sends a message flow of its own. It never reaches a gateway, START, END, END-TERMINATE, EVENT, another EVENT-* type, a message event that ends a flow, or a DATA, DATABASE or TEXT.
Severity. violation, checked.
Correct
pml
POOL Customer
START 'Need product' NEXT
ACTIVITY 'Place order' NEXT-MESSAGE 'Order received' 'Order form' NEXT
END 'Order placed'
POOL Shop
EVENT-MESSAGE 'Order received' NEXT
ACTIVITY 'Process order' NEXT
END 'Order processed'Incorrect
pml
POOL Customer
START 'Need product' NEXT
ACTIVITY 'Place order' NEXT-MESSAGE 'Order processed' 'Order form' NEXT
END 'Order placed'
POOL Shop
START 'Shift starts' NEXT
ACTIVITY 'Process order' NEXT
END 'Order processed'A sequence flow stays inside its pool
A sequence flow orders the work of one party. Work of two parties is linked by a message flow.
In process code. A NEXT between nodes of two POOLs, or from a node to another pool, is a sequence flow across pools. Write the link as NEXT-MESSAGE. The other checks read such a NEXT as neither a sequence flow nor a message flow, and leave it out of the placement of an event.
Severity. warning, checked by the compiler: the SequenceFlowAcrossPools compile warning, reported in the diagnostics and not as a finding.
Correct
pml
POOL Customer
START 'Need product' NEXT
ACTIVITY 'Place order' NEXT-MESSAGE 'Order received' 'Order form' NEXT
END 'Order placed'
POOL Shop
EVENT-MESSAGE 'Order received' NEXT
ACTIVITY 'Process order' NEXT
END 'Order processed'Incorrect
pml
POOL Customer
START 'Need product' NEXT
ACTIVITY 'Place order' NEXT 'Order placed' AND 'Order received' 'Order form'
END 'Order placed'
POOL Shop
EVENT-MESSAGE 'Order received' NEXT
ACTIVITY 'Process order' NEXT
END 'Order processed'A message flow names its message
The label of a message flow is the information it carries: an order form, an invoice, a confirmation.
In process code. Every NEXT-MESSAGE target carries a label: NEXT-MESSAGE 'Order received' 'Order form'.
Severity. suggestion, checked.
Correct
pml
POOL Customer
START 'Need product' NEXT
ACTIVITY 'Place order' NEXT-MESSAGE 'Order received' 'Order form' NEXT
END 'Order placed'
POOL Shop
EVENT-MESSAGE 'Order received' NEXT
ACTIVITY 'Process order' NEXT
END 'Order processed'Incorrect
pml
POOL Customer
START 'Need product' NEXT
ACTIVITY 'Place order' NEXT-MESSAGE 'Order received' NEXT
END 'Order placed'
POOL Shop
EVENT-MESSAGE 'Order received' NEXT
ACTIVITY 'Process order' NEXT
END 'Order processed'Events
A start event has no incoming sequence flow
A start event is where a flow begins. A flow that returns to an earlier point returns to a step after the start.
In process code. No NEXT points at a START. A loop back to the beginning points at a GATEWAY-EXCLUSIVE after the START that merges the loop.
Severity. violation, checked.
Correct
pml
START 'Request received' NEXT
GATEWAY-EXCLUSIVE 'Request in' NEXT
ACTIVITY 'Check request' NEXT
GATEWAY 'Complete?' NEXT 'Handle request' 'Yes' AND 'Ask for details' 'No'
ACTIVITY 'Ask for details' NEXT 'Request in'
ACTIVITY 'Handle request' NEXT
END 'Request handled'Incorrect
pml
START 'Request received' NEXT
ACTIVITY 'Check request' NEXT
GATEWAY 'Complete?' NEXT 'Handle request' 'Yes' AND 'Request received' 'No'
ACTIVITY 'Handle request' NEXT
END 'Request handled'An event type stands where BPMN allows it
An event without incoming sequence flow is a start event, an event without outgoing sequence flow an end event, and an event with both an intermediate event. Not every event type exists at every placement.
In process code. The EVENT-* keywords at their placement:
| Keyword | Start | Intermediate | End |
|---|---|---|---|
EVENT, EVENT-MESSAGE, EVENT-SIGNAL | allowed | allowed | allowed |
EVENT-TIMER, EVENT-CONDITIONAL | allowed | allowed | finding |
EVENT-LINK | allowed | finding | allowed |
EVENT-ESCALATION, EVENT-COMPENSATION | finding | allowed | allowed |
EVENT-ERROR | finding | finding | allowed |
EVENT-CANCEL | finding | finding | finding |
EVENT-TIMERandEVENT-CONDITIONALonly catch, and an end event only throws.EVENT-LINKis a pair: a throwing link without outgoing flow and a catching link without incoming flow.- An escalation and a compensation start event stand only inside an event sub-process. An
EVENT-SUBPROCESSin Instant Process is collapsed and holds no steps. - An error start event stands only inside an event sub-process, and an intermediate error event only on the boundary of an activity. Instant Process has no boundary event.
- BPMN has no cancel start event. An intermediate cancel event stands only on the boundary of a transaction, and a cancel end event only inside a transaction. A
TRANSACTIONin Instant Process is collapsed and holds no steps.
Severity. violation, checked.
Correct
pml
START 'Order received' NEXT
ACTIVITY 'Charge card' NEXT
GATEWAY 'Paid?' NEXT 'Ship order' 'Yes' AND 'Payment failed' 'No'
ACTIVITY 'Ship order' NEXT
END 'Order shipped'
EVENT-ERROR 'Payment failed'Incorrect
pml
START 'Order received' NEXT
ACTIVITY 'Charge card' NEXT
EVENT-ERROR 'Payment failed' NEXT
ACTIVITY 'Notify customer' NEXT
END 'Customer notified'An event-based gateway leads to catching events
An event-based gateway waits for the first of several events. Each branch starts with the event it waits for.
In process code. Every NEXT and AND target of a GATEWAY-EVENT is an intermediate EVENT-MESSAGE, EVENT-TIMER, EVENT-SIGNAL or EVENT-CONDITIONAL that receives.
Severity. violation, checked.
Correct
pml
START 'Quote sent' NEXT
GATEWAY-EVENT 'First response' NEXT 'Answer received' AND 'One week passed'
EVENT-MESSAGE 'Answer received' NEXT 'Process answer'
ACTIVITY 'Process answer' NEXT 'Response handled'
EVENT-TIMER 'One week passed' NEXT 'Response handled'
GATEWAY-EXCLUSIVE 'Response handled' NEXT
END 'Quote closed'Incorrect
pml
START 'Quote sent' NEXT
GATEWAY-EVENT 'First response' NEXT 'Process answer' AND 'One week passed'
ACTIVITY 'Process answer' NEXT 'Response handled'
EVENT-TIMER 'One week passed' NEXT 'Response handled'
GATEWAY-EXCLUSIVE 'Response handled' NEXT
END 'Quote closed'Activities
An event sub-process has no sequence flow
An event sub-process starts when its trigger occurs, outside the order of the steps around it. No sequence flow enters or leaves it.
In process code. An EVENT-SUBPROCESS carries no NEXT, and no NEXT or AND points at it. It may carry NEXT-MESSAGE and NEXT-ASSOCIATION.
Severity. violation, checked.
Correct
pml
START 'Order placed' NEXT
ACTIVITY-USER 'Review order' NEXT
ACTIVITY-SEND 'Ship order' NEXT
END 'Order shipped'
EVENT-SUBPROCESS 'Handle cancellation'Incorrect
pml
START 'Order placed' NEXT
ACTIVITY-USER 'Review order' NEXT
EVENT-SUBPROCESS 'Handle cancellation' NEXT
ACTIVITY-SEND 'Ship order' NEXT
END 'Order shipped'Ad hoc marks an event sub-process
The ad hoc marker says that the steps inside a sub-process run in any order. A task has no steps inside, a call activity runs another process as that process is, and a transaction follows its own protocol.
In process code. AD-HOC follows the description of an EVENT-SUBPROCESS only.
Severity. violation, checked.
Correct
pml
START 'Claim received' NEXT
ACTIVITY-USER 'Assess claim' NEXT
END 'Claim assessed'
EVENT-SUBPROCESS 'Gather extra evidence' AD-HOCIncorrect
pml
START 'Claim received' NEXT
ACTIVITY-USER 'Assess claim' AD-HOC NEXT
END 'Claim assessed'Gateways
A split is a gateway with two or more outgoing sequence flows. Its join is the first node every path from the split passes through on its way to the end. A pairing rule applies when that join is a gateway with two or more incoming sequence flows. A split whose branches end separately, or meet at a step that is not a gateway, has no join to pair with, and a GATEWAY-COMPLEX is never paired. A split is a loop decision when one of its branches leads back to the split before it reaches the join, and a loop decision pairs with no join. A split inside a loop whose branches meet again before the loop returns is no loop decision and pairs with its join.
An exclusive split never meets a parallel join
An exclusive or event-based split takes one branch. A parallel join waits for every branch, and it waits forever for the branches that were not taken.
In process code. The branches of a GATEWAY, GATEWAY-EXCLUSIVE or GATEWAY-EVENT never meet at a GATEWAY-PARALLEL. They meet at a GATEWAY-EXCLUSIVE.
Severity. violation, checked.
Correct
pml
START 'Order received' NEXT
GATEWAY 'Approved?' NEXT 'Ship order' 'Yes' AND 'Reject order' 'No'
ACTIVITY 'Ship order' NEXT 'Order decided'
ACTIVITY 'Reject order' NEXT 'Order decided'
GATEWAY-EXCLUSIVE 'Order decided' NEXT
END 'Order closed'Incorrect
pml
START 'Order received' NEXT
GATEWAY 'Approved?' NEXT 'Ship order' 'Yes' AND 'Reject order' 'No'
ACTIVITY 'Ship order' NEXT 'Order decided'
ACTIVITY 'Reject order' NEXT 'Order decided'
GATEWAY-PARALLEL 'Order decided' NEXT
END 'Order closed'A split and its join are of the same kind
A join mirrors its split: what the split starts, the join brings together.
In process code. A GATEWAY, GATEWAY-EXCLUSIVE or GATEWAY-EVENT split joins at a GATEWAY or GATEWAY-EXCLUSIVE, a GATEWAY-PARALLEL split at a GATEWAY-PARALLEL, and a GATEWAY-INCLUSIVE split at a GATEWAY-INCLUSIVE.
Severity. warning, checked.
Correct
pml
START 'Order received' NEXT
GATEWAY-PARALLEL 'Start fulfilment' NEXT 'Pack goods' AND 'Send invoice'
ACTIVITY 'Pack goods' NEXT 'Order ready'
ACTIVITY 'Send invoice' NEXT 'Order ready'
GATEWAY-PARALLEL 'Order ready' NEXT
ACTIVITY 'Ship order' NEXT
END 'Order shipped'Incorrect
pml
START 'Order received' NEXT
GATEWAY-PARALLEL 'Start fulfilment' NEXT 'Pack goods' AND 'Send invoice'
ACTIVITY 'Pack goods' NEXT 'Order ready'
ACTIVITY 'Send invoice' NEXT 'Order ready'
GATEWAY-EXCLUSIVE 'Order ready' NEXT
ACTIVITY 'Ship order' NEXT
END 'Order shipped'Every branch of a decision is labelled
The label on a branch is the answer that leads there.
In process code. Every NEXT and AND target of a GATEWAY, GATEWAY-EXCLUSIVE or GATEWAY-INCLUSIVE with two or more branches carries a label. A GATEWAY-PARALLEL takes every branch and carries no labels.
Severity. warning, checked.
Correct
pml
START 'Order received' NEXT
GATEWAY 'Approved?' NEXT 'Ship order' 'Yes' AND 'Reject order' 'No'
ACTIVITY 'Ship order' NEXT 'Order decided'
ACTIVITY 'Reject order' NEXT 'Order decided'
GATEWAY-EXCLUSIVE 'Order decided' NEXT
END 'Order closed'Incorrect
pml
START 'Order received' NEXT
GATEWAY 'Approved?' NEXT 'Ship order' AND 'Reject order'
ACTIVITY 'Ship order' NEXT 'Order decided'
ACTIVITY 'Reject order' NEXT 'Order decided'
GATEWAY-EXCLUSIVE 'Order decided' NEXT
END 'Order closed'A gateway splits or joins, not both
One gateway merges incoming paths, a second one splits them again.
In process code. A gateway that two or more links reach carries one outgoing link, and a gateway with two or more outgoing links is reached by one link.
Severity. warning, checked.
Correct
pml
START 'Request received' NEXT
GATEWAY-EXCLUSIVE 'Request in' NEXT
ACTIVITY 'Check request' NEXT
GATEWAY 'Complete?' NEXT 'Handle request' 'Yes' AND 'Ask for details' 'No'
ACTIVITY 'Ask for details' NEXT 'Request in'
ACTIVITY 'Handle request' NEXT
END 'Request handled'Incorrect
pml
START 'Request received' NEXT
GATEWAY 'Complete?' NEXT 'Handle request' 'Yes' AND 'Ask for details' 'No'
ACTIVITY 'Ask for details' NEXT 'Complete?'
ACTIVITY 'Handle request' NEXT
END 'Request handled'Parallel work splits at a gateway
A step with two outgoing sequence flows starts both branches at once.
In process code. A node other than a gateway carries one NEXT target. A decision is a GATEWAY after the step, parallel work a GATEWAY-PARALLEL. A NEXT-MESSAGE or NEXT-ASSOCIATION next to the NEXT is no second branch.
Severity. warning, checked.
Correct
pml
START 'Order received' NEXT
GATEWAY-PARALLEL 'Start fulfilment' NEXT 'Pack goods' AND 'Send invoice'
ACTIVITY 'Pack goods' NEXT 'Order ready'
ACTIVITY 'Send invoice' NEXT 'Order ready'
GATEWAY-PARALLEL 'Order ready' NEXT
ACTIVITY 'Ship order' NEXT
END 'Order shipped'Incorrect
pml
START 'Order received' NEXT
ACTIVITY 'Check order' NEXT 'Pack goods' AND 'Send invoice'
ACTIVITY 'Pack goods' NEXT 'Order ready'
ACTIVITY 'Send invoice' NEXT 'Order ready'
GATEWAY-PARALLEL 'Order ready' NEXT
END 'Order shipped'Start, end and paths
Every pool with steps has a start event
The work of each party begins at a start event.
In process code. Every POOL with steps, and a process without POOL, holds a START or an event without incoming sequence flow, such as an EVENT-MESSAGE that receives the message that starts the work. A pool without steps needs none.
Severity. warning, checked.
Correct
pml
POOL Customer
START 'Need product' NEXT
ACTIVITY 'Place order' NEXT-MESSAGE 'Order received' 'Order form' NEXT
END 'Order placed'
POOL Shop
EVENT-MESSAGE 'Order received' NEXT
ACTIVITY 'Process order' NEXT
END 'Order processed'Incorrect
pml
POOL Customer
START 'Need product' NEXT
ACTIVITY 'Place order' NEXT-MESSAGE 'Process order' 'Order form' NEXT
END 'Order placed'
POOL Shop
ACTIVITY 'Process order' NEXT
END 'Order processed'Every pool with steps has an end event
The work of each party finishes at an end event.
In process code. Every POOL with steps, and a process without POOL, holds an END, an END-TERMINATE or an event without outgoing sequence flow. A pool without steps needs none.
Severity. warning, checked.
Correct
pml
START 'Shift starts' NEXT
GATEWAY-EXCLUSIVE 'Next call' NEXT
ACTIVITY 'Take call' NEXT
ACTIVITY 'Log call' NEXT
GATEWAY 'Shift over?' NEXT 'Shift ended' 'Yes' AND 'Next call' 'No'
END 'Shift ended'Incorrect
pml
START 'Shift starts' NEXT
ACTIVITY 'Take call' NEXT
ACTIVITY 'Log call' NEXT 'Take call'Every path reaches an end event
A loop has a way out to an end event.
In process code. From every node on a loop of NEXT links, the NEXT links lead to an end event of the same pool. A message flow to another pool does not finish the flow of the sender. A node outside a loop is never a finding of this rule: a step that leads to a dead end, and the dead end itself, are left to Every step leads somewhere.
Severity. warning, checked.
Correct
pml
START 'Shift starts' NEXT
GATEWAY-EXCLUSIVE 'Next call' NEXT
ACTIVITY 'Take call' NEXT
ACTIVITY 'Log call' NEXT
GATEWAY 'Shift over?' NEXT 'Shift ended' 'Yes' AND 'Next call' 'No'
END 'Shift ended'Incorrect
pml
START 'Request received' NEXT
GATEWAY 'Urgent?' NEXT 'Handle now' 'Yes' AND 'Queue request' 'No'
ACTIVITY 'Handle now' NEXT
END 'Request handled'
ACTIVITY 'Queue request' NEXT
ACTIVITY 'Check queue' NEXT 'Queue request'Every step is reached
A step nothing leads to never happens.
In process code. Every node other than a START, an event that starts a flow, a DATA, a DATABASE and a TEXT is the target of a link.
Severity. warning, checked.
Correct
pml
START 'Order received' NEXT
ACTIVITY 'Pack goods' NEXT
END 'Order shipped'Incorrect
pml
START 'Order received' NEXT 'Order shipped'
ACTIVITY 'Pack goods' NEXT 'Order shipped'
END 'Order shipped'Every step leads somewhere
A flow goes on from every step until it reaches an end event.
In process code. Every node other than an END, an END-TERMINATE, an event that ends a flow, a DATA, a DATABASE and a TEXT carries a NEXT link to a step of its own pool. A NEXT-MESSAGE, a NEXT-ASSOCIATION, and a NEXT to a DATA, a DATABASE, a TEXT or a node of another pool do not count: a step with only such links is a dead end.
Severity. warning, checked.
Correct
pml
START 'Order received' NEXT
ACTIVITY 'Pack goods' NEXT
END 'Order shipped'Incorrect
pml
START 'Order received' NEXT
GATEWAY-PARALLEL 'Start fulfilment' NEXT 'Pack goods' AND 'Send invoice'
ACTIVITY 'Pack goods' NEXT
END 'Order shipped'
ACTIVITY 'Send invoice'A gateway decides between branches
A gateway with one way out decides nothing.
In process code. A gateway reached by one link carries two or more targets.
Severity. warning, checked.
Correct
pml
START 'Order received' NEXT
GATEWAY 'In stock?' NEXT 'Ship order' 'Yes' AND 'Order from supplier' 'No'
ACTIVITY 'Ship order' NEXT 'Order handled'
ACTIVITY 'Order from supplier' NEXT 'Order handled'
GATEWAY-EXCLUSIVE 'Order handled' NEXT
END 'Order done'Incorrect
pml
START 'Order received' NEXT
GATEWAY 'In stock?' NEXT 'Ship order'
ACTIVITY 'Ship order' NEXT
END 'Order shipped'A subprocess references another process
A process that calls itself as a subprocess never finishes expanding.
In process code. The PROCESS id of a SUBPROCESS is the id of another process. In the examples, 00000000-0000-0000-0000-000000000001 stands for the id of the process itself.
Severity. violation, checked.
Correct
pml
START 'Claim received' NEXT
SUBPROCESS 'Assess claim' PROCESS '00000000-0000-0000-0000-000000000002' NEXT
END 'Claim handled'Incorrect
pml
START 'Claim received' NEXT
SUBPROCESS 'Assess claim' PROCESS '00000000-0000-0000-0000-000000000001' NEXT
END 'Claim handled'Every lane holds a step
An empty lane is a role without work.
In process code. Every LANE holds at least one step. A link to another pool is no step of the lane, and a lane that holds only such links is empty. A POOL without steps is a party whose own steps are unknown and is no empty lane. The finding's nodeId is the lane name.
Severity. suggestion, checked.
Correct
pml
LANE Sales
START 'Order received' NEXT
LANE Archive
ACTIVITY 'Archive order' NEXT
END 'Order archived'Incorrect
pml
LANE Sales
START 'Order received' NEXT
END 'Order recorded'
LANE ArchiveAn explicit id only where it is needed
A node's description is its identifier. An explicit id is for two nodes that would otherwise share one.
In process code. A node with a unique description carries no explicit identifier and is referenced by its description.
Severity. suggestion, checked.
Correct
pml
START 'Order received' NEXT
ACTIVITY 'Pack goods' NEXT
END 'Order shipped'Incorrect
pml
START 'Order received' NEXT
ACTIVITY pack 'Pack goods' NEXT
END 'Order shipped'Naming and structure
An activity is named verb plus object
An activity is work, and its name says what is done to what.
In process code. An ACTIVITY description is a verb and an object: 'Send invoice', never 'Invoice'.
Severity. guidance.
Correct
pml
START 'Order received' NEXT
ACTIVITY 'Send invoice' NEXT
END 'Order invoiced'Incorrect
pml
START 'Order received' NEXT
ACTIVITY 'Invoice' NEXT
END 'Order invoiced'An event is named as a state
An event is something that has happened, and its name says so.
In process code. A START, END and EVENT-* description is an object and a past participle: 'Payment received', never 'Receive payment'.
Severity. guidance.
Correct
pml
START 'Order received' NEXT
ACTIVITY 'Send invoice' NEXT
EVENT-MESSAGE 'Payment received' NEXT
ACTIVITY 'Ship order' NEXT
END 'Order shipped'Incorrect
pml
START 'Order received' NEXT
ACTIVITY 'Send invoice' NEXT
EVENT-MESSAGE 'Receive payment' NEXT
ACTIVITY 'Ship order' NEXT
END 'Order shipped'A decision is named as a question
A decision asks a question, and its branches carry the answers.
In process code. A GATEWAY, GATEWAY-EXCLUSIVE or GATEWAY-INCLUSIVE split is described as a question: 'Order complete?', never 'Check'.
Severity. guidance.
Correct
pml
START 'Order received' NEXT
GATEWAY 'Order complete?' NEXT 'Ship order' 'Yes' AND 'Ask for details' 'No'
ACTIVITY 'Ship order' NEXT 'Order handled'
ACTIVITY 'Ask for details' NEXT 'Order handled'
GATEWAY-EXCLUSIVE 'Order handled' NEXT
END 'Order closed'Incorrect
pml
START 'Order received' NEXT
GATEWAY 'Check' NEXT 'Ship order' 'Yes' AND 'Ask for details' 'No'
ACTIVITY 'Ship order' NEXT 'Order handled'
ACTIVITY 'Ask for details' NEXT 'Order handled'
GATEWAY-EXCLUSIVE 'Order handled' NEXT
END 'Order closed'Alternative paths merge at a gateway
Two alternative paths that continue as one meet at a merging gateway.
In process code. The branches of a decision link to a GATEWAY-EXCLUSIVE that carries one NEXT, not straight to the step after it.
Severity. guidance.
Correct
pml
START 'Order received' NEXT
GATEWAY 'Approved?' NEXT 'Ship order' 'Yes' AND 'Reject order' 'No'
ACTIVITY 'Ship order' NEXT 'Order decided'
ACTIVITY 'Reject order' NEXT 'Order decided'
GATEWAY-EXCLUSIVE 'Order decided' NEXT
ACTIVITY 'Close order' NEXT
END 'Order closed'Incorrect
pml
START 'Order received' NEXT
GATEWAY 'Approved?' NEXT 'Ship order' 'Yes' AND 'Reject order' 'No'
ACTIVITY 'Ship order' NEXT 'Close order'
ACTIVITY 'Reject order' NEXT 'Close order'
ACTIVITY 'Close order' NEXT
END 'Order closed'Pools are parties, lanes are roles
A pool is an independent party: a customer, a supplier, a carrier. A lane is a role or a department inside one party.
In process code. Departments of one organisation are LANEs of one process, never POOLs. POOL is for separate parties that exchange messages.
Severity. guidance.
Correct
pml
LANE Sales
START 'Order received' NEXT
ACTIVITY 'Confirm order' NEXT
LANE Warehouse
ACTIVITY 'Pick goods' NEXT
END 'Goods picked'Incorrect
pml
POOL Sales
START 'Order received' NEXT
ACTIVITY 'Confirm order' NEXT-MESSAGE 'Pick list received' 'Pick list' NEXT
END 'Order confirmed'
POOL Warehouse
EVENT-MESSAGE 'Pick list received' NEXT
ACTIVITY 'Pick goods' NEXT
END 'Goods picked'Process code and BPMN
The checks read the compiled process. A sequence flow is a NEXT link between two steps of one pool. A NEXT between two pools is neither a sequence flow nor a message flow for the checks, it does not count towards the placement of an event, and only the SequenceFlowAcrossPools compile warning reports it. A message flow is a NEXT-MESSAGE link. A NEXT-MESSAGE with a DATA, DATABASE or TEXT end is a finding of the source or the target rule, and the other message flow rules leave it out. A flow node is a START, END, END-TERMINATE, ACTIVITY, task type, TRANSACTION, event, gateway or SUBPROCESS. An EVENT-SUBPROCESS is no flow node. The pool of a node is the POOL it stands in; a process without POOL is one pool.
| Process code | BPMN element |
|---|---|
START | none start event |
END, END-TERMINATE | none end event, terminate end event |
ACTIVITY | task |
ACTIVITY-SEND, ACTIVITY-RECEIVE, ACTIVITY-USER, ACTIVITY-MANUAL, ACTIVITY-BUSINESS-RULE, ACTIVITY-SERVICE, ACTIVITY-SCRIPT | send, receive, user, manual, business rule, service and script task |
TRANSACTION | collapsed transaction |
EVENT-SUBPROCESS | collapsed event sub-process; with AD-HOC, a collapsed ad hoc event sub-process |
SUBPROCESS | call activity |
LOOP | standard loop characteristics |
MULTI-PARALLEL, MULTI-SEQUENTIAL | parallel and sequential multi-instance characteristics |
COMPENSATION | an activity for compensation |
EVENT | none event at its placement |
EVENT-MESSAGE | message event: start catch, intermediate catch or throw, end throw |
EVENT-TIMER, EVENT-CONDITIONAL, EVENT-SIGNAL, EVENT-LINK, EVENT-ESCALATION, EVENT-ERROR, EVENT-CANCEL, EVENT-COMPENSATION | the event of that type at its placement |
GATEWAY, GATEWAY-EXCLUSIVE | exclusive gateway |
GATEWAY-PARALLEL, GATEWAY-INCLUSIVE, GATEWAY-COMPLEX, GATEWAY-EVENT | parallel, inclusive, complex and event-based gateway |
DATA, DATABASE, TEXT | data object, data store, text annotation |
POOL | participant |
LANE | lane |
NEXT | sequence flow, or a data or text association from a DATA, DATABASE or TEXT |
NEXT-MESSAGE | message flow |
NEXT-ASSOCIATION | association |