Title: Messages

Describe the issue: CONTRADICTION in definition of BPMN 2.0 messages. in one pargraph they are said to be meant for communication with EXTERNAL systems, and in the description, exactly the opposite is stated


Suggestions for improvement:

Ask ENGINEERING to describe the actual behavior


Additional information:

A.3. Collaboration mechanisms
Elements with execution semantics make use of general collaboration mechanisms. Different Elements allow you to access and use the mechanism in a different way; for example, there is a mechanism called signalling: a Signal is sent by a Throw Signal Intermediate Event Element and received by a Catch Signal Intermediate Event (two Elements with execution semantics make use of the same Signal mechanism).
Collaboration mechanism include the following:

    Messages: intended primarily for communication with other systems especially if a complex data type is required (it is possible ton define a Message structure that can become a process variable)
    Escalations: mainly inter-process (between processes) signalling of escalation to trigger escalation handling
    Errors: mainly inter-process signalling of escalation to trigger escalation handling
    Signals: general, mainly inter-process instance communication 

All the events are managed by the signaling mechanism. To distinguish individual objects of individual mechnism the signal use different signal codes or names.
Report a bug
⁠A.3.1. Messages
“A Message represents the content of a communication between two Participants. In BPMN 2.0, a Message is a graphical decorator (it was a supporting element in BPMN 1.2). An ItemDefinition is used to specify the Message structure. ⁠[1]”
Messages are objects that can be send between Processes or Process elements, that participate in the respective communication; Messages are ment for inter-Process communication, not for communication with other external systems. They are send by the Message Intermadiate Throw Events and Send Tasks, and can be consumed by the Message Start Events, Message Intermediate Catch Events, Message End Events, and Receive Tasks. One Message can be consumed by an arbitrary number of Processes and Process elements.