Cisco Cisco Customer Voice Portal Downloads Guia Do Utilizador
C
HAPTER
2:
V
OICE
XML
S
ERVER
C
OMPONENTS IN
D
ETAIL
V
OICE
XML
S
ERVER
U
SER
G
UIDE
FOR
C
ISCO
U
NIFIED
C
USTOMER
V
OICE
P
ORTAL
R
ELEASE
4.0(1)
17
Component Accessibility
Table 2-1 lists each component and its ability to get and set global, application, session, and
element data.
element data.
Global
Data
Application
Data
Session
Data
Element
Data
Component
Get
Set
Get
Set
Get
Set
Get
Set
Configurable Elements
Yes Yes Yes Yes Yes Yes Yes Yes
Standard Elements
Yes Yes Yes Yes Yes Yes Yes Yes
Dynamic Configurations
Yes Yes Yes Yes Yes Yes Yes Yes
Start and End of Call Actions
Yes Yes Yes Yes Yes Yes Yes Yes
Hotevents
No No No No No No No No
Say It Smart Plugins
No
No
No
No
No
No
No
No
Start and End of Application Actions
Yes Yes Yes Yes No No No No
Loggers
Yes No Yes No Yes No Yes No
On Error Notification
No
No
No
No
Yes
No
No
No
XML
Decisions
No No No No No No No No
VoiceXML Insert Elements
No
No
No
No
Yes Yes Yes Yes
Table 2-1
Notes:
Hotevents, being simply VoiceXML code appearing in the root document, do not have access
to any server-side information.
A Say It Smart Plugin’s sole purpose is to convert a value into a list of audio files and so do
not have a need to access server-side information.
A Logger's sole responsibility is to report or log data and therefore has access to all variables
types but cannot set them.
On Error Notification classes are given the session data that existed at the time the error
occurred.
APIs
To facilitate the development of components requiring programming effort, Unified CVP
provides two application programming interfaces (APIs) for developers to use. The first is a Java
API. The second API involves the use of XML sent via HTTP, thereby allowing components to
be built using programming languages other than Java. Some more complex and tightly
integrated components can be built only through the Java API, though in most other aspects, the
two APIs are functionally identical. The APIs themselves and the process of building
components using either API is fully detailed in the Javadocs published with the software and in
the Programming Guide for Cisco Unified Customer Voice Portal. The two components that do
provides two application programming interfaces (APIs) for developers to use. The first is a Java
API. The second API involves the use of XML sent via HTTP, thereby allowing components to
be built using programming languages other than Java. Some more complex and tightly
integrated components can be built only through the Java API, though in most other aspects, the
two APIs are functionally identical. The APIs themselves and the process of building
components using either API is fully detailed in the Javadocs published with the software and in
the Programming Guide for Cisco Unified Customer Voice Portal. The two components that do