Boundary signal intermediate events inherit
Integration Server Name settings from the step to which they are attached. They can be
interrupting or
non-interrupting depending on the activity type. The supported types are described in
About Interrupting Behavior for
Boundary Intermediate Events.
For a boundary event to catch an externally triggered event from a different track or process, the associated activity must be active.