Cisco Cisco Unified Customer Voice Portal 10.5(1) ユーザーガイド

C

HAPTER 

3:

 

C

ISCO 

U

NIFIED 

CVP

 

W

ORKSPACE

 

 

V

OICE

XML

 

S

TUDIO 

U

SER 

G

UIDE 

 

 

 

FOR 

C

ISCO 

U

NIFIED 

C

USTOMER 

V

OICE 

P

ORTAL

 

 

 

 

 

56

A configurable action element is rendered as a parallelogram. 

 

Even the simplest voice applications require some level of decision-making during the call flow. 
These “crossroads” are encapsulated in Decision elements. 

Encapsulates business logic that makes decisions with at 
least two exit states. 

A Decision element is like a traffic cop, redirecting the flow of calls according to built-in 
business rules. Examples of business rules include decisions such as whether to play an ad to a 
caller, which of five different payment plans to offer to the caller, or whether to transfer a caller 
to an agent or hang up. 

The results of a Decision element are represented as exit states. Although many decisions are 
Boolean in nature, (e.g., has the caller registered? or  is the caller new to the application?), 
Decision elements can have as many exit states as desired, as long as at least two are specified. 

The configuration for a Decision element contains two components: settings and variables. 
Additionally, the Java class that defines the configurable decision sets the exit states it can 
return. The designer must map each exit state to another call flow component to handle its 
consequences. 

 

A configurable Decision element is rendered as a diamond. 

 

Almost all voice applications must utilize a number of dialogs with the caller, playing audio 
files, interpreting speech utterances, capturing data entered by the user, etc. The more these 
dialogs can be contained in discrete components, the more they can be reused in a single 
application or across multiple applications. These dialog components are encapsulated in Voice 
elements. 

A reusable, VoiceXML-producing dialog with a fixed or