Working with the Call Flow Editor > Working with Sub Flows (vs. Modules) > Refactoring Projects to Use Sub Flows
	Refactoring Projects to Use Sub Flows

When refactoring projects to use Sub Flows, review the following considerations before performing your refactoring efforts:

• Move nodes (cut and paste) between main flow and sub flows. This preserves variable names and references and will not create duplicates (clones).

• Some nodes cannot be moved to a Sub Flow. AppRoot and Return (main.flow) are not allowed on Sub Flows. Do not include them in the selection when moving to the Sub Flow.

• Symbolic node references may be cleared. (Cleared if symbolic node is copied, but the reference node is not.)

• Plan the return points from the Sub Flow, as follows:

• A Sub Flow may utilize multiple return points in order to handle different return paths in the calling flow.

• When selecting a group of nodes to move to a Sub Flow, often a symbolic node indicates a need for a return point when the reference node is not in the selection.

• Renaming a Sub Flow is supported, but not encouraged. Never rename "main.flow".

• Copying or Cutting from main flow to a Sub Flow will copy or move Java code. User-defined code may have compile errors if referencing code in "flow" package without fully qualified name (For example, Project Variables).

• Imports must be organized to fix import statements:

• Open Java class: Source > Organize Imports (Ctrl+Shift+O).

• From Package/Project Explorer view, right click the Java class: Source > Organize Imports

• Cut and paste in same flow is no longer supported

• Cut and Paste in same flow is just a move operation.

• Was not recommended before because it would clear variable references.

©2009, Avaya Inc. All rights reserved.