Optional message flow lines can visually indicate expected message flow, but do not carry information used by the simulator. The simulator reads data from the message properties on each activity.
Home > Process Modeling and Simulation Concepts > Messages in Models
A message is used to synchronize and pass information between two related processes or pools that execute separately. These are sometimes called messaging partners.
For example, if a Customer process places an order (transaction) with the Vendor process whose order ID is 123, the customer may later send a message to cancel order ID 123. This message does not cancel all orders; just ID 123.
A message can:
Collect transactions at input.
Create a new transaction in the process when a message arrives.
Send or broadcast a message when transactions complete in a selected activity.
Interrupt the process of an activity and take an exception path if a message arrives.
|
|
Optional message flow lines can visually indicate expected message flow, but do not carry information used by the simulator. The simulator reads data from the message properties on each activity. |
If your process models a fault, the exception path can trigger a message sent to a messaging partner or another activity in the process.
Related Topics:
See Also