Sequence flows are solid lines with an arrow at one end, which link the elements in a process in the diagram or in a single pool and show the order in which they are performed. Message flows are dotted lines with an arrow at one end, which link elements in two separate pools and show the direction in which the message is sent.
Identify the object. The name should clearly convey the object's purpose to non-technical users, while the code, which is used for generating code or scripts, may be abbreviated, and should not normally include spaces. You can optionally add a comment to provide more detailed information about the object. By default the code is generated from the name by applying the naming conventions specified in the model options. To decouple name-code synchronization, click to release the = button to the right of the Code field.
|Source/ Destination||Specify the objects that are linked by the flow. For sequence flows, the source object comes before the destination object in the process. For message flows, the source object emits the message and the destination object receives it.|
|Condition||[sequence flows] Specifies the condition that must be fulfilled for the process to take this branch following a gateway.|
|Message format||[message flows] Specifies the message that transits the flow (see Messages (BPMN Executable))|
|Correlation key||[message flows] Specifies the correlation key used to associate the message to a particular instance of a process (see Correlation Keys (BPMN Executable)). In a conversation diagram, each flow must have the same key as the conversation node to which it is connected.|
|Correlation property||[message flows] Specifies the correlation property that acts as the unique identifier for this instance of the message .|