> For the complete documentation index, see [llms.txt](https://docs.eximee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/logika-biznesowa/parametry-wejsciowe-formularza.md).
# Form input parameters
## Form input parameters
To pass parameters via the URL to the form, we need to define a variable or add a component to which we want to pass this parameter.
In the application edit view, in the left menu, select the option **Input parameters**, and then **Add input parameter**. As the value **Alias** we provide the name of the injected variable alias. **Alias** will be part of the URL to the application page. As **Request component** we choose a field from the application or a session variable. We can also assign it a default value, which will be used if the parameter is not passed in the URL.
Figure 1. Form input parameters
### **Ways to pass parameters**
1. Passing the parameter directly in the URL:\
\
{% hint style="danger" %}
**Passing the parameter**
The parameter must be passed correctly in the address. Correct example: . The parameter must be before #.
{% endhint %}
2. Passing the parameter as a hidden input field:
```
```
### Input parameters of composite components
You can find more information in the section [Input parameters of a composite component](/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/komponenty-rozszerzone/komponenty-zlozone.md#parametry-wejsciowe)
\
---
# 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.eximee.com/documentation/documentation-en/budowanie-aplikacji/logika-biznesowa/parametry-wejsciowe-formularza.md?ask=&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.
