TX Plugin: TX boundaries are displayed on Event-based Gateways #18
Comments
falko
added a commit
to falko/camunda-transaction-boundaries
that referenced
this issue
Nov 26, 2019
and add TODO about Parallel/Inclusive Gateway with multiple incoming sequence flows fixes camunda/camunda-modeler-plugins#18
pinussilvestrus
pushed a commit
to bpmn-io/camunda-transaction-boundaries
that referenced
this issue
Nov 26, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The text was updated successfully, but these errors were encountered: