About Boundary Signal Intermediate Events
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.
You can configure the interrupting behavior with the Allow Boundary Signal Event to interrupt activity check box on the General page in the Properties view, except as noted in the supported event types table referenced above.
For a boundary event to catch an externally triggered event from a different track or process, the associated activity must be active.
Important: | Boundary signal events cannot be debugged directly for an externally-created signal event. When a signal event is transmitted from outside a process that is being debugged and there is a boundary signal event in the debugged process that is configured to receive and correlate to the transmitted signal, that signal is not recognized by the Process Engine as being associated with the process currently being debugged. |
Contact Support
|
Community
|
Feedback