Cisco Cisco Unified Customer Voice Portal 11.0(1) Veröffentlichungshinweis
C
HAPTER
16:
F
ORM
_W
ITH
_C
ONFIRM
E
LEMENT
S
PECIFICATIONS FOR
C
ISCO
U
NIFIED
CVP
VXML
S
ERVER AND
C
ISCO
U
NIFIED
C
ALL
S
TUDIO
64
Name (Label)
Type
Req’d Single
setting
value
Substitution
allowed
Default
Notes
secure_logging
(Secure Logging)
(Secure Logging)
boolean
Yes true
true
false
Whether or not to enable logging of potentially sensitive data of
the Form_With_Confirm element. If set to true, the following
potentially sensitive data of the element will not log: utterance,
interpretation, value, <SLOT_ELEMENT_DATAX>,
nbestUtteranceX, and nbestInterpretationX. Instead, the above
will be logged as the field name appended with the suffix
“_secureLogging” and with the value “*****”, for example
nbestUtterance1_secureLogging,*****.
the Form_With_Confirm element. If set to true, the following
potentially sensitive data of the element will not log: utterance,
interpretation, value, <SLOT_ELEMENT_DATAX>,
nbestUtteranceX, and nbestInterpretationX. Instead, the above
will be logged as the field name appended with the suffix
“_secureLogging” and with the value “*****”, for example
nbestUtterance1_secureLogging,*****.
Notes:
•
VXML 2.0-compliant browsers typically require top-level slot names in the grammar (inline or external) to match the field-level
slot attribute (if it exists) or the field name attribute, in order for the field name variable (and hence the “value” element data) to be
defined. For inline grammars, the Form_With_Confirm element automatically generates the grammar slot name to match the slot
attribute (if available) or the field name. For custom grammars that are referenced from an external source, the application
designer needs to set “
slot attribute (if it exists) or the field name attribute, in order for the field name variable (and hence the “value” element data) to be
defined. For inline grammars, the Form_With_Confirm element automatically generates the grammar slot name to match the slot
attribute (if available) or the field name. For custom grammars that are referenced from an external source, the application
designer needs to set “
Field Name
” and “
Field Slot
” properly based on the slot name returned by the grammar.
•
If a grammar returns different slots for different inputs or multiple slots per utterance, there are two ways to configure the
Form_With_Confirm element to store this data:
Form_With_Confirm element to store this data:
o
Leave the the “
slot_element_data
” setting empty. The Form_With_Confirm element will create element data named
“nbestInterpretationX” (where X is from 1 to the length of the n-best list) that contains a string that uses delimiters “+” and “:”
to separate the multiple slot names from their values. For example: “+Slot1:value1+Slot2:value2...”. A developer would then
need to parse this string in a subsequent element to obtain the different slot name and value pairs.
to separate the multiple slot names from their values. For example: “+Slot1:value1+Slot2:value2...”. A developer would then
need to parse this string in a subsequent element to obtain the different slot name and value pairs.
o
Configure the “
slot_element_data
” setting with the names for all the slots that can be returned. The Form_With_Confirm
element will create a new set of n-best element data to store the recognition results for each slot listed in that setting. The
element data will be named as <SLOT_ELEMENT_DATAX> (where “SLOT_ELEMENT_DATA” is a string identical to the
setting value and X is from 1 to the length of the n-best list). For example, if “
element data will be named as <SLOT_ELEMENT_DATAX> (where “SLOT_ELEMENT_DATA” is a string identical to the
setting value and X is from 1 to the length of the n-best list). For example, if “
slot_element_data
” had two values “city”
and “state” and there are three n-best results triggered, then six element data in the names of “city1”, “city2”, “city3”, “state1”,
“state2”, and “state3” will be created to store each of the n-best values for the “city” and “state” slots. Note that if n-best
processing is disabled by setting the maxnbest setting to 1, then only one interpretation result will be returned per
recognition and thereby only one element data per slot (“city1” and “state1”) will be created.
“state2”, and “state3” will be created to store each of the n-best values for the “city” and “state” slots. Note that if n-best
processing is disabled by setting the maxnbest setting to 1, then only one interpretation result will be returned per
recognition and thereby only one element data per slot (“city1” and “state1”) will be created.