|
AppsWatch is a module of the Chroniker Suite that is an availability monitoring and performance testing
solution for critical enterprise-class applications. It accurately assesses the
end user's experience under a variety of real-world scenarios. Its innovative
approach to automation enables you to test any windows-based client application
easily without developing complex scripts. Comprehensive diagnostics and
response time break-downs enable you to isolate the slow or failure point in an
application.
Back to top
Simplify your Testing
With AppsWatch, you don't need to spend days developing complex test scripts.
Simply use ScenarioBuilder to create the scenario using a step-by-step method to capture the sequence of mouse and keyboard actions to simulate user interaction with your application.
With these methods, you can create complex test scenarios in minutes, without
writing a line of code.
Realistic Test
Scenarios
By
simulating users in a real IT environment interacting with your production applications, AppsWatch
creates a test that reflects real user activity, and not just a test
simulation.
Protocol Independent
AppsWatch is a low cost solution that fits your budget constraints. More
importantly, its versatility brings you true value. This is not an application
specific test solution. AppsWatch supports any Windows-based client application
including Citrix Web services,.NET Legacy, JAVA/J2EE, client-server
Back to top
& Terminology
The four components to AppsWatch are Chroniker Base,
ScenarioStations, AppsWatch ScenarioBuilder and Target Applications.
Chroniker AppsWatch Base
The Chroniker Appswatch Base schedules scenario executions for the Scenario Stations at their different locations and stores all their real time and historical performance data. It is integrated into the Chroniker Suite to give you a complete picture of your performance and availability status. AppsWatchBase provides you with performance graphs and reports. And if necessary, it can trigger alarms or run steps when the performance results exceeds your threshold. AppsWatchBase provides you with the tools to gauge user satisfaction with any target application.
ScenarioStation
A ScenarioStation is a dedicated workstation which records and executes scenarios that monitor performance of your applications. ScenarioStations send response time and other data to the AppsWatch base. The Scenario Station emulates a user interacting with target application and should be located where you want to monitor response time data from.
AppsWatch Scenario Builder
The Scenario Builder is the component of the ScenarioStation that allows you to build your scenario step-by-step. All the command lines are listed in an easy to read format and you can later go back and modify or add actions within the scenario.
The Scenario Builder allows you to break up the scenario into transactions so you can see response time of portions of the scenario and know exactly where the failure or slowness occurs when the application is not’t performing as it should.
Target Applications
A target application is the application you wish to test. AppsWatch is
protocol independent and can test any Windows-based client including Java,
J2EE,.Net, Citrix, Web Services, and Client-Server applications. If the target application is Client-Server, the client installation must be installed on the scenario station.
Transactions
A Transaction is a section of the scenario (consisting of a sequence of actions) to be measure for performance (response time). Transactions lets you know the exact point where the failure or slowness occurs when running your target application. Within Scenario Builder, you can identify portions of the scenario or recording by measuring the execution time
between the beginning and the end of the Transaction.
Scenario File
The Scenario file is a simple text file created with AppsWatch Scenario Builder. A Scenario File contains all actions that a typical user may take during an interaction with the target application.
Response Time
Response time is the unit used to measure the performance the entire scenario, or Transactions within a scenario. The system calculates the response time from taking the end point of your Scenario or Transaction and subtracting it from the beginning point of your respective Scenario or Transaction respectively. ( “End LoginTransaction ” – “Begin LoginTransaction").
Scenario
A Scenario is the sum of all specified actions within the scenario.
Bitmap
A bitmap is the graphical object on the screen that needs to be found before the next action is executed.
Command
A more detailed description of the action to be performed
Line
A single task (or action) to be performed during a scenario.
Back to top
To run AppsWatch, you must have at least one ScenarioStation
installed to run the scenarios which will eventually report the response time back to Chroniker.
ScenarioStations must be installed on dedicated Windows machines that represent a typical user workstation in your environment. Below are the steps required to
setting up ScenarioStations and Chroniker.
a) The bundled AppsWatch package includes one ScenarioStation.
b)
If you have any of the other packages OR
If you want to monitor your application scenarios from
remote ScenarioStations, download a copy of the ScenarioStation software from http://www.nrgglobal.com/downloads/scenariostation_downloads.php
•
Enter the Chroniker host name when prompted
•
Follow the steps in the Installer wizard
*Note: the Scenario Station must be installed on a Windows workstation (i.e. Windows XP), not on a server.
Configuring the ScenarioStation software
To modify the configuration after installing the product, open ScenarioBuilder.
- Go to the Top-Menu and click on Tools -> Options.
- Click on the Station tab to modify the HostName and/or the Listener Port for the ScenarioStation.
- Click to the AppsWatch Base tab to modify the HostName, Listener Port, or to select/deselect SSL as a communication protocol to reach the Chroniker Base.
Licensing
The Chroniker AppsWatch Base manages licensing for the ScenarioStation. ScenarioStations must be registered in the AppsWatch base in order for the scenarios to be executed.
The number of ScenarioStations allowed to be registered on AppsWatch base is limited by the number of licenses you have purchased. For example, if you purchased 10 AppsWatch Licenses, the maximum number of registered ScenarioStations is 10.
This is an improvement in AppsWatch licensing giving you the flexibility to add/remove/change Scenario Stations without having to "hardcode" the licenses into the ScenarioStations.
Back to top
Starting the Scenario Builder Application
• In Start menu, Programs, go to Chroniker ->
ScenarioStation. Click on Scenario Builder and a window will open.
Back to top
Adding Actions
To Create a Scenario
• On the Left-Pane, click on the action you want to add to your scenario. Some actions will require you to enter additional information such as location of the program you want to invoke, text you want to enter, expressions you want to insert into your scenario, etc. Please see Action Objects Reference below for details.
• The action you have chosen will appear on the right-pane as a new line. Actions are automatically added sequentially unless specified by the user. To insert an action between existing lines, highlight the line immediately above the location where the new action is to be inserted. Then go to the left-pane and select the action you want to add. Once the selection is made, the new action will now appear underneath the highlighted action on the right-pane.
Deleting Actions
• On the right-pane, right-click on the action you want to delete, and then choose delete.
Modifying Actions
• On the right-pane, simply double click on a action and a window opens. Not all actions can be modified.
• Modify the parameters and click OK to save the changes, or hit cancel.
Changing the Sequence of Actions
• On the right-pane, right-click on the action you want to move and click on either  MOVE UP or  MOVE DOWN.
• Repeat until you have moved it to the desired location.
• You can also use the UP or DOWN arrows located on the toolbar menu by first highlighting the event, then clicking UP or DOWN until you have moved it to the desired location.
Back to top
Playback the Scenario
• From the top-menu, click on the  Play Scenario button (arrow pointing to the right). This plays the scenario from the action you have highlighted on the right-pane. To play the entire scenario, make sure you highlight the first line.
• To playback only a single action, click on the  Play Selected line only button (arrow pointing to a circle to the right)
To Save the Scenario
• Go to File ->Save , and type the name of the scenario file or
• Save the scenario (Default location: Chroniker/
ScenarioStation/bin) .
Register the Scenario
• Once all the actions are defined and the scenario is successfully played back, click on the  Register scenario with Chroniker Base icon from the top-menu.
• A window will appear with a status of your registration to the Chroniker Base.
• Once registered, you can now manage these scenarios in
Chroniker. The scenario should run regularly at the frequency already defined
in ScenarioStation. In Scenarios page in Chroniker , you can also click on the  icon
corresponding to the scenario you just registered to run that scenario
immediately.
Back to top
 Launch Application allows you to open the target application you want to test in your scenario.
 Close Application allows you to close the target application at the end of your test. This is a very important step because multiple applications may run concurrently on the ScenarioStation if this step is not taken.
 Play Scenario
Play Scenario plays an Station scenario file. This feature allows you to nest unlimited number of scenarios.
•From the Scenario Station interface, go to the left-pane and click on the Play Scenario action
•Select the scenario file you wish to include (file extension is .csc) from the dropdown menu and click on the OK button.
 Adding Windows actions
• On the Left-Pane, go to Windows and select a windows control object. For most Windows actions (except minimize all windows and close all windows), a window appears asking you to select the window object you are about to perform the action to.
• You may also use the drag-tool to select the window on your desktop. Simply click and hold the left-click button on the drag-tool and drag it to the open window on your desktop, then let go of the left-click button. Your selected window will be highlighted.
• Once you have selected the window object, type the name for the window object and click OK to apply.
• Here is a list of Windows related actions:
 Wait for Windows to Appear allows time for the the target application's window to appear before proceeding with the next event.
• Wait for Windows to Disappear allows time for the time for the target application to close before proceeding with the next event.
• Other Windows controls include:
- Move Window
- Resize Window
- Hide Window
- Restore Window
- Maximize Window
- Minimize Window
- Close Window
- Focus Window
- Minimize All Windows
- Close All Window
 Adding BitMap Checks
Please refer to Scenarios with BitMap Checks section below.
 Adding IF Expressions
• If Expressions allow you to setup an If-Then-Else condition on your scenario.
• On the Left-Pane, goto IF and choose IF expressions. When you click on it, a window appears.
• From the pull down menu, specify the line that you want the condition to apply. Then choose either Succeeds or Fails as a condition, then choose the line number you want to skip to. From the Else pull-down menu, choose the line you want to skip to if the previous conditions are not met.
• Click OK to save your changes. On the right-pane, you should see the details of your expression in parentheses.
• To modify the expression, simply double-click on the event and a window will open allowing you to make your changes.
• Goto expression allows you to skip to a different line without having to meet any conditions. From the left-pane, go to IF and click on Goto.
• A window appears with a pull-down menu. Choose the line you want to skip to and click OK.
 Adding Mouse and Keyboard Inputs
Mouse Inputs
•With mouse inputs, you can specify the action you want the mouse to take without having to record the actual mouse movement. Below is a list of objects you can chose to represent your mouse inputs:
 Mouse Move - when you click on this object, you are asked to move the mouse to the exact coordinates where you want your mouse to be before the next event takes place. To do so, just move your mouse to the desired location and press Shift+F10. The mouse coordinates will appear in the X: and Y: fields. Click OK to capture the location. - Mouse Left Button Click
- Mouse Left Button DoubleClick
- Mouse Left Button Down
- Mouse Left Button Up
- Mouse Middle Button Click
- Mouse Middle Button DoubleClick
- Mouse Middle Button Down
- Mouse Middle Button Up
- Mouse Right Button Click
- Mouse Right Button DoubleClick
- Mouse Right Button Down
- Mouse Right Button Up
Keyboard Inputs
•Keyboard inputs allow you to enter text into fields or any other area that requires inputs without having to record keystrokes. Below is a list of objects you can choose for your keyboard inputs:
 Keyboard Type Text - when you click on this object, a window opens asking you to type the text to be inputted into the scenario during playback. Once you have entered the text, click OK. On the right-pane, you will see the specified text in parentheses.  Keyboard Key Press - when you click on this object, a window opens with a pull down menu. Specify the key you want to be pressed from the pull-down menu which contain many of the keys available on a standard keyboard.  Keyboard Key Down- this is most useful when you need to click and keep the key pressed down. For example, if you need to invoke ctrl+alt+del action, you would specify a keyboard key down event for the ctrl key, another one for the alt key, and also specify a keyboard key press for the del key.  Keyboard Key Up- To release the key down, the key up event must be specified for each keyboard key down event. For example, if you have specified to key down on the ctrl+alt+del keys, then you must specify to key up for the ctrl key and another one for the alt key.
 Adding Wait periods
• Wait periods can be added to give the system enough time to execute the command properly.
• On the left-pane, go to Misc and click on Wait.
• The wait event automatically appears on the right-pane. By default, the wait time is 100 milliseconds.
• You may add more time by adding more wait time events or by double-clicking on the line and selecting a more appropriate wait time.
 Adding Transactions
Please refer to Scenarios with Transactions section below.
Back to top
•Transactions allow you to identify the portion of the scenario for purpose of measuring the performance.
• To mark the beginning of the Transaction, go to the right-pane and highlight the area were you want to insert the beginning of the Transaction.
• On the left-pane, go to Misc and click on Transaction. When the window opens, type the name of the Transaction and click OK.
•To mark the end of the Transaction, go to the right-pane and highlight the area where you want to denote the end of the Transaction.
• From the left-pane, go to Misc and click on Transaction. The same window opens, but this time, you will see a list of Transactions previously defined to start. Choose the appropriate Transaction to end and click OK.
Back to top
Bitmap Checks are a crucial component that ensures that a scenario has been properly executed. When a bitmap check is inserted into the scenario, the scenario will not continue until the image specified in the scenario has appeared somewhere on the screen.
Adding BitMap Checks
• On the Left-Pane, go to Bitmaps and click on Find Bitmap.
• A message appears with instructions on how to capture the bitmap. Click OK to start the capture process.
• A Capture Bitmap window opens with the following elements:
(Note: to capture the bitmap image you must press Shift+F10, not the OK button on the window.)
- The box on top shows the actual image that is to be captured when you press Shift+ F10.
- Bitmap Size allows you to increase or decrease the size of the bitmap to better fit the bitmap you are trying to capture.
- Threshold allows you to set the priority level given to the center of the image. For example, the lower the threshold, the lower importance the middle of the image will have. This means the image during playback has to be as sharp as possible for this action to be successful. On the other hand, if the threshold is higher,more importance is given to the center of the image while the peripheral areas take less of a priority.
- Name is where you can specify the name of the bitmap to be referenced from the ScenarioBuilder.
- Cursor Position allows you to specify the position of the cursor after the scenario has found the bitmap. This allows the next action to start from this position.
• Once you have finished capturing your bitmap, press OK to bring the captured image into the scenario.
Back to top
- My Scenario keeps failing at a certain bitmap image:
- Check to see that your bitmap does not change color or style on mouse over. When using Bitmap actions on the left pane to capture bitmaps,
make sure the bitmap image and the captured image are the same.
-
When using WaitForBitmapAppear action, for example, and the image changes on mouse over:
double click on WaitForBitmapAppear action and capture the bitmap as below. Position the mouse under the "Products" image on the website
so it will appear at the top of the captured bitmap window and set the cursor position to be "Top Center". This way you did not mouse over the image and captured
the exact image as you would look at it before clicking on it, and by positioning the mouse to be top center, the mouse will go over on the "Products" image:
-
Another way of capturing the bitmap is without using waitForBitmapAppear action:
You can take the bitmap yourself using snapshot or pint screen on your keyboard (make sure you don't edit the image or change the format). You can capture the image
itself and save it as bitmap using "paint" program. Make sure you save the bitmap same color depth as the machine you are running the scenario on. For example,
if the machine depth is 16bits then you should save the bitmap as 16 bits.
Save the image in your scenario scripts [scenario]_files folder
[Chroniker Install Folder]\ScenarioStation\bin\script\[scenario]_files folder
and give it a meaningful name, in our example we will use products.bmp
Open your scenario file in Text Editor "notepad", for example, and add the following line where appropriate
WaitBitmapAppear (products,81,95,640,286,4,10,0,0,0,0)
products is the name of the image we saved
81 is the width of the saved image
95 is the threshold of the image we saved
640 is the x position on the screen where you captured the bitmap
286 is the y position on the screen where you captured the bitmap
4 This is cursor position (center)
10 is the time wait for the bitmap to appear
0 Search Region (x) top from (top, left)
0 Search Region (y) left from (top, left)
0 Search Region (x) from (bottom, right)
0 Search Region (y) from (bottom, right)
-
If the bitmap on the screen needs time to appear, then use WaitForBitmapAppear action instead of FindBitmap. You can also specify the wait time for the bitmap
to appear in the WaitForBitmapAppear window. If you enter 5 as below, for example, this means the scenario will look for the image for 5 seconds before it
decides a fail or success.
-
If you captured the bitmap on one machine and then moved your scenarios to a different machine, then make sure the two machines have same color depth and the
captured image matches the original.
-
My Scenario fails before it's complete and I get "Playback failed to complete within specified duration of [number of seconds] :
You can set the scenario time by going to File then Scenario Properties from your Station and set the "Playback Error After" time. The duration time of your
actual scenario plus ( Event Enterval * number of lines in your scenario ) should be equal or less than "Playback Error After" time.
The Event Enterval means
to wait for the specified time in milliseconds before it executes each line in your scenario. It can also be specified by going to File then Scenario
Properties from your Station
-
My scenario fails and I have many applications open. How can close all those open applications?
In your Station, go to File then choose Scenario Properties: Input the command to execute on scenario failure. The command you enter will be
executed at the specific station where the scenario fails.
You can enter more than one command, for example,
taskkill /im iexplore.exe /im wfica32.exe /f
The above command will kill all "Internet Explorer" running and "Citrix ICA Client Engine" running.
Note: This command is a windows command. You can enter any windows command that is installed on your windows OS in this option box.
Back to top
Once registered, you can now manage these scenarios in
Chroniker under the AppsWatch Module.
To View Scenarios
• In the Main Scenarios Screen, click on the small
plus sign in the white box to expand to see the checkpoints under each scenario.
• Click on the scenario name to see real time and
history graphs.
• Apply profiles, alerts, view reports, etc. using
the same features available in all Chroniker modules.
PLease refer to Chapter 2: Features Common to All Modules .
To Run a Scenario Immediately
The scenario should run regularly at the frequency you already defined when you registered the scenario. For testing purposes, you can run a scenario immediately as follow:
• Find the scenario you wish to run in AppsWatch home page.
• Click the  icon corresponding to the scenario you wish to run. Click OK to confirm.
• On the ScenarioStation where the scenario is located, you will see the scenario running.
Back to top
To Edit a Scenario
• Find the scenario you wish to edit in AppsWatch home
page.
• Click the Edit icon corresponding to the scenario. This
brings up the Edit Scenario page.
To Delete a Scenario
• Find the scenario you wish to delete in AppsWatch
home page.
• Click the Trash can icon corresponding to the
scenario you wish to delete. Click OK to confirm.
Back to top
To setup alerts that will be triggered when your scenario fails or exceeds a certain threshold, you need to:
- Define a Reaction. Reactions are enacted when thresholds are exceeded.
- In Scenarios Page, click on Reactions button in the top menu bar
- Click on "Add New Reaction" and select the type of reactions you want to define: email, custom, numerical page, restart, or SNMP trap.
- Fill out the form.
Click here to learn more about reactions.
- Define an Event that the reaction will be applied to. Events will launch your predefined reactions when conditions you define are met. You can assign up to 2 reactions per event.
- In AppsWatch module, click on the events button in the top menu bar
- Click on "Add New Event" button and fill out the form.
Click here to learn more about events.
- Apply this event to your scenario:
- In the event page, click on the “Apply Event” button which is the first button to the left of the event you want to apply
- Select your scenario(s) from the list
- Click “Apply”
Note: you can also apply a predefined event to a scenario by clicking on the edit button next to the scenario in the Scenarios page in Chroniker Base
For detailed help on setting up reactions (alarms) in the Chroniker base, please refer to Chapter 2: Features Common to All Modules .
Back to top
The Pause icon and Resume icon toggles, allowing you to pause
and resume the scenario monitoring. If there is planned downtime, monitoring
can be paused and then re-started when necessary. Stopping monitoring will
prevent unwanted alerts and alarms. When scenario monitoring is active the
button shows the double red vertical bars.
To Stop Scenario Monitoring
• On the AppsWatch home page, find the scenario you
wish to stop monitoring.
• Click on the corresponding Pause icon.
• Confirm the pause by clicking OK.
To Resume Scenario Monitoring
• On the AppsWatch home page, find the scenario you
want to resume monitoring. When the scenario testing is paused the button shows
the resume icon.
• Click on the corresponding Resume icon for
the scenario.
• Confirm the resume by clicking OK.
Back to top
Screenshot of Current
Error
• To view current scenario error, click on the
screen icon next to Execution Failed.
Historical Viewing of
Screenshot Errors
• To view screenshots of past errors, click on the
scenario name to see the graph and summary statistics.
• In the line graph, click on the point on the graph where the
scenario failed in the past (value will be zero and the point color is red). The actual screenshot of the
failed scenario will pop up.
Note: • the center of the magnifying glass must be exactly over the point
to retrieve the screen shot.
• The historical screenshots are only accessible through line graphs and not the bar graphs.
Back to top
Chroniker AppsWatch provides pre-made templates for useful reports. It has three report categories: Analysis reports, Top (n) reports, and List reports.
Analysis Reports include:
• Daily/Monthly/Yearly Report.
• Service Level Agreement (SLA).
• Application Scripts Alert Details Report.
Top (n) Reports include:
• Slowest Application Scenarios for the current month.
• Least Available Application scenarios for the current month.
• Application scenarios with highest alert activity in past 24 hours.
List Reports for AppsWatch: includes event list report .
Active Alerts
Click the Active Alerts button, from the AppsWatch home page to view Active Alerts. Active Alerts show scenarios that failed or are currently exceeding thresholds at a glance. The table shows the Alert Time, the Alias, the Scenario, the alert message, and the reaction.
The colored ball indicates the alert status of the scenario.
Alert Status Color Codes
Blue ball icon - informational alert
Yellow ball icon - warning alert
Orange ball icon - error alert
Red circle white arrow icon - means "down", failed scenarios execution
Back to top
Daily/Monthly/ Yearly Report
This report displays Uptime and Performance information in three different time frames - daily, monthly, and yearly. Columns show the Uptime% or Performance in milliseconds for the time frames of Business hours or Twenty Four Seven.
Uptime Percentage and Performance in Seconds
Uptime Percentage is the numerical value for the amount of time the test is active.
Performance (ms)
This measurement is broken down by column in either 24/7 time period or Business Hours.
Business Hours
Uptime% during the hours of 9:00 am to 5:00 p.m., Monday through Friday as in the default Business Hours Profile included in Chroniker. You can assign a different profile for this column as follows:
 In Chroniker menu bar, click on setup
Once in Setup page, click on Global Options
Select the Business Hours Profile that you want to apply for reports from the drop-down list
Click submit
24/7
Total uptime% without any time restraints placed on it.
Back to top
Service Level Agreement (SLA)
Displays test Uptime and Performance information in three different time frames daily, weekly, and monthly.
Uptime Percentage and Performance in Milliseconds.
Uptime Percentage
The numerical value for the amount of time the test is active.
Performance (ms)
This is the numerical time value it takes to get a response from an active test.
These columns are split up by Today and Yesterday for the Day, Current or Previous for the Week and Month.
A high uptime percentage is desirable, while a low performance number (i.e. response time) is desirable. Green means good and red means bad when comparing today to yesterday or the current week/month to the previous one. The arrows show either up or down in comparison to its own category.
For example, a green arrow uptime of 98% compared to yesterday's 69% is good. A red up arrow for today's performance of 1000.24 compared to yesterday's 50.12 is bad.
Back to top
Application Scenarios Alert Details Report
Displays alert information about the specific module. It provides object alias of the monitored data with alert duration, starting and ending date and time, and alert message
Alert
This shows the alert status of the scenario following the color code below:
Green - no alert
Blue - information alert
Yellow - warning alert
Orange - error alert
Red circle white arrow icon -it means down, the execution of the scenario had failed.
Alias
This is the name of the scenario that is in an alert state.
Alert Duration
The amount of time that the scenario was down or exceeded a certain threshold.
Alert Started
This is the actual time in which the scenario first triggered the alert.
Alert Ended
This is the actual time in which the scenario was measured with an acceptable response time.
Alert Message
Displays the message you defined at the event level which includes specifics about that alert such as: alert type, state, the value watched which is the response time that triggered the alert, and more.
Back to top
Top N Reports
Select a number from the left hand drop down list. Click the radial button to Get the top N (5,10, 15, 20, 25, 50, or 100) scenarios with a particular test result statistic.
N Slowest Application scenarios for the current month: displays the top N scenarios with highest average execution time. For each of those scenarios, it will show its average, maximum, and minimum execution time.
N Least Available Application scenarios for the current month: shows the top N scenarios with lowest percent successful executions. For each of those scenarios, it presents the percent successful, total successful and total failed executions.
N Application scenarios with highest alert activity in past 24 hrs: displays the top N scenarios with highest total number of alerts. For each of these scenarios, it shows the number of down, error, warning, and information alerts associated with that scenario.
Back to top
List Reports for AppsWatch
Event List Report: displays a summary of which events are assigned to each scenario.
• Application script is the scenario name.
• Super Scenario is the check frequency group the scenario belongs to.
• Information event displays the information event name assigned to this scenario
• Warning event displays the warning event name assigned to this scenario
• Error event displays the error event name assigned to this scenario
• Down event displays the down event name assigned to this scenario
Back to top
Exporting Reports
Reports generated from the Reports page can be exported. To export a report to Excel:
• Go to the report you wish export.
• Click Export to Excel button.
• Choose to either Open the Report immediately OR to Save the report. To save the report one has to specify the path location to save the file to.
E-Mailing Reports
Reports generated from the Reports page can be E-mailed. Note the recipient must have HTML enabled for their inbox. To e-mail a report:
• Go to the report you wish to email.
• Click the E-Mail this Report button.
• Type the Name and E-mail address of who will receive the report in the proper fields.
• Type your name and E-mail address in the proper fields.
• Type a message you wish to accompany the report in the body of the E-mail.
• Click the Send E-mail button.
Back to top
| 
