Manual

or
AppName.*.*.SESSION:Varname
Note: This syntax is used to indicate session variables.
A semicolon (;) should be used to separate each item in a lter. For example, ElementA ;
ElementB is valid.
A single wildcard (*) can be specied anywhere within the application name, element type,
element name, or eld name.
Element types, element names, and eld names can contain alphanumeric characters,
underscores, and a space character.
An application name can contain alphanumeric characters and underscores, but the space
character is not allowed. For example, A_aa.B_bb.*C_cc_DD.E_ee_F* is valid.
Examples of VoiceXML Filter Wildcard Matching
The table below provides examples of VoiceXML lter wildcard matching.
Table 8: Examples of VoiceXML Filter Wildcard Matching
Matches all voice elements in MyApplicationMyApplication.Voice.*.*
Matches all Voice elements in all applications.*.Voice.*.*
Matches all elds in MyApplication that start with the string
var.
MyApplication.*.*.var*
Matches all elds in MyApplication that end with 3.MyApplication.*.*.*3
Matches the Company session variable in MyApplication.MyApplication.*.*.SESSION:Company
Examples of Inclusive and Exclusive VoiceXML Filters for Reporting
The table below provides examples of some different combinations of Inclusive and Exclusive
lters and the resulting data that the VXML Server feeds to the Reporting Server.
Table 9: Examples of Inclusive and Exclusive VoiceXML Filters for Reporting
Data the VXML Server Feeds To the
Reporting Server
Exclusive FilterInclusive Filter
All Application1 dataNoneApplication1.*.*.*
All Application1 data, except Element1
and Element2
*.*.Element1.*;
*.*.Element2.*
Application1.*.*.*
Reporting Guide for Cisco Unified Customer Voice Portal Release 4.1(1)
49
Chapter 4: Configuring the VXML Server for Reporting
Editing a VXML Server in the Operations Console