> For the complete documentation index, see [llms.txt](https://docs.novacura.com/flow-connect/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.novacura.com/flow-connect/reference/how-to-guides/create-user-step-controls/text-input.md).

# Text input

## Add a text input

1. Open an existing [application ](https://docs.novacura.com/flow-connect/working-with-connect/create-and-design/applications/create#create-application)or create a new one in an [application package](https://docs.novacura.com/flow-connect/working-with-connect/create-and-design/application-packages) and open it in the Designer.

   1. Add a User step.&#x20;
   2. Add a Text input.&#x20;
   3. In the Target Variable, write color.
   4. Under Appearance, in Prompt, write "Write a color".
   5. In Default Text, write "Blue".
   6. Under Behaviour, check the boxes "Force Uppercase", "Enable Text Correction" and "Trim Input Automatically".&#x20;
   7. Click the **Play** button in the top right-hand corner to run the application in diagnostic mode.

   <figure><img src="/files/TZ17uEjN5uu9kHuoOrwG" alt=""><figcaption><p>Notice that the default text shows as BLUE even though we wrote Blue, since we checked the "Force Uppercase" checkbox. </p></figcaption></figure>
2. Go back to the Designer.

   1. In the Condition To Hide, write “{userId = “*your user id”*} *(the user Id you log in to Connect with)*
   2. Run the application in diagnostic mode again.

   <figure><img src="/files/18jiW3pvUU6bcbbiO5jd" alt=""><figcaption><p>The image is now hidden since the condition is fulfilled.</p></figcaption></figure>


---

# 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.novacura.com/flow-connect/reference/how-to-guides/create-user-step-controls/text-input.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.
