Skip to content

Explicit identifiers ​

Every node has an identifier. NEXT uses it to point at the node. By default the identifier is the node's description, so most processes never need an explicit identifier.

An explicit identifier is a short name you give a node yourself.

Syntax ​

The explicit identifier is one token between the keyword and the description:

pml
ACTIVITY Review 'Review application'

References use the token, without quotes:

pml
ACTIVITY 'Submit' NEXT Review

Rules:

  • One token: letters, digits, _ and -, starting with a letter or _. No spaces, no quotes.
  • It replaces the description as the identifier. After that, 'Review application' no longer points at the node.
  • It is unique in the process. It cannot match another node's description or identifier.

When you need one ​

  • Two nodes have the same description.
  • A process has more than one START.
  • A link needs a label. A label sits after the target and needs an explicit identifier on that target.
  • A description is long, and you want short references.
pml
START Customer 'Start' NEXT
START Supplier 'Start' NEXT
pml
ACTIVITY 'Check order' NEXT Approve 'Approved'
ACTIVITY Approve 'Approve the order after the manager has checked every line' NEXT

Mixing both styles ​

A process can use descriptions and explicit identifiers together. A reference uses whichever the target has:

pml
ACTIVITY Task_A 'Task' NEXT OtherNode AND 'Node 2'

Duplicates ​

Descriptions and explicit identifiers share one namespace. Two nodes that resolve to the same identifier produce the error described in Common errors.

The formal rules are in the Language specification.