Cisco Cisco Customer Voice Portal 8.0(1) Mode D'Emploi

Page de 107
C
HAPTER 
2:
 
V
OICE
XML
 
S
ERVER 
C
OMPONENTS IN 
D
ETAIL
 
 
V
OICE
XML
 
S
ERVER 
U
SER 
G
UIDE 
 
 
 
FOR 
C
ISCO 
U
NIFIED 
C
USTOMER 
V
OICE 
P
ORTAL 
R
ELEASE 
4.0(1) 
 
 
 
 
 
37
   
History
. This information deals with the history of elements visited so far in the call. The 
inputs start with “audium_history_”. 
o
 
audium_history
. This entire content of the element history (including exit states) is 
contained in this variable. The format is [ELEMENT]:[EXITSTATE]|..|[ 
ELEMENT]:[EXITSTATE] where ELEMENT is the name of the element and 
EXITSTATE is the name of the exit state of this element. The order of the element/exit 
state pairs is consistent with the order in which they were visited. This will not appear if 
this insert element is the first element in the call. 
   
Data
. This is the element and session data created so far in the call. 
o
 
audium_[ELEMENT]_[VARNAME]
. This is an element variable where ELEMENT is the 
name of the element and VARNAME is the name of the variable. Note that both the 
element and variable names will have all spaces replaced with underscores. There may be 
no instances of this input if no element variables exist when this insert element is visited. 
For example, the variable “audium_MyElement_the_value” is element data named “the 
value” from the element “MyElement”. 
o
 
audium_session_[VARNAME]
. This is a session variable whose name is VARNAME. 
Note that the variable name will have all spaces replaced with underscores. The value is 
expressed as a string even if the type is not a string (the 
toString()
 method of the Java 
class is called). There may be no instances of this input if no session variables exist when 
this insert element is visited. 
   
User Data
. This element information associated with the caller. It will only appear if the 
application has associated the call with a UID and a user management database has been set 
up for this application. The data will appear in the input exactly as in the database. The inputs 
start with “user_”. 
o
 
user_uid
. This is the UID of the user. 
o
 
user_account_number
. The account number of the user. 
o
 
user_account_pin
. The PIN of the user. 
o
 
user_demographics_name
. The name of the user. 
o
 
user_demographics_birthday
. The birthday of the user. 
o
 
user_demographics_zip_code
. The zipcode of the user. 
o
 
user_demographics_gender
. The gender of the user. 
o
 
user_demographics_social_security
. The social security number of the user. 
o
 
user_demographics_country
. The country of the user. 
o
 
user_demographics_language
. The language of the user. 
o
 
user_demographics_custom1
. The value of the first custom column. 
o
 
user_demographics_custom2
. The value of the second custom column. 
o
 
user_demographics_custom3
. The value of the third custom column.