> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/process-node-parts/change-text-case.md).

# Change Text Case

## Description

This part allows you to convert text to upper case or lower case. This is helpful when you need to standardize user input to a specific case.

## Editor Fields

This part uses the following editor fields:

| Tab   | Field Name  | Description                                                                                          | Type/Options | Optional/Mandatory |
| ----- | ----------- | ---------------------------------------------------------------------------------------------------- | ------------ | ------------------ |
| Basic | Input text  | This is the literal text the system will convert. To reference a data object, use the $(...) syntax. | Text         | Mandatory          |
| Basic | Output path | This is the path (data object) for the output.                                                       | Data object  | Mandatory          |

## Example

For an example of how to use the Change Text Case part, download and import the following sample project in your workspace.


---

# 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://community-test.logicnets.com/release-9/platform-documentation/process-node-parts/change-text-case.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.