VoiceXML 2.1 Development Guide

<error> element

The error element is the shorthand for the <catch event=”error”> handler, and will catch all events whose value begins with ‘error’. See the documentation for 'exceptions' to learn more.

usage

attributes

cond	Data Type: CDATA	Default: Optional (true)
	The cond attribute specifies a Boolean expression, which must equate to ‘true’ in order for the content to be visited and executed. Any standard ECMAScript Boolean value is valid for this attribute.
count	Data Type: CDATA	Default: Optional
	The count attribute allows the developer fine grained control over event handling upon multiple event occurrences. When an event is thrown for the first time, the catch element with a count of 1 will be executed. Upon the second instance of the same event, the FIA will look for a catch handler with a count value of 2, if one exists, otherwise, it will simply execute the catch handler with the count of 1 again.

shadow variables

_event	The _event shadow variable equates to a string specifying the event name that caused the exception, thereby making it available for the developer to log or submit the resultant exception/error to a database, or to save it to another local variable to get an application ‘error report’.
_message	The _message shadow variable will equate to the value of any user-defined message that is explicitly thrown. Currently, Voxeo has no platform-defined messages for any standard events, such as *error.badfetch* or *error.semantic*, so any caught messages must be user-defined.

parents

children

code samples

<Error count-cond> sample

<?xml version="1.0" encoding="UTF-8"?>

<vxml version = "2.1">

<meta name="author" content="Matthew Henry"/>
<meta name="copyright" content="2005 voxeo corporation"/>
<meta name="maintainer" content="YOUR_EMAIL@HERE.COM"/>

<form id="F1">

<error count="1" cond="false">
<prompt>
this handler will not get filled, as
the condition is set to false
</prompt>
</error>

<error count="1" cond="true">
<prompt> we have caught the first error. </prompt>
<throw event="error.AnotherError"/>
</error>

<error count="2" cond="true">
<prompt> we have now caught the second error. </prompt>
</error>

<block>
<prompt> preparing to throw the error. </prompt>
<throw event="error.MyError"/>
</block>

</form>

</vxml>

<Error-shadowvariables> sample

<?xml version="1.0" encoding="UTF-8"?>

<vxml version = "2.1">

<meta name="author" content="Matthew Henry"/>
<meta name="copyright" content="2005 voxeo corporation"/>
<meta name="maintainer" content="YOUR_EMAIL@HERE.COM"/>

<error>
<prompt>
The message is <value expr="_message"/>
The event is <value expr="_event"/>
</prompt>
</error>

<form id="F1">

<block>
<prompt>
Hey, lets throw an error, what do you say?
</prompt>

<throw event="error.MyError" message="'hey its an error, whoop dee doo'"/>
</block>

</form>

</vxml>

additional links

W3C 2.0 Specification

ACCOUNT LOGIN

ANNOTATIONS: EXISTING POSTS

nargesafshordi

8/27/2007 4:30 AM (EDT)

Hi,
I have an application, and up to an hour ago it was working fine. Now when I call it, I don't hear anything and the debugger gives the error "error.dialog.notstarted" reason="all dialog targets are unavailable".

I don't know what's happened. Can anyone please help ASAP?

voxeojeff

8/27/2007 9:21 AM (EDT)

Hi there,

This was a small glitch in our Staging environment which, once diagnosed, was quickly resolved. Your application should now be functioning properly. :-)

Cheers,

Jeff Menkel
Voxeo Corporation