Your email address as well as other information about you and your company will be kept protected from abuse.
You can choose to have all submitted data removed from our system at any time.
Access to the information you submit will be controlled by you and your company.
All information sent to and from RRR|Online using your browser will be encrypted using SSL to ensure privacy.
We at RRR AB will monitor the applications at RRR|Online to make sure that all services are functioning properly.
We log all access to the system by storing email address, script name of url and timestamp. This information will only be used for overall statistical purposes and to track errors or abuse of RRR|Online.
Please send any questions or comments about our privacy policy to support@rrr.se.
2. Integrating RRR|Flash in your application
2.1. Required fields starting with two underscores
2.2. Optional fields starting with one underscore
This documentation is intended to serve as a guide to using RRR|Flash.
The documentation will give you detailed information about all parts in the product.
If you think that relevant information is missing, or have any other comments or questions, feel free to send them to support@rrr.se.
Copyright 2002 by Real Refined Resource Scandinavia AB. All rights reserved.
You may not distribute the RRR|Flash definitions, but may personally install the module at any ARSystem.
You are entitled to print this documentation for your personal use.
The RRR|Flash gives you limited flashboards-type graphical representation of data in your ARSystem.
Statistical data shows opened/closed tickets grouped by:
- Month
- Week
- Day
- Hour
4 different graphs that shows:
- Number of new tickets for each period
- Number of closed tickets for each period
- Number of open tickets at end of each period
- The difference between the number of new and closed tickets
The small module can be integrated to almost any ARSystem application.
The requirements only demand two date/time-fields.
The first represent the start date of the ticket (i.e. 'Status-History.New.TIME' or 'Create Date').
The second represent the closure date of the ticket (i.e. 'Status-History.Fixed.TIME').
You can add qualifications when the module is called to give you more specific statistics.
No workflow is added to your current forms. There are two active links that retrieve the statistics from your form. These active links are attached to the main RRR|Flash form and are named RRR|Flash period loop 001 init (custom) and RRR|Flash period loop 111 count (custom).
This is what you need to do to quickly get some results from RRR|Flash:
1. Enter your form name in the request-form att RRR|Online
2. Enter the field ids of the two date/time-fields that represents the opening and closeore of your tickets
3. Submit the request form
4. Import the two definition files that is mailed to you
5. Look at (and copy/duplicate) one of the 3 active links attached to the RRR|FlashTest form
To use RRR|Flash, you need to ad one or more active links to your application.
The active link should have one action that does an Open Window Dialog with the RRR|Flash form
Make sure that you call the Automatic-view of the RRR|Flash form.
There are three required fields that you need to give RRR|Flash to work on.
These fields are the three topmost fields displayed in your Open Window Dialog action, named '__period', '__starttime' and '__endtime'.
These fields are discussed in detail in the next section.
These are the three mandatory fields when doing an Open Window Dialog to RRR|Flash:
| __period | This field can be set to one of four values: 0 - Month 1 - Week 2 - Day 3 - Hour This will decide the granularity of the statistics. |
| __starttime | This field tells the statistics when to start finding tickets. Note that the actual starting date will be the first second of the Month/Week/Day/Hour that the time you specify belongs to. You do not need to find this specific time yourself. If you pass $TIMESTAMP$ to this field, it will find the correct time. |
| __endtime | This field tells the statistics when to stop searching tickets. Note that the actual starting date will be the last second of the Month/Week/Day/Hour that the time you specify belongs to. You do not need to find this specific time yourself. If you pass $TIMESTAMP$ to this field, it will find the correct time. |
There are a number of parameters you can set that affects how RRR|Flash works.
| _advancedsearch | In this field you can add qualifications to make the statistics more specific. i.e. you can add "'Assigned Group' = ""Network""" to show only tickets that was assigned to the Network Group. Note that you need to double doublequotes to have the system understand them. If you use keywords you need to put a backslash (\) after the first dollar-sign ($) of the keyword. Look below for an example. If you want tor replace "Network" with a field in your calling form it gets even more tricky. You should then type "'Assigned Group' = """ + $Assigned Group$ + """" |
| _datetimefield_open _datetimefield_close |
These two fields can be used to specify other date/time-fields to represent the opening/closure of your tickets. 3 represent the Create Date 15.0.2 represents the Status-History.0.TIME field (0 is the first Status Value). |
| _hideopened _hideclosed _hideend _hidediff |
If you assign a value (Yes/0) to these fields, the corresponding part of the statistics will not show. |
| _fontsize | Default is 9. If you enter a larger value, the fontsize will grow. |
| _maxperiods | Default is 100. This field makes sure that the statistics requested by the user does not span an unreasonable number of periods, resulting in a very long waitingtime. If you view statistics per month, 100 periods will be the same number of months (more than 8 years). Statistics per hour will give you 4 days at the default 100 periods. |
| _nocache | Set this field to Yes/0 if you do not wish to use the cache functionality in RRR|Flash. Caching is important for performance. The second user requesting the same statistics will not need to compute it again. Note that caching is not used at all wen users do statistics on periods that are not closed. No caching is used if you do monthly statistics including the current month, or day-statistics when you include the current day. I.e. if you want to show the user statistics on the last 7 days, set the _starttime to $TIMESTAMP$-8*24*60*60 and the _endtime to $TIMESTAMP$ - 1*24*60*60, to make sure that caching is used. |
| _scale | This value defaults to 100, and is suitable for graphs where you open/close about 5000 tickets per the selected period. If you are doing hour statistics, you could lower this to 1 if the number of tickets opened per hour does not exceed 50-100. |
| _width | Defaults to 20, and represents the width of the individual boxes in the graph. |
Some default values can be change by opening the RRR|Flash form in in the ARAdmin Tool, and changing the default values of these fields.
The picture shows the fields you can change.
To run RRR|Flash, you need a server and clinet with at lease version 5 of the ARSystem.
The following clients has been tested.
The windows client version 5.0.1 with patch 1162.
There was sporadic problems on my testing environment when I used an unpatched ARUser 5.0.1, resulting in ARUser crasching. It seemed to be related to the fact that I was continously changing the application definitions...
If you want to deploy RRR|Flash to the web, you only need to import the RRR|Flash application that is already prepared for this purpose.
The RRR|FlashTest application can be used to test the system.
Version 5.1 of MidTier works OK.
There is a problem with tables not aligning the graphs to the bottom of the table, thus making the statistics look a little different...
RRR|Flash did not work at all in MidTier 5.0.1 with no patch installed.