> 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/9.3-data-integration/pdi-transformation-steps-reference-overview/mapping/mapping-input-specification/options.md).

# Options

| Option                                          | Description                                                                                                                                                                                                                                                        |
| ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Step name**                                   | Name of the step. This name has to be unique in a single transformation.                                                                                                                                                                                           |
| **Name**                                        | The name of the field as it will be known inside the sub-transformation.                                                                                                                                                                                           |
| **Type**                                        | The data type of this field.                                                                                                                                                                                                                                       |
| **Length**                                      | Maximum string length.                                                                                                                                                                                                                                             |
| **Precision**                                   | Maximum number of decimals.                                                                                                                                                                                                                                        |
| **Include unspecified fields, ordered by name** | <p>In certain borderline cases, you not only want the required fields, but all of them. This option allows for this situation.</p><p>This is the case, for example, if you want to remove certain fields from the stream later on, retaining all other fields.</p> |

\*\*Note:\*\* During design time, none of these unspecified fields will be available in field picklists etc., since these fields will be available only during runtime, not design time.


---

# 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/9.3-data-integration/pdi-transformation-steps-reference-overview/mapping/mapping-input-specification/options.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.