In BPMN, the communication between processes is defined as a sequence of activities that represents message exchange.
These messages flows are represented by a dotted arrow called Message flow connector. As the connections are made between different pools, it would be incorrect to connect a message flow to an activity within the same process.
A pool has many connection points, and you can locate the points by dragging the start or end connection along the border.
Whenever a connection is available for connection, it will highlight to a green point.
In BPMN, the communication between processes is defined as a sequence of activities that represents message exchange.
These messages flows are represented by a dotted arrow called Message flow connector. As the connections are made between different pools, it would be incorrect to connect a message flow to an activity within the same process.
A pool has many connection points, and you can locate the points by dragging the start or end connection along the border.
Whenever a connection is available for connection, it will highlight to a green point.
You would use involve more than 1 as these also have an explicit direction (so you will most likely have one message from Process A to B, then some stuff is done in Process B, and finally Process B sends a message back to Process A).
Keep in mind that the example above provides a general message connection illustration, but you may also have those message endpoints connect directly to and between tasks (or events).
For example: from Task 1 in Process A to Task 1 in Process B, and then another from Task 2 in Process B to Task 2 in Process A.
If I got this straight: If I have 3 proccesses that are related in some way, let's say at some point you can call one process from within another. They are not sub processes of each other. So, to represnt that I use the Message Exchanges Flow.
In BPMN, the communication between processes is defined as a sequence of activities that represents message exchange.
These messages flows are represented by a dotted arrow called Message flow connector. As the connections are made between different pools, it would be incorrect to connect a message flow to an activity within the same process.
A pool has many connection points, and you can locate the points by dragging the start or end connection along the border.
Whenever a connection is available for connection, it will highlight to a green point.
In BPMN, the communication between processes is defined as a sequence of activities that represents message exchange.
These messages flows are represented by a dotted arrow called Message flow connector. As the connections are made between different pools, it would be incorrect to connect a message flow to an activity within the same process.
A pool has many connection points, and you can locate the points by dragging the start or end connection along the border.
Whenever a connection is available for connection, it will highlight to a green point.
So do you use one message flow per message, or does one message flow cover all messages being sent between the two processes?
Dear Jeff,
One message flow represents one message.
You would use involve more than 1 as these also have an explicit direction (so you will most likely have one message from Process A to B, then some stuff is done in Process B, and finally Process B sends a message back to Process A).
Keep in mind that the example above provides a general message connection illustration, but you may also have those message endpoints connect directly to and between tasks (or events).
For example: from Task 1 in Process A to Task 1 in Process B, and then another from Task 2 in Process B to Task 2 in Process A.
Best regards,
I'm a little late here , i suppose.
If I got this straight: If I have 3 proccesses that are related in some way, let's say at some point you can call one process from within another. They are not sub processes of each other. So, to represnt that I use the Message Exchanges Flow.
Comments have been locked on this page!