> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/actions/generic/string-operations/convert-to-uppercase.md).

# Convert to Uppercase

This is a pre-built Action located under the **@Generic Element**. The functionality of this Action in Avo Assure is to change the given text to uppercase letters. The converted text is stored in a dynamic variable.

## **Syntax**

**Input Value**: `<input string>`&#x20;

| Argument                             | Description                                               |
| ------------------------------------ | --------------------------------------------------------- |
| <p>\<input string><br>(Required)</p> | Provide the text that needs to be converted to uppercase. |

**Output Value**: `<Dynamic Variable>;<Dynamic Variable>(Optional)`

| Argument                                     | Description                                                       |
| -------------------------------------------- | ----------------------------------------------------------------- |
| <p>\<Dynamic Variable></p><p>(Required)</p>  | This dynamic variable stores the converted string.                |
| <p>\<Dynamic Variable></p><p>(Optional) </p> | This dynamic variable stores the status as **True** or **False**. |

### **Example**: Converting a String to Uppercase

In this example, we explain how to convert a given string into uppercase letters.

* **Action**: Convert to Upper case
* **Input Value**: Alice Johnson
  * This specifies the string (**Alice Johnson**) that needs to be converted into uppercase.
* **Output Value**: {Uppercase string}
  * The converted string (ALICE JOHNSON) is stored in this **{Uppercase string}** dynamic variable for further use.
  * If the second output variable is defined, it stores the action status with the following possible values:&#x20;
    * **True**: If the conversion is successful.
    * **False**: If the conversion fails due to invalid input or configuration.
* **Logical Explanation**: The **Convert to Upper case** action fetches the value from the **Input Value** column (**Alice Johnson**) and converts it into uppercase (ALICE JOHNSON). The converted string is then stored in the **{Uppercase string}** variable.

<figure><img src="/files/1ZEKpye07iCr26T4OaTm" alt=""><figcaption></figcaption></figure>

#### **Knowledge Bites:**&#x20;

Here are some examples of different string scenarios:

| String                       | Input Value | Result     |
| ---------------------------- | ----------- | ---------- |
| Text Strings                 | automation  | AUTOMATION |
| Already in Uppercase         | EMPID       | EMPID      |
| Special Character and Number | Pass\@123   | PASS\@123  |
| Alphanumeric strings         | id2025      | ID2025     |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.avoautomation.com/avo-assure/actions/generic/string-operations/convert-to-uppercase.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.