Message events serve as a means to incorporate messaging capabilities into business process modeling. These events are specifically designed to capture the interaction between different process participants by referencing messages.
Trigger | Description | Marker |
---|---|---|
Message | A Message Intermediate Event serves to send or receive messages. A filled marker denotes a “throw” event, while an unfilled marker indicates a “catch” event. This either advances the process or alters the flow for exception handling. Identifying the Participant is done by connecting the Event to a Participant through a Message Flow. | Throw ![]() ![]() |
Trigger | Description | Marker |
---|---|---|
Message | Non-interrupting Message Catch Event: The event can be triggered at any time while the associated task is being performed. | Non-interrupting ![]() |
Trigger | Description | Marker |
---|---|---|
Message | Interrupting Message Catch Event: The event can be triggered at any time while the associated task is being performed, interrupting the task. | Interrupting ![]() |
${kafka.topic.naming.prefix}.core.message.event.process${kafka.topic.naming.suffix}
. The engine listens here and writes the response.
attachedTo
: a property that applies to boundary eventsmessageName
: a unique name at the database level, should be the same for throw and catch eventscorrelationKey
: a process variable used to uniquely identify the instance to which the message is sentdata
: allows defining the JSON message body mapping as output and input