Signal Event

In descriptive models, a Signal trigger, which can be either throwing or catching, may be sent between any Signal events in the same process instance or even across processes. However, in executable models, Workflow Modeler restricts Signal events to communication within a process instance. A throwing Signal event can be caught by a catching Signal event or boundary event, interrupting or non-interrupting, anywhere in the process.

Signal works via publish-subscribe integration. The Signal trigger has a Name property, and any catching Signal event subscribing to that Name will catch the trigger. Signal start event is not supported by Automation.

The Attributes/Signal Event context menu lets you define the trigger Name and, optionally, its datatype. A Signal may contain data, which is captured to a data object via data output mapping, or may contain no data.