> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pdia-data-integration/10.2-data-integration/pdi-transformation-steps-reference-overview/pentaho-reporting-output/general.md).
# General
The following fields and button are general to this transformation step:
| Field | Description |
| --------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Step name** | Specify the unique name of the Pentaho reporting output step on the canvas. You can customize the name or leave it as the default. |
| **Report definition file** | Specify the field that will contain the name of the `.prpt` file during step execution. |
| **Output file** | Specify the field that will contain the name of the output file. Also, specify the output file path. Otherwise, the file will be created in the PDI client's home folder (`/data-integration/output.pdf` for example). |
| **Accept file name from field?** | Select to specify that the report file and output file will be determined by incoming fields. If this option is not selected, you must specify the filepaths and names of the report definition and output files. |
| **Report definition file** | Specify the filepath and name of the report definition file. This field is only active if **Accept file name from field** is not selected. |
| **Output file** | Specify the filepath and name of the output file. This field is only active if **Accept file name from field** is not selected. |
| **Create Parent Folder** | Select this checkbox and specify the full file path in the **Output file** field, if you want to create a parent folder for placement of the output file. |
| **Parameter name** | Specify the name of the parameter (if the report being generated supports parameters for input), to pass values from an input field to the report. |
| **Field name** | Specify the name of the field (if the report being generated supports parameters for input) to stream fields to provide the values. If you specify a field to use, the static input value is not used.
To pass data to String arrays, make sure the data items are separated using tabs as a delimiter.
|
| **Output processor** | Specify the reporting engine used for the generation of the output file type (for example, `.pdf`, `.csv`, `.xml`, etc.). |
| **Get Report Parameters**(button) | Click this button to import the defined parameters from an existing report. |
\*\*Note:\*\* To view a sample transformation in the PDI client, open the \`Pentaho/design-tools/data-integration/samples/transformations/Pentaho Reporting Output Example.ktr\` sample file.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.pentaho.com/pdia-data-integration/10.2-data-integration/pdi-transformation-steps-reference-overview/pentaho-reporting-output/general.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.