A conversation node is a hexagon symbol in a conversation diagram that links two participants and regroups a set of message exchanges that share the same correlation.
Conversation nodes can be decomposed and contain their own conversation diagrams in the same way as standard BPM processes (see Decomposing Processes).
| Property | Description |
|---|---|
| Name | Specifies the name of the item, which should be clear and meaningful, and should convey the item's purpose to non-technical users. |
| Code | Specifies the technical name of the item, which is used for generating code or scripts. |
| Comment | Specifies a descriptive comment for the object. |
| Stereotype | Extends the semantics of the object. You can enter a stereotype directly in this field, or add stereotypes to the list by specifying them in an extension file. |
| Composite status | Specifies whether the task is a simple conversation or a sub-conversation (which can itself contain conversation nodes, listed on the Conversation Nodes tab). If you revert from a sub-conversation back to a communication, then any conversations that you have created inside it will be deleted. For detailed information about decomposing objects, see Decomposing Processes. |
| Reusable | Specifies whether the conversation node may be reused in other contexts. |
| Reuse conversation | Specifies the conversation node that is being reused in this context. |
| Correlation key | [atomic conversations only] Specifies the correlation key (set of correlation properties drawn from the message) used to associate the conversation to a particular instance of a process (see Correlation Keys (BPM)). Each flow connected to the node must have the same key as the node. |