Cisco Cisco Unified Customer Voice Portal 11.0(1) User Guide

Page of 107
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) 
 
 
 
 
 
15
ƒ 
Start and End of Application Actions
. To perform tasks when a Unified CVP 
VoiceXML Server application is loaded and/or shuts down.  
ƒ 
Loggers
. Plugins designed to listen to events that occur within calls to an application 
and log or report them. 
ƒ 
On Error Notification.
 To perform tasks if an error causes the phone call to end 
prematurely. 
   
Built Without Programming
. These components do not require high-level programming effort 
to construct. 
   
XML Decisions.
 Unified CVP provides an XML format for writing simple decisions 
without programming. The exact XML format is detailed in this chapter. 
   
VoiceXML Insert Elements.
 This element is used in situations where the developer wishes 
to incorporate custom VoiceXML content into a Unified CVP application. The guidelines 
for building a VoiceXML insert element are given in this chapter. 
Variables 
Unified CVP offers variables as a mechanism for components to share data with each other, in 
four forms: global data, application data, session data and element data.  
Global Data 
A global data variable is just that, it is globally accessible and modifiable from all calls to all 
applications. Global data is given a single namespace within Unified CVP VoiceXML Server 
that is shared across all calls to all applications. If a component changes global data, that change 
is immediately available to all calls for all applications. Global data can hold any data, including 
a Java object. The lifetime of global data is the lifetime of the VoiceXML Server. Global data 
would be reset if the application server was to be restarted or the Unified CVP VoiceXML 
Server web application archive (WAR) was to be restarted. 
Global data is typically used to store static information that needs to be available to all 
components, no matter which application they reside in. For example, the holiday schedule of a 
company that applies to all applications for that company. 
Application Data 
An application data variable is accessible and modifiable from all calls to a particular 
application. Application data variables from one application cannot be seen by components in 
another application. Each application is given its own namespace to store application data. If a 
component changes application data, that change is immediately available to all other calls to the 
application. Application data can hold any data, including a Java object. The lifetime of 
application data is the lifetime of the application. Application data would be reset if the 
application were updated and would be deleted if the application were released.