Process items. Intermediate Throwing Events
When an incoming sequence flow is activated, intermediate throwing events create messages or signals that activate the corresponding catching events.
An intermediate throwing message activates the message whose name is indicated in the properties of the given event.
For example, before the sales manager starts preparing documents (Fig. 130), the accountant has to confirm that the payment from the customer was received.
Fig. 130 Intermediate throwing message
In this case, the “Control payment” user task in the “Accounting” lane initiates the “Payment received” throwing message that is expected in the “Sales” lane by the corresponding catching event with the same name.
The message cannot be sent to a different process.
[Message] – This property is used to specify the name of the throwing message.
An intermediate throwing signal works in the same manner as an intermediate throwing message. Unlike the message event, the signal is sent to all active processes in the system. If the intermediate throwing signal event is triggered:
•In all active processes, all catching signals that have the selected signal indicated in their properties will be triggered;
•All processes that are activated by this start throwing signal will be initiated.
Use the [Signal] property to specify the name of the signal that will be sent by the selected event.
See also
