Differences

This shows you the differences between two versions of the page.

--- en:rule:collapsed_subprocess [2024-01-11 23:27] – external edit 127.0.0.1
+++ en:rule:collapsed_subprocess [2024-03-24 18:39] (current) – [Use collapsed subprocesses] Anatoly Belaychuk
@@ Line 1: / Line 1: @@
 ====== Use collapsed subprocesses ======
-{{tag>subprocess}}
+{{tag>subprocess visual_style}}
 Primary purpose of subprocesses is process diagram simplification by decomposition. Depicting subprocess expanded makes the diagram more complicated, hence it's usually better to use collapsed representation.
@@ Line 424: / Line 424: @@
 ===== Notes =====
-The overarching process / subprocess logic should not depend on the subprocess internals. As an example, at the diagrams above two flows exit from both approval and signing subprocesses. Whatever happens inside the subprocesses, it comes down either to "OK" or to "not OK" option.
+  * The overarching process / subprocess logic should not depend on the subprocess internals. As an example, at the diagrams above two flows exit from both approval and signing subprocesses. Whatever happens inside the subprocesses, it comes down either to "OK" or to "not OK" option.
 ===== Exceptions =====
-It may make sense to depict a sub-process expanded if it's used not for decomposition, but as a special technique like the [[en:rule:control_branch | control branch]].
+  * It may be handy to expand a subprocess for training/explanatory purposes but working process models should depict them collapsed.
+  * It may make sense to depict a sub-process expanded if it's used not for decomposition, but as a special technique like the [[en:rule:control_branch | control branch]].
 ===== See also =====