Via messages, you can communicate with an open process instance and provide additional data into the instance.
This can e.g. be used to synchronize the process with other applications, or to wait for additional data before continuing.
Available BPMN elements with message parameter are:
BPMN Element | Usage | Details | |
---|---|---|---|
| |||
| |||
|
A receive task is a task that is ready to receive a message parameter: Via this message parameter, you can provide additional data to a process. The process will pause on a receive task and wait for the message reception. A torso of the above displayed execution diagram (On Exit 4) is already created when adding a receive task:
If you remove the execution diagram (4), the message parameter is dropped.
|
A message event is similar to a receive task but cannot have a boundary event. It can be used in two ways:
A message event can have execution: It is ready to receive a message parameter. To the execution of a message event, the same applies as for receive tasks (see above).
A message start event is a start event that is ready to receive a message. You can find more details on the message start event onĀ Message Start Event, and all about using message start events on Modeling Process Start > Message Start Event.
For message receiving process elements, the API of the generated xUML service has POST operations that can be used to send the message to the process as a body parameter. For the BPMN_Event_Example, that would be six in total:
Each of the POST operations get the process instance id via the path, and the related message parameter in the request body.
Refer to xUML Service Interface for more information on the xUML service API in general, and to Testing and Integration for details on how to access the API and a list of the available operations.