How to connect BPMN processes between end and start points

A Start event in a process:
- ❌ Cannot have an incoming event or sequence flow from a Task, Activity, Call Activity, or (sub)Process.
- ✅ Can have an incoming Message flow from another Pool or Process in a Collaboration.
An End event in a process:
- ❌ Cannot have an outgoing event or sequence flow to a Task, Activity, Call Activity, or (sub)Process.
- ✅ Can have an outgoing Message flow to another Pool or Process in a Collaboration.

Since direct sequence flows from one process to another are not allowed, you can use these alternatives:

Instead of ending Process A with an End event, end it with a Call Activity.
This activity can call another external process (Process B, which can be an orchestration or collaboration).
Keep in mind: In the diagram of Process B, you will not see that it was started from Process A.

Visualize the relationship in a Collaboration diagram.
Show Process B starting from a Message flow that originates from Process A.
This makes the interaction explicit between the two Pools or between activities in different Pools.

Direct sequence connections between End and Start events across processes are not permitted by BPMN.
To maintain BPMN compliance, use either a Call Activity or a Message flow in a Collaboration.

In BPMN, it may seem logical to directly connect the end of one process to the start of another. However, Mavim follows the formal BPMN specification defined by the Object Management Group (OMG). This means there are strict rules about how processes can be linked.