> 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/mapping/options-mapping-step/output-tab.md).

# Output tab

![Mapping Output Tab](https://2745965000-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvZoINBz5C5WnDZQlbOJQ%2Fuploads%2Fgit-blob-e3065547b572e19a0f2cf62caf329db38c08fe34%2FPDI_TransStep_Mapping_Output_Tab.png?alt=media)

By default, one output entry is available; however, you can add more output entries using the Plus Sign button by the **Available outputs** pane. Each of the output entries correspond to one Mapping output specification step in the mapping or sub-transformation. That means you can have any number of output entries (or none) in a single mapping step.

| Options                            | Description                                                                                                                                                                                                                                                |
| ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Available outputs (Add output)** | <p>Use the Plus Sign button to add a tab to specify an output mapping for the specified sub-transformation.</p><p>You can remove an output entry by clicking the X icon.</p>                                                                               |
| **Main data path**                 | Check this if you only have one output mapping and you can leave the two following fields (**Mapping source step name**and **Output target step name**) empty.                                                                                             |
| **Mapping source step name**       | The name of a Mapping output specification step in the sub-transformation where data will be read from. Use the **Choose** button to select this step from a list.                                                                                         |
| **Output target step name**        | The name of the step in the current transformation (parent) that is to receive the rows from the Mapping source step. This can be any step whose incoming hop is connected to the Mapping step. Use the **Choose** button to select this step from a list. |
| **Description**                    | Add a description to this output step mapping here.                                                                                                                                                                                                        |
| **Mapping**                        | Not enabled on the **Output** tab.                                                                                                                                                                                                                         |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pentaho.com/pdia-data-integration/10.2-data-integration/pdi-transformation-steps-reference-overview/mapping/options-mapping-step/output-tab.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
