AppRoot Node Event Handlers

Working with the Call Flow Editor > Setting Global Application Properties: AppRoot Node > AppRoot Node Event Handlers

	AppRoot Node Event Handlers

Event handlers, in the AppRoot node, include options that determine how the application handles exceptions that are not defined within a specific node or field.

The AppRoot node can include the following types of Event Handlers. Also see AppRoot Node Application Items for more information.
AppRoot Node Event Handler

Event Handler

Description
Catch (VXML Events)

Determines how an event meeting specific criteria is to be handled when the event is thrown. For it to function, you must assign to the Catch event handler at least one Prompt, Goto, or Throw item.

Exit

In the case where there are more serious errors, consider using the Exit event handler to exit the application or to return events back to the calling application (from a module).

No Input

Determines what the application does whenever the caller fails to respond. For it to function, you must assign to the No Input event handler at least one Prompt, Goto, or Throw item.

No Match

Determines what the application does whenever the system cannot match the response from a caller with any expected response. For it to function, you must assign to the No Match event handler at least one Prompt, Goto, or Throw item.

On Disconnect

Determines how the system responds when the caller hangs up, no matter where in the call flow the disconnection occurs.

Return Event

Returns an event to the calling application. Can be used to propagate an event caught in a module to the calling application, or may be used to throw a different event back to the calling application.

Transfer

Special transfer that can be added as a child of an event handler (Catch) and is used to transfer the caller to an extension (that is, to an agent) in the event that the application experiences unrecoverable errors (for example, the application server crashes).

This item will generate a Blind Transfer to a destination that comes from a variable or is hard coded.

Event Handler	Description
Catch (VXML Events)	Determines how an event meeting specific criteria is to be handled when the event is thrown. For it to function, you must assign to the Catch event handler at least one Prompt, Goto, or Throw item.
Exit	In the case where there are more serious errors, consider using the Exit event handler to exit the application or to return events back to the calling application (from a module).
No Input	Determines what the application does whenever the caller fails to respond. For it to function, you must assign to the No Input event handler at least one Prompt, Goto, or Throw item.
No Match	Determines what the application does whenever the system cannot match the response from a caller with any expected response. For it to function, you must assign to the No Match event handler at least one Prompt, Goto, or Throw item.
On Disconnect	Determines how the system responds when the caller hangs up, no matter where in the call flow the disconnection occurs.
Return Event	Returns an event to the calling application. Can be used to propagate an event caught in a module to the calling application, or may be used to throw a different event back to the calling application.
Transfer	Special transfer that can be added as a child of an event handler (Catch) and is used to transfer the caller to an extension (that is, to an agent) in the event that the application experiences unrecoverable errors (for example, the application server crashes). This item will generate a Blind Transfer to a destination that comes from a variable or is hard coded.