A BusinessProcess element in Enterprise Architect comes from the Process class in the BPMN specification. The inheritance chain for this is CallableElement, RootElement and Base Element. The specification uses this as a diagram as you can see from the quotes below. Enterprise Architect has introduced an element to hold the properties of the Process.
"In BPMN a Process is depicted as a graph of Flow Elements, which are a set of Activities, Events, Gateways, and Sequence Flows that define finite execution semantics (see Figure 10.1)."
"Note that BPMN uses the term Process specifically to mean a set of flow elements. It uses the terms Collaboration and Choreography when modeling the interaction between Processes."
A sequence flow is a link between two FlowNodes. In the description of a sequence flow in the specification you will find that "Only the Gateway, Activity, Choreography Activity, and Event elements can connect to Sequence Flows and thus, these elements are the only ones that are sub-classes of FlowNode." This is the rule that was implemented in version 10.
To model a sequence of processes in a conformant way you would create CallActivity elements referencing the process.
To do this in Enterprise Architect:
- Create an Activity
- Set the isACalledActivity tagged value to true
- Set the calledActivityRef tagged value to the Business Process Element
However, it's obvious that there are many users having this issue. Our goal is to make it easier to make a model, not harder. We are planning to release a patch for version 10 that will allow Business Process elements to be directly connected using a Sequence Flow.