Transaction boundaries should not be displayed on Event-based Gateways unless they have asyncBefore=true. My customer today got confused by this into thinking that the event subscriptions after the Gateway are executed in a separate transaction and was afraid of race conditions.
All flow nodes that are allowed after an Event-based Gateways are wait states and have TX boundaries correctly displayed on them. So we can simply remove the TX boundary before the Gateway.
Transaction boundaries should not be displayed on Event-based Gateways unless they have
asyncBefore=true. My customer today got confused by this into thinking that the event subscriptions after the Gateway are executed in a separate transaction and was afraid of race conditions.All flow nodes that are allowed after an Event-based Gateways are wait states and have TX boundaries correctly displayed on them. So we can simply remove the TX boundary before the Gateway.