Cisco Cisco Unified IP Interactive Voice Response (IVR) 8.0(1) Leaflet

Use the Call Subflow step to execute a subflow, which is analogous to a 
subroutine or module in structured programming.

You create the subflow with the CRS Editor as an independent script that you can 
reuse in other scripts. You can also call subflows from within scripts that are 
themselves used as subflows.

If the script was originally loaded from disk, the subflow script must reside in the 
same folder as the script that calls it. If the script was loaded from the Repository, 
then the subflow must also reside in the Repository.

Use a subflow in a script (instead of a redirect) to transfer a call to another script. 

When you debug a script that uses subflows, the CRS Editor does not debug the 
subflows; it checks only the script you are debugging. If a subflow is invoked, it 
will be executed completely until the subflow returns back the control to the main 
flow being debugged. You must debug each subflow separately. The debug 
validation process does not detect mapping of mismatched types, but such a 
mapping causes a run-time exception when the script is loaded into the execution 
engine.

During run time, if an exception occurs within a subflow, and you do not handle 
the exception within the subflow, the exception is available to the parent script for 
processing. For more information about exceptions, see the 

.

The Call Subflow customizer window contains three tabs:

The following sections describe these tabs.