The basic properties for a message intermediate throw event are:
| Property | Required | Description |
|---|---|---|
| ID | Required | The unique identifier for the message intermediate catch event. This is system generated and cannot be altered, for example: IntermediateThrowEvent_1yohpmt |
| Name | Optional | The name of the message intermediate catch event. This will be displayed on the canvas. |
| Documentation | Optional | A free text description of what the message intermediate catch event does. |
| Asynchronous Continuation | Optional | The Asynchronous Continuation checkbox (unchecked by default) makes it possible for the task to be executed in the background, using a different unit of work than the whole process. |
In addition to the basic intermediate event properties, the generic Message Intermediate Throw Event has the following properties:
| Property | Description |
|---|---|
| Message |
A message must be defined for the Message Intermediate Catch Event to receive. You can select an existing Message from the properties drop-down list, or create a new one using the + icon. After the message is selected or created, configure its name and payload. |
| Correlation key | Message events can optionally contain a correlation key. If a correlation key is present then when a message is thrown, it uses the activiti:correlationKey value and the messageRef of the throwing event to match against the same two properties in a catching event. If only one property is matched then the message will not be caught. |
| Message Payload |
A message payload contains the data sent from a throwing event to a catching event. Payloads are defined on message throwing events and consist of one or more properties. Each property includes a name, type, and value. Message payload mappings can be viewed in the Extensions Editor, where throwing events are mapped as inputs, and catching events are mapped as outputs. |
For more information on message configuration see Configuring Messages for Message Events.