Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
en:rule:check_subprocess_results [2023-08-19 13:29] – ↷ Page name changed from en:rule:subprocess_results to en:rule:check_subprocess_results Anatoly Belaychuken:rule:check_subprocess_results [2024-08-22 20:12] (current) – [Check subprocess results on exit] Anatoly Belaychuk
Line 1: Line 1:
-====== Check subprocess results on exit ====== +====== Check subprocess result on exit ======
- +
-{{tag>subprocess}} +
- +
-{{:underconstruction.png?nolink&200|}} +
- +
-After subprocess call check its results stored in process data.+
  
 +{{tag>subprocess gateway}}
 ===== ✔ How to ===== ===== ✔ How to =====
  
Line 173: Line 168:
 ===== Notes ===== ===== Notes =====
  
-Logic is the same for embedded subprocessescall activities or tasks. +  * If a subprocess isn't followed by a gateway then it is assumed that the subprocess is always successful which usually isn't the case. A subprocess not followed by a gateway may be not a mistake but should raise question whether we anticipate the possibility of unsuccessful subprocess completion. 
 +  * This rule is applicable to embedded subprocesses and call activities calling a process, collapsed and expanded subprocesses.
 ===== Exceptions ===== ===== Exceptions =====
  
-Subprocess call not followed by a gateway means that subprocess results don't affect process execution. It'the case sometimes but better check twice. +  * Deal negotiation in the "How not to" diagram above may be always successful if it'concluded between affilated parties, e.g. a business unit company and a shared services company belonging to a single group. No need for a gateway in this case.
 ===== See also ===== ===== See also =====
  
-[[en:rule:implicit_parallel]] +  * [[en:rule:business_exception_error]] 
- +  [[en:rule:human_decision]]
-[[en:rule:business_exception_error]]+
  
 ===== Author(s) ===== ===== Author(s) =====
  
  --- //[[user:bell|Anatoly Belaychuk]] 2023-08-06 14:41//  --- //[[user:bell|Anatoly Belaychuk]] 2023-08-06 14:41//
 +