Building a process
Documentation status: reference — see Maturity and evidence.
Build a process from the business scenario, not from a thread or technical queue.
Recommended sequence
- name the expected business outcome;
- identify participants;
- define observable states or steps;
- choose entry actions;
- identify events and messages;
- define completion, failure, and recovery conditions;
- publish only the required capabilities.
Start action
-> create process state
-> step A
-> event/message
-> step B
-> completed | failed | cancelled
Asynchronous execution, retry, and transport details remain separate from the business meaning of the process.