Cisco Cisco Unified Customer Voice Portal 10.0(1) Notas De La Versión
C
HAPTER
7:
S
TANDARD
A
CTION
E
LEMENTS
P
ROGRAMMING
G
UIDE FOR
C
ISCO
U
NIFIED
CVP
VXML
S
ERVER
AND
C
ISCO
U
NIFIED
C
ALL
S
TUDIO
R
ELEASE
7.0(1)
40
Figure 7-1
The elements in this XML document are:
•
status
– Since the XML API accesses a process that exists in context separate from VXML
Server, there is no automatic way for an error that occurs during the creation of a response to
be caught and handled properly by VXML Server. This tag exists to simulate that process by
containing either the word “success” or a text message describing the error. When anything
but “success” is returned, VXML Server throws an exception using the content of
be caught and handled properly by VXML Server. This tag exists to simulate that process by
containing either the word “success” or a text message describing the error. When anything
but “success” is returned, VXML Server throws an exception using the content of
<status>
as the error message. This way, from the perspective of VXML Server and the application
logs, the result will be the same no matter whether the Java API or the XML API is used. See
the description for the
logs, the result will be the same no matter whether the Java API or the XML API is used. See
the description for the
<error>
tag below as there is some overlap in functionality.
•
error
– This tag reports to VXML Server that an error occurred while executing the standard
action. VXML Server will then throw an exception whose message is contained in the
<error>
tag. This tag acts almost exactly like the
<status>
tag and was introduced later to
allow for consistency across all components. An error listed in this tag takes precedence over
an error message listed in the
an error message listed in the
<status>
tag. The
<status>
tag must still be used to indicate
that the standard action element executed without error by containing the word “success”.