Using Built-in Event Handlers for Default Events

Working with Event Types > Events in Applications > Using Built-in Event Handlers for Default Events

	Using Built-in Event Handlers for Default Events

The Avaya Application Simulator (AAS), which is used to run Dialog Designer applications, has built-in event handlers for the "default catch items" as defined and required by the VoiceXML Version 2.0 recommendation. This means that, for the default catch items, you are not absolutely required to use event handlers, because the AAS can handle them automatically.

These built-in event handlers, however, might not be what you want or need, as they are very generic in their responses. As such, they might not respond to a given event the way you want. Therefore, Avaya recommends that, whenever possible, you consider where and how to use the built-in Dialog Designer event handlers for these events:

Use built-in event handlers in the AppRoot node to catch any occurrences of those events for which you might not have event handlers in place at lower levels. For more information about using the AppRoot node for global settings, see Setting Global Application Properties: AppRoot Node.

Use built-in event handlers at the node (form) or node item (field) level within a node, to catch and respond in a specific way to those events that might be thrown at those levels.

For example, you might have a generic No Match event handler that says something like: "I'm sorry, I do not understand you." This might be fine for a global response, but for a particular Prompt and Collect node, you might want a more specific response like, "I'm sorry, that is not one of the options. For checking account information, please say or press 'one'; for savings account information, please say or press 'two'." In this case, you would add a No Match event handler to your Prompt and Collect node.

Note that it is not necessary, with the default catch items, to use a Throw item to throw the event. This functionality is already programmed into the AAS, and the system knows when to throw these events. All you need do is provide the event handler so the system knows how to respond when the event is thrown.