Cisco Cisco Customer Voice Portal 8.0(1) Developer's Guide

Standard Decision Elements

Decision elements apply business logic to decide which exit state to return. A pre-built,
configurable decision element has already defined the business logic and only requires a
configuration to modify its behavior. Standard decision elements, however, are defined by the
developer and have no configuration since they represent decisions specific to an application.
For simple to moderately complex decisions, Unified CVP provides a means of defining decisions
without programming by constructing an XML document (the Unified CVP XML decision
format is described in Chapter 2 of 

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

products_user_guide_list.html)). Should this format prove insufficient, Java or XML APIs are
provided to allow the developer to build the business logic programmatically.

A standard decision element, in addition to the functionality provided all components, is allowed
to create and modify element data.

This chapter contains the following topics:

•

•

Using the Java API

A standard decision element is built in Java by extending the abstract base class

 found in the 

 package (this

package’s name is such due to backwards compatibility considerations). It contains a single
abstract method named 

 that acts as the execution method for the decision element,

and must be implemented by the developer. The method receives two arguments: the name of
the decision element (as a String) and an instance of 

. This class

belongs to the Session API and is used to access session information (See 

 for more on this API). The method expects a String object in return containing the exit state

in the exact format specified in Builder for Call Studio when the standard decision element was
first defined.

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