Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| en:rule:explicit_parallel_merge [2024-08-24 16:48] – ↷ Page name changed from en:rule:explicit_parallel_join to en:rule:explicit_parallel_merge Anatoly Belaychuk | en:rule:explicit_parallel_merge [2024-09-26 13:54] (current) – [See also] Anatoly Belaychuk | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== | + | ====== Make parallel merge explicit ====== |
| {{tag> | {{tag> | ||
| - | |||
| - | {{en: | ||
| Use parallel gateway to merge parallel flows. | Use parallel gateway to merge parallel flows. | ||
| Line 138: | Line 136: | ||
| </ | </ | ||
| - | Задача, | + | Task with two incoming flows will be executed twice. |
| - | Вряд ли это то, чего вы хотели. | + | Probably this wasn't your intention. |
| <bpmnio type=" | <bpmnio type=" | ||
| Line 205: | Line 203: | ||
| </ | </ | ||
| - | Исполнение такой модели в BPMS приведет к искажению отчетности | + | Executing this model by BPMS would lead to misreporting |
| <bpmnio type=" | <bpmnio type=" | ||
| Line 274: | Line 272: | ||
| </ | </ | ||
| - | Как и в предыдущем примере, BPMS выдаст искаженную отчетность, | + | Similarly to previous example, BPMS would produce wrong reports with doubled number of end events. |
| ===== Exceptions ===== | ===== Exceptions ===== | ||
| Line 346: | Line 343: | ||
| </ | </ | ||
| - | Если одна или несколько параллельных ветвей заканчиваются событием-остановом или событием-ошибкой. | + | Ending parallel branches without merge may make sense if one or more come to terminate or error event. |
| ===== See also ===== | ===== See also ===== | ||
| * [[explicit_parallel_split]] | * [[explicit_parallel_split]] | ||
| * [[do_not_save_on_gateways]] | * [[do_not_save_on_gateways]] | ||
| + | * [[structured_diagram]] | ||
| ===== Author(s) ===== | ===== Author(s) ===== | ||
| --- // | --- // | ||
