Cisco Cisco Unified Customer Voice Portal 10.0(1) User Guide
C
HAPTER
2:
U
NIVERSAL
E
DITION
C
OMPONENTS IN
D
ETAIL
U
SER
G
UIDE FOR
C
ISCO
U
NIFIED
C
ALL
S
ERVICES
,
U
NIVERSAL
E
DITION
AND
U
NIFIED
C
ALL
S
TUDIO
30
•
Call Services-Specific
. These components are built to run on Call Services as a whole and
do not apply to a specific call.
Start and End of Application Actions
. To perform tasks when a Call Services
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.
Universal Edition 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 Universal Edition
application. The guidelines for building a VoiceXML insert element are given in this
chapter.
application. The guidelines for building a VoiceXML insert element are given in this
chapter.
Variables
Universal Edition 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.
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 Call Services 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 Call Services. Global data would be reset if the
application server were to be restarted or the Call Services web application archive (WAR) were
to be restarted.
applications. Global data is given a single namespace within Call Services 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 Call Services. Global data would be reset if the
application server were to be restarted or the Call Services web application archive (WAR) were
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.
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 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