Differences
This shows you the differences between two versions of the page.
| 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 Belaychuk | en:rule:check_subprocess_results [2024-08-22 20:12] (current) – [Check subprocess results on exit] Anatoly Belaychuk | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Check subprocess | + | ====== Check subprocess |
| - | + | ||
| - | {{tag> | + | |
| - | + | ||
| - | {{: | + | |
| - | + | ||
| - | After subprocess call check its results stored in process data. | + | |
| + | {{tag> | ||
| ===== ✔ How to ===== | ===== ✔ How to ===== | ||
| Line 173: | Line 168: | ||
| ===== Notes ===== | ===== Notes ===== | ||
| - | Logic is the same for embedded subprocesses, call activities | + | * 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 | ||
| ===== Exceptions ===== | ===== Exceptions ===== | ||
| - | Subprocess call not followed by a gateway means that subprocess results don't affect process execution. It' | + | * Deal negotiation in the " |
| ===== See also ===== | ===== See also ===== | ||
| - | [[en:rule:implicit_parallel]] | + | * [[en:rule:business_exception_error]] |
| - | + | | |
| - | [[en:rule:business_exception_error]] | + | |
| ===== Author(s) ===== | ===== Author(s) ===== | ||
| --- // | --- // | ||
| + | |||