Including exceptions data in a custom report
Issue 3.0 May 2002
147
Including exceptions data in a custom report
For historical custom reports only, you can design reports that include exceptions data.
See the Avaya CMS R3V11 Database Items and Calculations (585-780-702) document for
a description of the exceptions tables and the data they contain.
The steps for creating a custom report with exceptions data are almost identical to the
steps for creating any other custom report. As with any other type of data, you must specify
the database items, the tables, the row search conditions, and the report input fields.
However, you cannot copy any standard exceptions report on Screen Painter. The
exceptions reports are not displayed if you select
List all
in the Get Copy of Design
window.
Also, in every exceptions table, the database item EXTYPE stores the types of exceptions
that occurred. However, exception types are stored as numbers, not as character strings. If
you want your report to list the types of exceptions that occurred, the types must be listed
as numbers (see Avaya CMS R3V11 Database Items and Calculations, 585-780-702, for a
description of these numbers). The following table shows an example of a VDN exceptions
report:
VDN exceptions report
If you designed a custom exception report to replicate the standard VDN Exceptions
Report, then the design might be displayed as shown in the following figure:
Custom exceptions report
VDN Exceptions
ACD: burbank
Printed 04/10/93 04:35 PM
Date: 04/09/93
Time
Time
VDN
Vector
Exception
Limit
Threshold
------------------------------------------------------------------------------------------
09:16AM
Catalog Sales
Weekday Sales
Number calls abandoned in vector
20
09:24AM
Catalog Sales
Weekday Sales
Calls in ACD split queue
10
10:02PM
Catalog Sales
Off-hour Sales Calls disconnected
50