Message Event

The Message Event waits for a message with a defined content. You can use the message event in the Designer as an intermediate event or as a boundary event:

• Intermediate: You can use the object as an intermediate catching event. In this case, the event is a separate process step where the process must wait for a specific trigger.

• Boundary: The signal is associated with an activity. The event listens to a signal being fired while the associated activity is active.

Plain Event, Message Event and Timer Event can be used as boundary events along with User Task and Receive Task. When using the events as boundary events, attach the element directly to the border of the corresponding task:

• Name

• Description

• Trigger Events (see Particularity)

• Symbol Type

Trigger Events: Use the attribute Trigger Events in the Attributes Panel to define which button of a form associated to the element triggers the default process flow of a BPMN process. This attribute is only available for boundary events.

On Exit: Input message (define the corresponding type of message in your own Library or Data Model class).

• Refer to Working with the BPMN Editor for further information regarding editing of BPMN elements using the different context menus on the diagram pane.

• Refer to Styling BPMN Elements for further information regarding styling possibilities for BPMN elements, for example how to change the background color, the font style and size etc.