Tasks To Create A Custom Report - Avaya Call Management System Custom Reports

Tasks to create a custom report

There are 14 tasks you need to complete to create a custom report. If you consistently do
all of these tasks for each report you create, then your reports will run properly and you will
be able to create them efficiently. The 14 tasks are:
1. Defining a report's name, access, type, and option
Define the name that you use both to run the report and to access the report design if
you want to change the design. Define access to whether other users can run the
report and copy the report's design to create their own custom reports. Define the type
as either real-time or historical.
2. Navigating Screen Painter
Access Screen Painter so that you can design the report.
3. Copying an existing report design
Copy an existing design so that you start with existing report headings, data fields,
bars, and other report features. While this is an optional step, it saves you a lot of time
and trouble by copying and modifying an existing report design. Both standard and
custom report designs can be copied.
4. Editing a report with blocks
Edit a report design using block moves, copies, and deletions. Editing with blocks lets
you rearrange and delete sections of a report design quickly and easily. Block editing is
particularly convenient when you have just copied an existing report design.
5. Entering report text
Enter text to provide headings for the data fields in the report. Entering report text
should be one of the first things you do so that:
If you copy a report design the text of that report will be included. Using the Custom
Reports subsystem, you can modify the text as required.
6. Defining fields for the Report Input window
Define fields for the report input window so that users can run the report using the
parameters they choose (i.e., what split, agent, time, date, and so on, the report
covers).
If you copy a report design, the definition of that report's input window will be included.
You can then modify the input fields as needed.
on page 53
The text provides a skeleton layout for positioning data fields
The text helps you remember what data is supposed to go in the data fields
on page 41
on page 45 (Optional)
on page 48
on page 55
Tasks to create a custom report
on page 31
Issue 3.0 May 2002 17