<nomatch>
Last updated
Last updated
The <nomatch>
element is short for <catch event=“nomatch”>.
Name | Data type | Description |
---|---|---|
None
The output of the above script would be:
Computer: Please enter your user identification number. User: <user enters: 1 2 3> (nomatch x1) Computer: Your input was not valid. Your customer identification number should be the five digit number you received in your sign up email. Computer: Please enter your user identification number. User: <user enters: 1 2 3 4> (nomatch x2) Computer: Your input was not valid. Your customer identification number should be the five digit number you received in your sign up email. Computer: Please enter your user identification number. User: <user enters: 2 2 2> (nomatch x3) Computer: It appears you are having difficulty with your customer identification number. Please try your call again later. Goodbye. *application hangs up*
<assign>, <audio>, <clear>, <data>, <disconnect>, <enumerate>, <exit>, <foreach>, <goto>, <if>, <log>, <prompt>, <reprompt>, <return>, <script>, <submit>, <throw>, <value>, <var>
<field>, <form>, <menu>, <record>, <subdialog>, <transfer>, <vxml>
count
(defaults to 1) The occurrence of the event. The count allows you to handle different occurrences of the same event differently.
Each <form>, <menu>, and form item maintains a counter for each event that occurs while it is being visited. These counters are reset each time the <menu> or form item's <form> is re-entered. The form-level counters are used in the selection of an event handler for events thrown in a form-level <filled>.
Counters are incremented against the full event name and every prefix matching event name. For example, occurrence of the event “event.foo.1” increments the counters associated with handlers for “event.foo.1” plus “event.foo” and “event”.
cond
(defaults to true) An expression that must evaluate to true after conversion to Boolean in order for the event to be caught.