Home > Process Modeling and Simulation Concepts > Messages in Models > Broadcast Messages
Broadcast messages signal that something has happened that may be interesting to any transaction in the receiving partner. This type of message is not used to synchronize cooperating processes, but is more like a general purpose event sent from one partner to another. An example might be a StockTradingSuspended message meant to inform any transaction handling stock trades of the event. Contrast this with a TradeCompleted message that must apply to a single transaction in the client.
Because a broadcast message is not received by a single transaction, it cannot expect a return value. The Receive Data list in the Define Messages dialog box is disabled when Broadcast Message is checked.
All transactions at the receiving activity receive the broadcast message at simulation time, not just the one or more that were created by the same transaction in the sending process. The broadcast message does not throw an Undeliverable Message fault if no activity receives it.
Marking a message as a broadcast is not standard BPMN behavior, and was implemented by iGrafx before BPMN added the Signal event. You may want to consider using a Signal instead of a Broadcast Message.
Related Topics: