Avaya Call Management System Custom Reports page 26

Introduction to Custom Reports
The data that CMS plugs into the report is the data found in the intersection of the selected
database items and rows. Therefore, the report shows data as shown in the following
figure:
Sample custom report 1
Note:
As mentioned earlier, CMS uses indexes to create a structure for storing data. Similarly,
CMS uses these indexes to search for data. Indexes allow CMS to find data much faster
than if data were stored more randomly. Therefore, when you design a custom report, the
rows of data for the report should be defined on the basis of index values. See
fields for the Report Input window
Note:
As another example of how CMS retrieves report data is shown in
design, which is an example of a report design for a custom intrahour interval split report
that lists, by intrahour interval, data for a split in a single day.
26 Avaya CMS Custom Reports
Split: 1
Agent ID:
1001
1002
1003
1004
1005
1006
1008
1010
Actually, when you design a custom report, you normally set up the row
selection so that the users running the report can choose the rows in the
report's input window. For example, to run the report in the previous figure,
you would set up the row selection so users would fill out a Report Input
window that asked them for a Split number. See
Report Input window
The indexes for each standard table are fixed and cannot be changed,
deleted or added to. However, if you define a custom table in the CMS
database via INFORMIX* SQL, you can define any indexes wanted for that
new table.
Current ACD
State Calls
AVAIL 21
AVAIL 19
ACD 15
ACD 9
ACD 11
AUX 20
ACW 18
AVAIL 18
on page 55 .
on page 55.
ACD Average
Time Talk Time
988 47:00
777 40:09
400 26:07
58 6:44
644 58:54
245 12:25
603 33:50
203 11:28
Defining fields for the
Sample 2 custom report
Defining