Lucent Technologies CentreVu Call Management System Custom Reports Manual

							  Completing Your Custom Report CentreVu CMS Custom Reports
Highlighting Fields5-3
Select any you wish:
lReverse 
videoThis setting causes brightness/color settings for text 
and background to be reversed. For example, for an 
amber monochrome terminal, reverse video makes 
the background amber and the text/data black. For a 
color terminal set for white text on blue background, 
reverse video makes the background white and the 
text blue.
The brightness and blinking options also affect the 
display of reverse video.
lUnderlineThis setting draws a line under any text/data in the 
defined area. If you also select “Reverse video, the 
underline color/brightness is reversed.
Text color (for color terminals only):
lDefaultThis setting displays text in the color set in the 
Options: Color window, which you access via 
.
lSpecific 
colorThis setting assigns to the text one of the eight 
colors displayed at the bottom of the window. If you 
select this option, you must enter the number of the 
color in the associated field you want.
Background color (for color terminals only):
lDefaultThis setting displays the background in the color set 
in the Options: Color window, which you access via 
.
lSpecific 
colorThis setting assigns to the background one of the 
eight colors displayed at the bottom of the window. If 
you select this option, you must enter, in the 
associated field, the number of the color you want.
5.Select the Modify action list 
option.®The Add Highlights window 
disappears.
Commands
Commands
NoteFor some color terminals, dim or bright settings may affect 
the colors selected. 
						

							  Completing Your Custom Report CentreVu CMS Custom Reports
Defining Stationary (No-Scroll) Areas5-4
Defining Stationary (No-Scroll) Areas5
Many standard reports are bigger than the available space on your terminal. 
As a result, when you display the report on your terminal, you must scroll the 
window to see all the data, either down or to the side. However, you will 
notice that some report text or data fields do not move. These stationary, or 
no-scroll, parts of the report normally are column headers, column totals, and 
row identifiers.
In the following report illustration, the shaded areas are no-scroll areas.
Figure 5-2:  Sample Non-Scroll Areas
No-Scroll areas apply only to reports that you are viewing on your terminal. If 
you display the report on your terminal, almost half of the right side of the 
report is hidden from view. Thus, you have to scroll to the right and data on 
the left disappears off the left side of the window. But while you scroll the 
data, the agent on the left remain in place so you always know what agent 
the data is for.
And if you have over 20 agents listed in the report in Figure 5-2
, some rows 
of data at the bottom will be hidden. Thus, you have to scroll down to see the 
rows of data past 20 agents. Meanwhile, data at the top scrolls off the top of 
the window. But the report title, the column headers, and the Totals: row 
stay in place. 
						

							  Completing Your Custom Report CentreVu CMS Custom Reports
Defining Stationary (No-Scroll) Areas5-5
In your custom report, you may wish to assign areas as no-scroll areas. You 
can assign one no-scroll area on the left side of the report and one no-scroll 
area at the top of the report. To define no-scroll areas, use the following 
steps:
1.On the Screen Painter, select 
Upper/left no-scroll.®
The cursor returns to the upper 
left corner of the report. The 
following message appears on 
the status line:
 Move the 
cursor down and right. 
Press RETURN when 
finished.
2.To define a no-scroll area at the 
top, move the cursor down the 
desired number of lines. To 
define a no-scroll area on the left, 
move the cursor to the right.®
CentreVu CMS highlights the 
no-scroll area as you move the 
cursor.
3.Press   to save the no-scroll 
area.Return 
						

							  Completing Your Custom Report CentreVu CMS Custom Reports
Defining Stationary (No-Scroll) Areas5-6
Changing a 
No-Scroll Area
51.On the Screen Painter, select 
Upper/left no-scroll.®The cursor returns to a 
position at the edge of the top 
and/or left no-scroll areas. 
The following message 
appears on the status line:
 
Move the cursor down 
and right. Press 
RETURN when finished.
2.To change a no-scroll area at the 
top, move the cursor up or down 
the desired number of lines. To 
change a no-scroll area on the 
left, move the cursor to the right 
or left.®
As you move the cursor, 
CentreVu CMS highlights the 
no-scroll area that you add or 
removes the highlight for the 
no-scroll area you delete.
3Press   to save your 
changes.Return 
						

							  Completing Your Custom Report CentreVu CMS Custom Reports
Saving the Report Design5-7
Saving the Report Design5
Before you exit the Screen Painter, you must save your report design. If you 
do not save the design, all the work you did since accessing the Screen 
Painter will be lost, including any work you did with secondary windows. You 
must save the design, even if you successfully test it with the Test design 
action list option.
You can save a design that does not test successfully because there are 
errors. Do not run a report design until you have corrected any errors and it 
tests successfully.
To save your report design, do the following:
If 
CentreVu CMS displays errors, do the following:
lNote the errors
lPress the   SLK
lFix the errors on the Screen Painter
lRepeat Step 1. 1.On the Screen Painter, select 
Save design.®Successful 
may appear on the 
Screen Painter status line.
If you did not define all necessary 
elements of the design, the Save 
Design window appears with a list 
of errors.
When there are errors in the design, certain items may be deleted from 
the design and the next time the design is read into the screen painter, 
these elements will not appear.
2.After you save your design, you can continue working on the design, 
test it, or exit the Screen Painter and continue working on the design at 
a later time.
Exit
NoteIf you exit the Screen Painter without first fixing errors found 
in the Save Design window, then the report items associated 
with the errors will be deleted from the Screen Painter. 
						

							  Completing Your Custom Report CentreVu CMS Custom Reports
Testing the Report Design5-8
Testing the Report Design5
Instead of running a report and having it fail because you had errors in your 
design, you can test the design directly from the Screen Painter. Testing your 
report design regularly can save you time.
Use the following steps to test a report design:
Figure 5-3:  Sample Test Design Window - Phase One Errors 1.On the Screen Painter, select 
Test design.®
If your design has Phase One 
errors, a window (Figure 5-3
) 
listing those errors appears. See 
the following section, “Te s t  
Design Error Messages for a 
description of these errors. If 
your design has no Phase One 
errors, the Test Design window 
(Figure 5-4
) appears with a 
facsimile of the Report Input 
window. 
						

							  Completing Your Custom Report CentreVu CMS Custom Reports
Testing the Report Design5-9
Figure 5-4:  Sample Test Design Input Window
Figure 5-5:  Sample Test Design Input Window
2.Complete the fields on the 
Report Input window, and select 
Test select.®A list of the row search 
conditions appears 
(Figure 5-5
), with a list of any 
Phase Two errors. See 
Te s t  
Design Error Messages, for a 
description of these errors.
NoteIf you had Phase One 
errors, fix the errors 
indicated, and go back to 
Step 1.If you have no errors No 
errors found 
appears in the 
window.  
						

							  Completing Your Custom Report CentreVu CMS Custom Reports
Test Design Error Messages5-10
If you have no errors, press the   SLK and continue with your design, or 
save the design and exit the Screen Painter.
Test Design Error Messages5
Test design error messages are divided into three categories:
lPhase 1 Error Messages (detected before the sample input screen 
appears)
lPhase 2 Historical Error Messages (require the sample input before 
occurring)
lPhase 2 Real-Time Error Messages (require the sample input before 
occurring).
Phase 1 Error 
Messages
5
This section contains Phase 1 error messages. Table 5-1 lists the messages 
alphabetically, and includes a cause and a recommended solution for each 
message. 3.If you have errors, then do the following:
lNote the errors
lPress the   SLK
lFix any errors
lSelect Test design again
lRepeat Steps 1 and 2.
Exit
NoteFor real-time reports the link to the switch must be up for the 
current ACD, and there must be data for the particular item you 
are selecting, such as Split 5.
Exit
Table 5-1:  Phase 1 Error Messages 
Message:$ not defined
Cause:The “where” clause contains a variable that is not defined.
Solution:Define the variable using the define input action or remove 
the variable from the row search criteria.
Message:Cannot mix aggregates and nonaggregates in 
the select 
						

							  Completing Your Custom Report CentreVu CMS Custom Reports
Test Design Error Messages5-11
Table 5-1: Phase 1 Error Messages (Contd) Cause:You cannot specify both aggregate columns and 
nonaggregate columns in the same select for real-time 
reports.
Solution:Create two identical row search conditions and apply one to 
the aggregate columns and one to the nonaggregate 
columns.
Message:Cannot use the SYN function for order by
Cause:You cannot use a synonym to sort the output.
Solution:Remove the SYN aggregate from the Order by field.
Message:CMS system error - Check the error log
Cause:A 
CentreVu CMS system error occurred while the select 
executed. The error should be recorded in the error log.
Solution:Check the error in the error log to initiate corrective action. Table 5-1:  Phase 1 Error Messages  — 
Continued
CautionIf you run a report that merges data from two tables 
(particularly tables with large amounts of data) into a 
single field and your Select rows where 
statement is not specific enough, you may get this error 
message. The specific cause may be that the number 
of selected rows is very large, and 
CentreVu CMS 
does not have enough space to create temporary files. 
If this is the case, you should add additional “where” 
clauses to the row search criteria.
Message:CMS system error - Data collection off
Cause:
CentreVu CMS cannot test the row search criteria while 
data collection is off.
Solution:Turn data collection on and rerun test of report design.
Message:CMS system error - Too much data retrieved - 
try a more restrictive search
Cause:Too much data was retrieved with the given row search 
criteria.
Solution:Add more conditions to the row search criteria so that fewer 
rows are retrieved. 
						

							  Completing Your Custom Report CentreVu CMS Custom Reports
Test Design Error Messages5-12
Message:CMS system error - Updating translations
Cause:
CentreVu CMS cannot test the row search criteria while 
CentreVu CMS is receiving the set of configuration data 
from the switch.
Solution:Wait until configuration data has been sent. Then rerun the 
test of report design.