Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
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 | ||
---|---|---|---|---|
| ||||
| ||||
|
Receive Task
Multiexcerpt include | ||||||
---|---|---|---|---|---|---|
|
Multiexcerpt include | ||||||
---|---|---|---|---|---|---|
|
Multiexcerpt | ||
---|---|---|
| ||
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.
|
Message Event
Multiexcerpt include | ||||||
---|---|---|---|---|---|---|
|
A message event is similar to a receive task but cannot have a boundary event. It can be used in two ways:
- on the boundary of a receive or user task
- in the process sequence flow
- If used as a message boundary event, the reception of the message ends the task the boundary event is used on.
- If the message arrives, the process ends the receive or user task, and continues with the sequence flow on the message event.
- If the message event does not arrive, the process stays in the task the boundary event is used on.
- If used in the sequence flow of the process, the process pauses and waits for the message before continuing.
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).
Message Start Event
Multiexcerpt include | ||||||
---|---|---|---|---|---|---|
|
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.
Messages in the Process API
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:
- two POST operations, one for each start event (1,2)
- four POST operations, one for each message related task or event
- Receive_a_message (receive task, 3)
- Message_Event (message boundary event, 4)
- Plain_Event (boundary event, no message, 5)
- Wait_for_message_before_proceeding (message intermediate event, 6)
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.
Panel | ||
---|---|---|
| ||
|
Multiexcerpt include | ||||||
---|---|---|---|---|---|---|
|
Multiexcerpt include | ||||||
---|---|---|---|---|---|---|
|
Panel | ||
---|---|---|
| ||