| Page | Date | User | Tags |
|---|
| A subprocess and a control branch may be used as an alternative to the attached event | 2023-09-10 11:32 | Anatoly Belaychuk | subprocess,
event,
attached event,
terminate event |
| Avoid micromanagement | 2023-08-06 14:34 | Anatoly Belaychuk | task,
subprocess |
| Check subprocess result on exit | 2023-08-06 14:56 | Anatoly Belaychuk | subprocess,
gateway |
| Diagram should fit one page | 2024-01-25 19:15 | Anatoly Belaychuk | subprocess |
| Error event may be used to model business exceptions | 2024-01-09 09:23 | Anatoly Belaychuk | event,
error event,
attached event,
end event,
subprocess |
| Follow structured modeling rules | 2024-08-25 20:18 | Anatoly Belaychuk | subprocess,
gateway,
loop |
| Subprocess must be started by none event | 2024-01-18 12:55 | Anatoly Belaychuk | event,
start event,
subprocess |
| Use a subprocess with a terminate or error error event to model veto power | 2025-01-08 20:05 | Anatoly Belaychuk | subprocess,
terminate event,
error event |
| Use collapsed subprocesses | 2023-08-05 12:03 | Anatoly Belaychuk | subprocess,
visual style |
| Use the same naming templates for processes and subprocesses | 2024-08-27 20:13 | Anatoly Belaychuk | naming,
process,
subprocess |