About Subscription Triggers
A subscription trigger starts a new process instance or joins an existing process instance at a particular step. You configure an appropriate receive step to receive a message or a signal from outside the process. This information in this message or signal is transmitted to the receive step using the messaging protocol specified for that information type. The receive step then uses this information to either trigger a new process instance or join an existing process instance.
Subscription triggers are generated using the data that comes into the step and the protocol specified to transmit that information. Several different types of receive steps can use subscription triggers to start a process or join an already started process.
Top-Level Process Steps | Available Messaging Protocols |
Message start event (receive a message and start a process) Message intermediate event (receive a message and join a process) | Subscription (For Publishable Documents) JMS (For JMS Triggered Processes) EDA (For EDA Event Triggered Processes |
Signal start event (observe a signal and start a process) Signal intermediate event (observe a signal and join a process) | Subscription (For Publishable Documents) JMS (For JMS Triggered Processes) |
Receive task  Receive a message and start a process Receive a message and join a process | Subscription (For Publishable Documents) JMS (For JMS Triggered Processes) Simple Service (For Synchronous Receive/Send) |
None start event (receive a message and start a BPMN callable process from a parent process) | Subscription (For Publishable Documents) JMS (For JMS Triggered Processes) EDA (For EDA Event Triggered Processes Important: | A BPMN callable process requires a none start event to start. The none start event can exist in addition to another start step (such as a message start step) that applies to the process when it is running as other than a callable process. |
|
