Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| en:rule:disconnected-flows [2024-08-21 21:25] – [Disconnected sequence flows not allowed] Anatoly Belaychuk | en:rule:disconnected-flows [2024-08-21 21:31] (current) – [Disconnected sequence flows not allowed] Anatoly Belaychuk | ||
|---|---|---|---|
| Line 2: | Line 2: | ||
| {{tag> | {{tag> | ||
| - | |||
| - | {{en: | ||
| Pool (if not a "black box") depicts a non-breaking activities flow of a single process. | Pool (if not a "black box") depicts a non-breaking activities flow of a single process. | ||
| Line 325: | Line 323: | ||
| ===== Notes ===== | ===== Notes ===== | ||
| - | У процесса может быть больше одного начального и больше одного конечного события, но все они должны быть связаны потокам управления в единый поток работ. | + | Although BPMN 2.0 specification does allow disconnected flows, this is a bad practice that should be avoided. |
| - | Подпроцесс " | + | A process may have more than one start and/or end event, all of them must be connected into a single work flow. |
| + | Parallel block subprocess ("how not to", bottom) may confuse non-professional users and therefore should be avoided. | ||
| + | Better use explicit parallel split and merge ("how to", bottom). | ||
| ===== Exceptions ===== | ===== Exceptions ===== | ||
| - | Подпроцесс " | + | Ad-hoc subprocess: |
| <bpmnio type=" | <bpmnio type=" | ||