Cisco Cisco Unified Customer Voice Portal 10.5(1) Release Note
C
HAPTER
2:
Unified CVP
C
OMPONENTS IN
D
ETAIL
U
SER
G
UIDE FOR
C
ISCO
U
NIFIED
CVP
VXML
S
ERVER
AND
C
ISCO
U
NIFIED
C
ALL
S
TUDIO
32
Configurable Elements
Most of the elements in a typical Unified CVP application are pre-built, reusable elements whose
configurations are customized by the application designer. Using a configurable element in a call
flow requires no programming or VoiceXML expertise and since they can encapsulate a lot of
functionality, greatly simplifies and speeds up the application building process. VXML Server
includes dozens of elements that perform common tasks such as collecting a phone number or
sending e-mail. A need may exist, however, for an element with functionality not available in the
default installation. Additionally, while Unified CVP elements have been designed with
configurations that are as flexible as possible, there may be situations where a desired
configuration is not supported or difficult to implement.
configurations are customized by the application designer. Using a configurable element in a call
flow requires no programming or VoiceXML expertise and since they can encapsulate a lot of
functionality, greatly simplifies and speeds up the application building process. VXML Server
includes dozens of elements that perform common tasks such as collecting a phone number or
sending e-mail. A need may exist, however, for an element with functionality not available in the
default installation. Additionally, while Unified CVP elements have been designed with
configurations that are as flexible as possible, there may be situations where a desired
configuration is not supported or difficult to implement.
To satisfy these concerns, a developer can construct custom configurable elements that, once
built, can be used and reused. The developer can design the element to possess as large or as
small a configuration as desired, depending on how flexible it needs to be. Once deployed,
custom elements appear in Builder for Call Studio in the Element Pane and are configured in the
same way as Unified CVP Elements.
built, can be used and reused. The developer can design the element to possess as large or as
small a configuration as desired, depending on how flexible it needs to be. Once deployed,
custom elements appear in Builder for Call Studio in the Element Pane and are configured in the
same way as Unified CVP Elements.
Due to the level of integration with the Unified CVP software required, only the Java API
provides the means for building configurable elements. Using this API, configurable action,
decision, and voice elements can be built. Voice elements, due to the fact that they are
responsible for producing VoiceXML, use an additional Java API, the Voice Foundation Classes
(VFCs). The VFCs are used to abstract the differences between the various voice browsers
supported by Unified CVP. The VFCs follow a design that parallels VoiceXML itself and only a
developer familiar with VoiceXML and the process whereby a voice browser interprets
VoiceXML will be fully suited to utilize the VFCs to build voice elements.
provides the means for building configurable elements. Using this API, configurable action,
decision, and voice elements can be built. Voice elements, due to the fact that they are
responsible for producing VoiceXML, use an additional Java API, the Voice Foundation Classes
(VFCs). The VFCs are used to abstract the differences between the various voice browsers
supported by Unified CVP. The VFCs follow a design that parallels VoiceXML itself and only a
developer familiar with VoiceXML and the process whereby a voice browser interprets
VoiceXML will be fully suited to utilize the VFCs to build voice elements.
The Programming Guide for Cisco Unified CVP VXML Server and Cisco Unified Call Studio
describes the process of building configurable elements including detailing the VFC API for
building voice elements.
describes the process of building configurable elements including detailing the VFC API for
building voice elements.
Standard Action and Decision Elements
Unlike configurable action or decision elements, a standard action or decision element is
designed more as a one-off as they satisfy an application-specific purpose. As a result, standard
action and decision elements do not require configurations.
designed more as a one-off as they satisfy an application-specific purpose. As a result, standard
action and decision elements do not require configurations.
There are many situations where programming effort is required to perform some task specific to
an application. Since the task is very specialized, pre-existing reusable elements are too general
to perform the effort. Additionally, building a configurable element for this purpose would be
overkill since there is little chance it would be needed anywhere but in this application. The
developer would use a standard action or decision element to perform just this task. If the task is
applicable to multiple situations, the developer most likely would put in the extra effort to
construct a configurable, reusable element.
an application. Since the task is very specialized, pre-existing reusable elements are too general
to perform the effort. Additionally, building a configurable element for this purpose would be
overkill since there is little chance it would be needed anywhere but in this application. The
developer would use a standard action or decision element to perform just this task. If the task is
applicable to multiple situations, the developer most likely would put in the extra effort to
construct a configurable, reusable element.