...
Reporting Plugin Parameter Reference
The Pentaho Reporting System reserves all parameter names starting with "::" as system parameter. The engine will claim these parameters as private property. Do not use such parameter names for your own reports.
In addition to that, the following parameter names are used by the MantleBI-Server reporting-Plugin and should not be used in a report for user-data (unless you know exactly what you are doing)
...
Table Cell (td) |
---|
The name of the current solution in the solution repository |
|
|
...
Table Cell (td) |
---|
The path within the solution repository |
|
|
...
Table Cell (td) |
---|
The name of the prpt within the repository |
|
Table Row (tr) |
---|
Table Cell (td) |
---|
Alias for the "name" parameter. |
|
Table Row (tr) |
---|
Table Cell (td) |
---|
renderMode |
|
|
...
Table Cell (td) |
---|
One of the following values: Value | Description |
---|
REPORT | renders the report | XML |
|
|
|
...
returns the parameter description document for the UI |
|
|
|
...
| PARAMETER | same as XML, but does not perform any pagiation | SUBSCRIBE | for managing subscriptions | DOWNLOAD |
|
|
|
...
Downloads the prpt file, if the user has the correct permissions |
|
|
|
...
Table Row (tr) |
---|
Table Cell (td) |
---|
output-target |
Table Cell (td) |
---|
Defines how the report should be exported. This parameter is the canonical output parameter and overrides all other parameters that may attempt to define the output type. Output-target | Description |
---|
table/html;page-mode=stream | HTML as a single page, all report pagebreaks are ignored | table/html;page-mode=page | HTML as a sequence of physical pages, manual and automatic pagebreaks are active | application/vnd.openxmlformats-officedocument.spreadsheetml.sheet;page-mode=flow | Excel 2007 XLSX Workbook | table/excel;page-mode=flow | Excel 97 Workbook | table/csv;page-mode=stream | CSV output | table/rtf;page-mode=flow | Rich-Text-Format | pageable/pdf | PDF output | pageable/text | Plain text | pageable/xml | Pageable layouted XML | table/xml | Table-XML output | pageable/X-AWT-Graphics;image-type=png | A single report page as PNG | mime-message/text/html | Mime-Email with HTML as body text and all style and images as inline attachments |
|
|
Table Row (tr) |
---|
Table Cell (td) |
---|
dashboard-mode |
|
|
...
Table Cell (td) |
---|
if "true": If the export generates HTML, the report will generate a body-fragment (content without the HTML, HEAD and BODY tags and all styles inlined into "style" attributes), which is easy to include in dashboards or other HTML pages. This is the same result as if the report configuration property "org.pentaho.reporting.engine.classic.core.modules.output.table.html.BodyFragment" has been set to true. |
|
|
...
Table Cell (td) |
---|
Defines which page to generate for HTML-Page and PNG output. |
|
Table Row (tr) |
---|
Table Cell (td) |
---|
autoSubmit |
Table Cell (td) |
---|
Defines whether auto-submit should be active in the UI. If this parameter is given and either "true" or "false", the UI will not allow the user to change the auto-submit configuration. This property is deprecated. Auto-Submit should be defined inside the report itself. A global default can be defined in the report configuration, using the global configuration key "org.pentaho.reporting.engine.classic.core.ParameterAutoSubmit". |
|
Table Row (tr) |
---|
Table Cell (td) |
---|
autoSubmitUI |
Table Cell (td) |
---|
Defines the initial state for the auto-submit checkbox in the UI. This parameter has no effect if "autoSubmit" is defined in any way. This property is deprecated. Auto-Submit-UI should be defined inside the report itself. A global default can be defined in the report configuration, using the global configuration key "org.pentaho.reporting.engine.classic.core.ParameterAutoSubmitUI". |
|
Table Row (tr) |
---|
Table Cell (td) |
---|
A internal flag indicating that a subscription is configured. |
|
Table Row (tr) |
---|
Table Cell (td) |
---|
subscription-id |
Table Cell (td) |
---|
A internal parameter. |
|
Table Row (tr) |
---|
Table Cell (td) |
---|
subscription-name |
Table Cell (td) |
---|
A internal parameter. |
|
Table Row (tr) |
---|
Table Cell (td) |
---|
destination |
Table Cell (td) |
---|
A internal parameter. |
|
Table Row (tr) |
---|
Table Cell (td) |
---|
Defines whether the report shall be printed. Overrides all other output properties. |
|
Table Row (tr) |
---|
Table Cell (td) |
---|
printer-name |
Table Cell (td) |
---|
The (optional) name of the printer |
|
|
...
Deprecated properties
- action: The name of the xaction within the repository (use name instead)
- paginate: Boolean (DEPRECATED: use output-target parameter instead)
- content-handler-pattern: when exporting to HTML, the name of the content handler servlet that sends images and css files to the browser. (DEPRECATED: configure that via a global configuration setting)
- layout (BISERVER 3.6): vertical or flow (DEPRECATED: use report attribute instead)
- ignoreDefaultDates: boolean (DEPRECATED: use configuration instead)
- output-type: (DEPRECATED: use output-target parameter instead)
The output type specified as mime-type. This provides a generic way to select the output-target and possibly requires additional parameters to work. - text/html
- application/vnd.ms-excel
- text/csv
- application/rtf
- application/pdf
- text/plain
- mime-message/text/html
in addition to that, the following deprecated output-types are supported, but will yield a warning everytime they are used. These output-types should no longer be used and support for them will be removed in a future version.
...
Table Row (tr) |
---|
Table Cell (td) |
---|
showParameters |
Table Cell (td) |
---|
Defines whether the parameter UI shows any parameter input. This URL parameter is deprecated. Use the report attribute with the same name instead. |
|
Table Row (tr) |
---|
Table Cell (td) |
---|
report-definition |
Table Cell (td) |
---|
Only usable in XActions. Has no effect if given on a URL. |
|
Table Row (tr) |
---|
Table Cell (td) |
---|
useContentRepository |
Table Cell (td) |
---|
Only usable in XActions. Has no effect if given on a URL. |
|
Table Row (tr) |
---|
Table Cell (td) |
---|
Only usable in XActions. Has no effect if given on a URL. |
|
Table Row (tr) |
---|
Table Cell (td) |
---|
Only usable in XActions. Has no effect if given on a URL. |
|
Table Row (tr) |
---|
Table Cell (td) |
---|
Deprecated. Only used in legacy reports. |
|
Table Row (tr) |
---|
Table Cell (td) |
---|
content-handler-pattern |
Table Cell (td) |
---|
Only usable in XActions. Has no effect if given on a URL. |
|
Table Row (tr) |
---|
Table Cell (td) |
---|
Defines how the parameter inputs are laid out. Can be one of "vertical", "horizontal" or "flow". This URL parameter is deprecated, use the report attribute instead. A global default can be defined in the report configuration, using the global configuration key "org.pentaho.reporting.engine.classic.core.ParameterUiLayout" |
|
Table Row (tr) |
---|
Table Cell (td) |
---|
ignoreDefaultDates |
Table Cell (td) |
---|
Deprecated. Has no effect anymore. The UI does no longer generate default selections, if you need a default value for a parameter, set it in the parameter definition instead. |
|
Table Row (tr) |
---|
Table Cell (td) |
---|
output-type |
Table Cell (td) |
---|
Deprecated. Use "output-target" instead. |
|
|
How the simple-reporting-component selects the output-target
The algorithm to determine the output target from the given parameters is as follows:
...
If the output type given is invalid, the report will not be executed and calls to
SimpleReportingComponent#getMimeType() will yield a generic "application/octet-stream" response.
Examples
To download a PRPT file from the server:
Code Block |
---|
/content/reporting?renderMode=download=DOWNLOAD&solution={0}&path={1}&name={2}
|
To view the parameter document for a report.
Code Block |
---|
/content/reporting?renderMode=PARAMETER&solution={0}&path={1}&name={2}
|
...
Code Block |
---|
/content/reporting?renderMode=reportREPORT&solution={0}&path={1}&name={2}&output-target{3}
/content/reporting?renderMode=reportREPORT&solution={0}&path={1}&name={2}&output-type{3}
|
...