Throw

In Dialog Designer, custom events can be created for situations where they are needed. For example, perhaps a custom event is needed to handle caller requests to be transferred to an operator. Or custom events can be used to handle other out-of-the-ordinary situations.

Use the Throw item to throw events created using the Event Editor. For more information about creating and using custom events, see Working with Event Types.

Note:

The default VoiceXML events are thrown automatically, as the system responds to various predefined situations. Avaya designed the Throw event to only throw those custom events that have been created.

Before using the Throw item, an event must be created for it to throw. Also, somewhere in the application, within the scope of this item, a Catch (VXML Events) item must be used.

In most cases, a Throw item is used to respond to actions or inputs from callers that are outside the scope of what is expected. For example, perhaps a custom event is created in which the caller can request to transfer to an operator from anywhere in the call flow. Create an event called Xfer2Operator, for example. For more information about custom events, see Custom Events.

A Link item can be used in the AppRoot node, to monitor and respond to a caller request from anywhere in the call flow. When the caller utters the word or phrase that activates the Link item, the Link item throws the custom event. At this point, set up a Catch (VXML Events) event handler to instruct the application on what to do with the caller (that is, transfer the caller to an operator, in this case).

Throw items can also be used to handle situations where a certain threshold of other events has been reached and you want the system to respond differently after that point. For example, suppose you want to give callers only three chances to make an acceptable response to a Prompt and Collect node. However, if the No Match and No Input event handlers were treated independently and separately, the caller could have a total of five chances before the appropriate event is thrown.

A Throw item can be used in each of the No Match and No Input event handlers, and then catch it within the same node. By setting the Threshold for the Throw item to 3, then it does not matter whether the caller has a No Match or No Input situation. After the third event, the Throw item is activated, and the call flow moves on to whatever you set the Catch for this Throw item to do.

When an event is thrown, it is caught by the next higher level element in the application. In an input form, event throws at the field level can be caught at the form level, and an event thrown at the form level can be caught at the application root. You cannot catch an event at the same level that it is thrown. An event thrown at the menu level is caught at the application root level.

Tip:

For an example the Throw item being used as described, see the sample application named Events included with the Dialog Designer software package.

For more information about creating events, throwing events, and catching events, see Working with Event Types.

Note:

If you do not have any custom events defined, this list is populated only with the built-in events for cancel, exit, and help.

Note:

This field is available only when the Throw item is placed in an event handler or a node. This field is not available when the Throw item is placed in a Link item.

Nodes and Palette Options > Detailed Palette Option Descriptions > Throw

	Throw