This page was last edited on November 30, 2018, at 18:46.
Comments or questions about this documentation? Contact us for support!
Use the Exit block to end the application. There will usually be an Exit block in every main callflow, unless you use a GoTo block, blind transfer, or other mechanism to end a callflow. Return Mode should be set to false in the main callflow's Exit block. The Exit block is typically connected to the connection.disconnect.hangup exception handler. It is also connected to the last block in the application (for example, when the application wants to play an error message and terminate the call). You can have multiple Exit blocks inside a callflow. The Exit block has no page exceptions.
The Subdialog block is used to create subcallflows, which are VoiceXML subdialogs. An Exit block terminates the subcallflow application. If the control has to be returned to the main application, then the Return Mode property should be set to true and the user can send a list of parameters to the main call flow as the output parameters. Name
Find this property's details under Common Properties.
Can be used for both callflow and workflow blocks to add comments.
This property is visible only for subcallflows. Enter a reason for the implicit ActionEnd to be used for VAR reporting.
This property is visible only for subcallflows. Click the down arrow under Value and select one of the following:
Use this property to specify the variable(s) whose value(s) will be returned once the Exit block is executed. To select return variables:
Find this property's details under Common Properties for Callflow Blocks.
Find this property's details under Common Properties for Callflow Blocks.
Find this property's details under Common Properties for Callflow Blocks.
Find this property's details under Common Properties for Callflow Blocks.
This property is visible only for subcallflows. Click the down arrow and select one of the following to be used for VAR reporting: