Define The Tables For Calculation Names; Justify Data In The Field; Define The Field Format - Avaya Call Management System Custom Reports

Define the tables for calculation names

Enter a table name in the Table for calculations field only if you entered a
calculation name in the Select field. The table name tells CMS in what table to look for
the database items in the calculation.
Note:
For example, look at the following entries:
Select: AVG_POS_STAFF
Table for calculation: hsplit
These entries mean "Take the calculation defined in the Dictionary subsystem for
<AVG_POS_STAFF>, which is I_STAFFTIME/(INTERVAL*60) , and apply the hsplit
table name to the database items." In effect, the two fields make the calculation
hsplit.I_STAFFTIME/(hsplit.INTERVAL*60) .

Justify data in the field

Select, from the Justification list, the way you want CMS to line up data when the
data is displayed in the field. Normally, numerical data is right-justified so that the right
hand side lines up in a column. Names are normally left-justified so that the first character
of each name is lined up. However, you may choose any of the three options for any type
of data.

Define the field format

Enter an x to select an item in the Field Format list. You must also complete the field
associated with the list item.
The format type and the format you specify in the associated field tell CMS how to display
the values it finds for the field. However, the format you select depends on the type of data
CMS will display. The format options are as follows:
Number
Select Number if the field will display a number of events, an average, or a percentage.
You must also specify a number of decimal places for the field. Enter 0 if you do not need
decimal places displayed. If the field's expression were ACDCALLS , you would select
Number and enter 0 in the field. However, if the field expression were to generate an
average, such as the average staffed positions per interval,
I_STAFFTIME/(INTERVAL*60) , you may want to include decimal places.
The Table for calculations field is necessary because you cannot
append a table name to a calculation name in the Select field.
Defining report fields
Issue 3.0 May 2002 75