> For the complete documentation index, see [llms.txt](https://docs.meta-inf.hu/pipeline-forms/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.meta-inf.hu/pipeline-forms/user-guides/user-guide/create-forms/variables.md).

# Variables

## Managing Variables

<figure><img src="/files/VCrT733W1qCw8OwqLOBb" alt=""><figcaption><p>Accessing variables</p></figcaption></figure>

You can manage your variables via the upper-right corner menu of the application. From this menu, you can:

* Add new variables.
* Remove existing variables.

{% hint style="warning" %}

#### Sensitive Information

If you need to store sensitive information, toggle the lock icon next to the value field. Locked values will be masked in the list to ensure confidentiality.
{% endhint %}

## Using Variables

{% hint style="info" %}
Variables are currently only available in the **Remote Select** field.&#x20;
{% endhint %}

Below is an example of how variables can be integrated into the field:

```yaml
- &example-remote-select-field
    label: Remote Options With Auth
    type: remote_select
    name: EXAMPLE_REMOTE_SELECT
    availableValues:
      url: "https://hub.docker.com/v2/repositories/atlassian/jira-software/tags/?{{query}}"
      path: "$.results.[*].{{path}}"
      headers:
        - user-name: {{user}}
        - api-key: {{apiKey}}
        - My-{{header}}: test
      method: "{{method}}"
      body: "{'test': '{{bodyValue}}'}"
```

Under the `availableValues` section, you can use variables in any of the values. If a variable does not exist, its placeholder will remain empty. This allows for dynamic configurations based on the variables provided.

***

By effectively managing and utilizing variables, you can enhance the efficiency and flexibility of your Pipeline Forms configurations.


---

# 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.meta-inf.hu/pipeline-forms/user-guides/user-guide/create-forms/variables.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.