Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
custom_report [2016/09/22 02:35] 127.0.0.1 external edit |
— (current) | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | Custom reports are written in [[http:// | ||
- | The best way to write your first custom report is to clone one of the existing reports in / | ||
- | |||
- | Step 1: identify the websvc data set(s) you need for your report. You can use one or multiple websvc data set from [[WebSvc DataSet|WebSvc DataSet]]. | ||
- | |||
- | Step 2: write XSL, use www/ | ||
- | |||
- | Step 3: define report to config.properties | ||
- | |||
- | | ||
- | |||
- | where **rptName** is the name of your report to be displayed in " | ||
- | |||
- | **websvcUrl** must be a valid url that starts with **http:**. Use the following token to avoid hardcoding the url: | ||
- | |||
- | * @CURSVR@ - to be replaced by current TestOptimal server url, http:// | ||
- | * @SVRMGR@ - to be replaced by [[Server Manager Edition|SvrMgr]]' | ||
- | * @MODEL@ - to be replaced by current model name | ||
- | * @BATCHID@ - to be replaced by batch id passed as report param | ||
- | |||
- | The example above has " | ||
- | |||
- | TestOptimal stores the output of [[WebSvc Dataset|WebSvc Dataset]] and output from your xsl in /temp folder. They are useful for learning what data are available in [[WebSvc Dataset|WebSvc Dataset]] and debugging your xsl. | ||
- | |||
- | Step 4: Restart TestOptimal server to make the new report available. | ||
- | |||
- | Step 5: Test the report with a browser with url: | ||
- | |||
- | |