Each subflow represents a subordinate business process. When used within a process flow, subflows help keep the process flow from becoming too complex. Use subflows to break up process flows into sections of 50 activities or less. You can embed subflows within process flows and within other subflows.
A subflow cannot contain a starting point because you cannot initiate work items in a subflow.
Subflows must contain:
one initial activity
a single Exit Point Activity
Subflows can contain:
Manual Activities
Automatic Activities (BICs)
Split and Join Activities
DPAs, Iterator, Work Item Merge, and Work Item Priority Activities
Subflow, Personal Subflow, and Remote Subflow Activities
Subflows cannot contain:
Load Balancer Activities
Anonymous Activities