> 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/input-tab.md).
# Input tab
Although one input entry point is available, you can create additional input entry points. Each input corresponds to one Mapping input specification step in the mapping sub-transformation. You can have any number of these entry points in a single mapping step, including no input entry point. The following table describes the options in the **Input** tab.
| Option | Description |
| ----------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Available inputs (Add input)** | Use the Plus Sign button to add an input mapping for the specified sub-transformation.
You can remove an input by clicking the X icon.
|
| **Main data path** | Select to indicate that you only have one input mapping and you can leave the two following fields (**Input source step name**and **Mapping target step name**) empty. |
| **Input source step name** | Specify the name of the step in the parent transformation (not the mapping) to read from. It can be any step in the parent transformation with an outgoing hop connected to the Mapping step. Click **Choose** to select the target step from a list. |
| **Mapping target step name** | Specify the name of the Mapping Input specification step inside the sub-transformation that is to receive the rows from the input source step. Click **Choose** to select the target step from a list. |
| **Description** | Add a description to this input step mapping. |
| **Update mapped fields downstream** | Select this option to rename fields back to their original names when they reach the **Mapping output** step. This will make your sub-transformations more transparent and reusable. If not selected, fields get renamed before they are transferred to the mapping transformation. |
| **Mapping** | Click to open the **Enter Mapping**dialog box. Use this field mappings dialog to specify exactly how the fields from the input source step are connected to the fields of the **Mapping target step**. When you finish mapping fields, click **OK** in the **Enter Mapping** dialog box. Your field mapping will appear in the mapping table located beneath the **Description**field. |
---
# 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/input-tab.md?ask=&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.