Consumption Analytics Documentation

Home > Documentation for older versions > Cloud Cruiser 3 > Administering > Managing reports > Creating custom reports > Report properties

Report properties

Table of contents
No headers

The report itself can define the following user properties:



Indicates that the initial report launch page should collect some input values from the user and provide one or more values for each known parameter to the report server for generation. The value of this property should specify the name of a predefined set of standard parameters. Currently, only one such set has been defined which provides the UserGroupID parameter: standard_set_1 .

Defines the report group in which the report should be listed. The value should be the group name (key) not the title of a group in the system.

<property name="" value="Invoices"/>

If this property is not included, or the value does not refer to a valid group name, when imported, the report will be filed under the default group. The report group definition table contains a default_flag column which defines which Group in the system is default. The default group is where reports can be grouped if not defined at import time.

Indicates that the report is only actually referenced by other reports and should not be displayed as a top-level report in the Reports tree.

<property name="" value="true"/>

If this property is not included, or the value is not true, it will be assumed that the report is a top-level report and should be displayed in the reports tree.

This defines the designed report type. Some reports are intended to be exported/viewed to a specific format, as opposed to being viewed in Cloud Cruiser and then exported to some file type determined by the user. This value can be used to group reports differently (for example, Show all XLS Reports ).

<property name="" value="XLS"/>

If this property is not included, or the value does not refer to either XLS, PDF or HTML when imported, the report will be defined as HTML.

Tells the report server how to cache report information. Currently, the two possible values are: REPORT and DATA, indicating whether to cache the filled report itself or just the dataset used to fill the report, respectively. The default is REPORT, which should be used in most cases.

If you want the dataset used to fill the report to be cached separate from the filled report itself, you can specify a stored procedure call with parameter names in this property. The expected format of this value is procedure_name:param1 , param2 , param3 , etc. For example, this property declaration indicates that the dataset should be generated outside of JasperReports by calling the sp_test stored procedure with values from the resourceGroupID and resourceID parameters:

<property name="" value="sp_test:resourceGroupID,resourceID"/>

Note that in order for these values to be supplied to the report server and the report, you will also need to add properties to the parameters themselves in order for the user to be prompted for values.

By default, all reports will be loaded for the administrator role only. This is a precaution intended to prevent accidental distribution of potentially sensitive information to non-administrative users. Once an administrator determines that the report is safe for non-administrators to view, they may add this property to the report with a value of false and reload the report. It will then be visible to all users to run. Note that a value of true is same as the default behavior of not supplying the property at all - it is loaded for administrators only.

Last modified


This page has no custom tags.


This page has no classifications.

 (c) Copyright 2017-2020 Hewlett Packard Enterprise Development LP