Defining the data for a custom report
74 Avaya CMS Custom Reports
avg
The avg aggregate function retrieves the average of all values found over the time
frame of the report. Using the sample table shown in the previous figure, if you enter
avg(ACDCALLS)
for a field and run the report for Split 1 for all intervals on 07/02/95,
the value 402.75, which is the average of
399, 400, 394, and 418, are displayed.
count(*)
The
count(*)
expression tells CMS to count the number of rows in a table that match
certain row search conditions (as defined in the Row Search window). For example, if you
want the number of agents in a split that had more than five extension-out calls, the Row
Search window would have a row search statement like:
Select rows where: SPLIT = 1 and
(ACWOAUXOUTCALLS) > 5
This statement means, “Find rows of data where the SPLIT value is
1
and total extension-
out calls, for both ACW and AUX states, is greater than 5." Then, by entering
count(*)
in the
Select:
field, the report field would count the number of rows that match, and
display that number in your report.
Do not append a table name to the beginning of
count(*)
.
count(*)
is always a number of matching rows and makes sense only if you want to track
some specific measure of performance by ACD elements (for example, the number of
agents currently logged into a split, the number of trunks that were occupied for more than
80% of the time, the number of VDNs that had over 30 abandoned calls in an intrahour
interval).
count(*)
allows you to create fields that act as exception counts.
Data from more than one table
A calculation can merge data from more than one table in a report field.
For example, you may want the percentage of a split's ACD calls that an agent handled in
a day. Thus, you can enter a calculation that merges data from the Daily Agent and Daily
Split tables, as in the following example.
dagent.ACDCALLS/dsplit.ACDCALLS
When you merge data from two tables, you must define your row search conditions in a
special way. See
Selecting rows from more than one table
on page 151.
Note:
You cannot use calculation names for a field in which you merge data from
two tables, and you cannot merge data in real-time reports.