In a hierarchical process where an activity has a subflow of activities, the subflow can run
in one of the following ways:
An empty activity with no steps automatically runs its subflow one time.
A process step (for example, DOE or Loop), also referred to as a driver step, inherently makes
calls to run the subflow multiple times as part of its execution logic.
An explicit step can be added to the inner flow of an activity to denote that the subflow should
run at that point.
Note:
Only one subflow is allowed in an activity.
The following simulation process shows the different subflows as described above: