> 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/switch-case/options.md).

# Options

The Switch / case step includes the following options:

![Screen capture showing the options available for the switch case step](https://3411831820-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAYwCj9fPr1B2pjC11IOQ%2Fuploads%2Fgit-blob-14bd1f98c1b6733cb95a249c9ed77c9355227d0c%2FPDI_TransStep_Dialog_SwitchCase.png?alt=media)

| Option                             | Description                                                                                                                                                                                                                                           |
| ---------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Step name**                      | Specify the unique name of the Switch/case step on the canvas. You can customize the name or leave it as the default.                                                                                                                                 |
| **Field name to switch**           | Specify the field name that contains the **Value** to use as a basis for the row routing. Values are specified in the **Case values** entry table.                                                                                                    |
| **Use string contains comparison** | If selected, the comparison will be true if the **Value** is found anywhere in the field being tested.If cleared, the **Value** must exactly match the field.                                                                                         |
| **Case value data type**           | Specify the data type of the values listed in the **Case values** entry table.                                                                                                                                                                        |
| **Case value conversion mask**     | Specify the conversion mask of the values listed in **Case values** (numeric / data values).                                                                                                                                                          |
| **Case value decimal symbol**      | Specify the decimal symbol of the values listed in **Case values** (numeric values).                                                                                                                                                                  |
| **Case value grouping symbol**     | Specify the grouping symbol of the values listed in **Case values** (numeric values).                                                                                                                                                                 |
| **Case values**                    | In the table, per each row, specify a single **Value** and **Target step** pair. You may specify the same **Target step** in more than one single row\.To specify a null value, leave the **Value** for a row blank while entering a **Target Step**. |
| **Default target step**            | Specify the name of a target step in the transformation as a default for any unmatched rows. All rows that do not match any of the **Case values** are sent to this target step.                                                                      |


---

# 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/switch-case/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.