A subflow represents a subordinate business process that has a single input activity and single output activity. When used in 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 other subflows, and you can use the Remote option to make the subflow available to remote instances of the EPX Application Server.
You add Manual Activities, BICs, System Activities, Transitions, Split Activities, Join Activities, and other subflows to a subflow just as you would to a process flow. You can also validate, print, and delete a subflow just as you would a process flow, as described in the previous chapter.
Subflows must contain:
one initial activity
a single Exit Point Activity
Subflows can contain:
Manual Activities
Automatic Activities (BICs)
Split and Join Activities
DPAs, and Iterator, Work Item Merge, and Work Item Priority Activities
Subflow, Personal Subflow, and Remote Subflow Activities
Subflows cannot contain:
Load Balancer Activities
Anonymous Activities