Cisco Cisco E-Mail Manager Unity Integration Option User Guide
Chapter 2 Introduction to Report Templates
Planning a Custom Report Template
2-6
Template Design Guide Using InfoMaker for Cisco ICM/IPCC Enterprise & Hosted Editions, Release 7.0(0)
Planning a Custom Report Template
Whether you create a new custom template “from scratch” (as explained in
Chapter 3) or you create a custom template by modifying an existing template (as
explained in Chapter 4), first consider the following:
Chapter 3) or you create a custom template by modifying an existing template (as
explained in Chapter 4), first consider the following:
What is the reporting category for the template?
What entity do you want to target (for example: Agent by Agent, Call Types,
Peripheral services)?
Peripheral services)?
The reporting category determines the template’s Webview report type, and
consequently the menu where it appears in the WebView interface, the report
parameters passed to it, and the template library in which it will be stored.
consequently the menu where it appears in the WebView interface, the report
parameters passed to it, and the template library in which it will be stored.
What presentation style do you want for the template: graph or table?
ICM/IPCC templates can use either a tabular (text) or graph (graphical)
presentation format.
presentation format.
What data is to appear in the template?
Which database tables and columns do you want to include in the template?
For information on ICM databases, refer to the Database Schema Handbook for
Cisco ICM/IPCC Enterprise & Hosted Editions , Release 7.0(0) and the Schema
Help available from the Cisco Admin Workstation program group.
Cisco ICM/IPCC Enterprise & Hosted Editions , Release 7.0(0) and the Schema
Help available from the Cisco Admin Workstation program group.
What arguments does the template require to retrieve data?
WebView users are prompted to specify certain data retrieval parameters when
launching a report template:
launching a report template:
•
Real-time reports always provide one argument—a list of IDs that represent
the entities listed in your report. These are the items the user selects in
WebView.
the entities listed in your report. These are the items the user selects in
WebView.
•
Historical reports always provide three arguments—a list of IDs and also
the start date and the end date for the period of time represented in your
report.
the start date and the end date for the period of time represented in your
report.