Cisco Cisco Customer Voice Portal 8.0(1)

Page of 132
or
AppName.*.*.SESSION:Varname
Note: 
This syntax is used to indicate session variables.
A semicolon (;) should be used to separate each item in a filter. For example, 
ElementA ;
ElementB
 is valid.
A single wildcard (*) can be specified anywhere within the application name, element type,
element name, or field name.
Element types, element names, and field 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 VXML Filter Wildcard Matching
The table below provides examples of VXML filter wildcard matching.
Table 2: Examples of VXML Filter Wildcard Matching
What It Matches
Filter
Matches all voice elements in MyApplication
MyApplication.voice.*.*
Matches all Voice elements in all applications.
*.voice.*.*
Matches all fields in MyApplication that start with with the
string 
var
.
MyApplication.*.*.var*
Matches all fields in MyApplication that end with 
3
.
MyApplication.*.*.*3
Matches the Company session variable in MyApplication.
MyApplication.*.*.SESSION:Company
Examples of Inclusive and Exclusive VXML Filters for Reporting
The table below provides examples of some different combinations of Inclusive and Exclusive
fi
lters and the resulting data that the VXML Server feeds to the Reporting Server.
Table 3: Examples of Inclusive and Exclusive VXML Filters for Reporting
Data the VXML Server Feeds To the
Reporting Server
Exclusive Filter
Inclusive Filter
All Application1 data
None
Application1.*.*.*
All Application1 data, except Element1
and Element2
*.*.Element1.*;
*.*.Element2.*
Application1.*.*.*
Reporting Guide for Cisco Unified Customer Voice Portal Release 8.0(1)
113
Chapter 6: Reporting Best Practices
Inclusive and Exclusive VXML Filters for Reporting