Differences

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

--- en:rule:event_gateway_warning [2023-09-10 12:51] – Anatoly Belaychuk
+++ en:rule:event_gateway_warning [2024-08-24 15:49] (current) – [Use event gateways with caution] Anatoly Belaychuk
@@ Line 1: / Line 1: @@
-====== Use the event gateway with caution ======
+====== Use event gateways with caution ======
-{{tag>subprocess gateway event}}
+{{tag>gateway parallel_gateway event_gateway}}
+Event gateway immediately interrupts all catching events when any single one occurs.
+For more versatile logic consider the combination of parallel gateway and terminating event.
-Mind the difference between the diagrams above: while the "to do" process waits for the message all the time till the end, the "no to do" process interrupts when the timer triggers. If the message arrives while while we are discussing the issue with the client, it won't be catched and the process will hang after returning to the event gateway. This is rather common mistake.
 ===== ✔ How to =====
@@ Line 303: / Line 305: @@
 </bpmnio>
-===== Exceptions =====
+===== Notes =====
-Specify exceptions to the rule above, if any
+Mind the difference between the diagrams below: while "to do" process waits for the message all the time till the end, "no to do" process interrupts when the timer triggers. If the message arrives while we are clarifying delay with the client, it won't be caught and the process will hang after returning to the event gateway.
 ===== See also =====
-Reference similar rules here (this section is optional)
+  * [[en:rule:control_branch]]
+===== Автор(ы) =====
-===== Автор(ы) =====
+ --- //[[user:bell|Anatoly Belaychuk]] 2023-09-10 12:51//
-Put signature here