> 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/string-operations/the-fields-to-process-string-operations-step.md).

# The fields to process

![The fields to process table in the String Operations step](https://3411831820-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAYwCj9fPr1B2pjC11IOQ%2Fuploads%2Fgit-blob-222188d54946ca239477d148a270e6252b386656%2FssPDITransStep_StringOperations_PropertiesDialogBox.png?alt=media)

Use **The fields to process** table to specify which operations you want to apply to your input strings.

The table contains the following columns:

| Column                       | Description                                                                                                                                                                                                                                                       |
| ---------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **In stream field**          | Name of the field containing the string to be processed. Use **Get fields** to populate the table with fields from the incoming PDI data stream.                                                                                                                  |
| **Out stream field**         | (Optional) A new outgoing PDI field containing the results of the specified string operations. If you do not specify a value for this field, the **In stream field** is replaced by the resulting string.                                                         |
| **Trim type**                | Specifies whether to remove extra spaces before or after a field. You can trim a field on its left side, right side, or both. The default value is none.                                                                                                          |
| **Lower/Upper**              | Specifies whether to make all the characters in a field upper or lowercase. The default value is none.                                                                                                                                                            |
| **Padding**                  | Specifies whether to add extra characters before or after a field. You can pad a field on its left side or its right side. The default value is none.                                                                                                             |
| **Pad char**                 | The extra character added to a field for padding.                                                                                                                                                                                                                 |
| **Pad Length**               | The amount of extra characters used for padding.                                                                                                                                                                                                                  |
| **InitCap**                  | Specifies whether to capitalize the initial character in a field. The default value is N.                                                                                                                                                                         |
| **Escape**                   | <p>Specifies whether to use, ignore (escape), or process (unescape) if the following formats are present in a field:</p><ul><li>XML</li><li>HTML</li><li>CDATA</li><li>SQL</li></ul><p>The default value is None.</p>                                             |
| **Digits**                   | Specifies whether to return only or remove numeric characters (digits). The default value is none.                                                                                                                                                                |
| **Remove Special character** | <p>Specifies whether to remove any of the following special characters from a field:</p><ul><li>Carriage return (CR)</li><li>Line feed (LF)</li><li>Carriage return and line feed</li><li>Horizontal tab</li><li>Space</li></ul><p>The default value is none.</p> |


---

# 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/string-operations/the-fields-to-process-string-operations-step.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.
