Differences

This shows you the differences between two versions of the page.

--- 75:use_reports [2020/05/15 10:01] – sahr
+++ 75:use_reports [2020/09/23 14:23] – cgl
@@ Line 1: / Line 1: @@
 ====== Use Reports ======
-Stages has connected a report engine. With this report engine content that is modelled in Stages can be analyzed.
+Stages has connected a report engine. With this report engine content that is modeled in Stages can be analyzed.
 There are three types of reports:
-  * Reports that analyze the modelled process
+  * Reports that analyze the modeled process
   * Reports that analyze the content of projects
   * Administrative reports that analyze the usage of Stages
-Stages already provides a set of [[:reports:start|Standard Reports]].
+Stages already provides a set of [[:reports:start|Standard Reports]] that can be downloaded for free.
 ===== Run a Report =====
-===== Export a Report =====
+All available reports can be found at <font inherit/inherit;;inherit;;rgb(251, 250, 249)>Reports</font>.
+Reports are global. Besides Administrative reports, reports usually analyze the content of the user's current workspace or the sub-workspaces.
+If the report has Parameters these have to be set before the report can be executed.
+{{https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/reports_parameter.png?nolink&400x187}}
+After setting the parameter the report can be executed by clicking on "Run" or on the play button.
+{{https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/reports_execute_1.png?nolink&500x448}}
+===== Export Report Results =====
+Reports results can be exported in different formats, for example Excel.
+To export report results, click on the three dots in the right corner and choose the respective format.
+{{https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/reports_export.png?nolink&500x272}}
+===== Troubleshooting =====
+If Stages is accessed through a proxy server, in some cases there can be connectivity problems for reporting requests (report execution, parameters loading and script upload fails). When these problems cannot be resolved otherwise, the following workaround can be used:
+.) Add the following property to config.xml with an url of the Stages server (host name or ip address) which is accessible for internal request from the Stages server to itself:<code>
+<property name="metrics.serverAddress" value="http://localhost"/>
+</code>
+.) Configure the proxyName and proxyPort of your proxy server for the internal connector in tomcat/conf/server.xml as shown in the following example:
+<code>
+<Connector port="80"
+proxyName="myproxy.mydomain.com"
+proxyPort="443"
+..../>
+</code>