Cisco Cisco Customer Voice Portal 8.0(1) User Guide

As with any other component that produces VoiceXML, the hotevent utilizes the VFCs and
therefore can only be constructed with the Java API.

Say It Smart Plugins

In VXML Server, developers can create their own Say It Smart plugins. Similar to custom
elements, Say it Smart plugins are pre-built Java classes that when deployed in the Builder for
Call Studio can be used as a new Say It Smart type. As with custom elements, the level of
integration required with the Unified CVP software restricts the creation of Say It Smart plugins
to the Java API.

Custom Say It Smart plugins can be constructed to read back formatted data not handled by
Unified CVP Say It Smart plugins, such as spelling playback or reading the name of an airport
from its three-digit code. Plugins can also be created to extend the functionality of existing
plugins, such as adding new output formats to play the information in another language. For
example, a plugin can define a new output format for the Unified CVP Date Say It Smart plugin
that reads back dates in Spanish.

Refer to the 

 (http://www.cisco.com/en/US/products/sw/custcosw/ps1006/

products_programming_reference_guides_list.html) for a full description of the process of
building custom Say It Smart plugins.

Start and End of Application Actions

Unified CVP provides mechanisms to execute some code when an application is launched or
shut down. A start of application action is run when the VXML Server web application archive
(WAR) starts up (which occurs when the application server first starts up or the application
server reloads the WAR), or the application is updated. An end of application action is run when
the application is updated, released, or the web application is shut down (which occurs if the
application server reloads or shuts down the web application or the application server itself is
shut down).

The purpose of the start of application action is typically to set up global data or application
data that would be accessed by components within the callflow. Since global and application
data’s lifetime is the lifetime of the application and they can contain Java objects, the start of
application action could even set up persistent database connections or other communications
to external systems that would remain connected as long as the application were running.

Note: Should an error occur within the start of application class, the application deployment
will continue unchanged. The designer can specify that an error in a particular start of application
class should stop the application deployment. This would be done if the class performs mandatory
tasks that are necessary for the application to run correctly.

The purpose of the end of application action would be to clean up any data, database connections,
and so on. that would no longer be needed once the application is shut down.

User Guide for Cisco Unified CVP VXML Server and Cisco Unified Call Studio Release 8.0(1)