> 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/proces-biznesowy/zadania-uzytkownika/formularz-startowania-sprawy.md).
# Case start form
**Case initiation form** plays a key role in launching the workflow process, as it is the starting point of the entire workflow. It is used by the user to initiate a new case (i.e. a new process instance) by entering the necessary data that forms the basis for the further course of the process.
Such a form makes it possible to collect all the information required to correctly start and direct the workflow – e.g. the applicant’s data, a description of the problem, or attachments. This allows the system to automatically determine the appropriate paths of action, participants, and tasks.
A properly designed start form therefore ensures not only the correct initiation of the process, but also order as well as completeness and quality of the data.
## Linking the form to the case type
The process definition is attached to the form in the tab **Steps** of the request editor, in the section **Request save point,** by adding the element **EximeeRouter2** and setting in it:
* **Process name** - process definition key, i.e. the key identifying the process definition
* **Case number (Business key)** - a component or session variable that contains the value for the business key of the created request. By default, if the parameter **Case number**, it will take the value of the request number.
Configuring this panel results in starting the integrated process after passing the request save point.
Figure 1. Configured request save point
## Starting the process instance and redirecting to the user task
It is possible to simultaneously save the request, start the process instance, and redirect the user to the next task. To do this, add a component to the request, e.g. [Trigger](/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/biblioteka-komponentow-bazowych/6-interakcje-i-akcje/trigger.md). Then define the action for it in the artifact properties **`START_PROCESS_AND_RESUME`**. More information in the section [Actions](/documentation/documentation-en/budowanie-aplikacji/logika-biznesowa/przeplywy/akcje.md#akcja-uruchamiania-instancji-procesu)
## Passing data from the request to the process
To pass data from the request to the process, it is necessary to add the session variable *use-model-mapping* and set its value to *true*. Then map the data from the request fields to process variables in the tab **Data model**. The column **MID** contains the component id, and **UniFlow ID** the name of the variable in the process to which the value from the request is mapped.
Figure 2. Request mappings
More info: [Passing data to the process](/documentation/documentation-en/budowanie-aplikacji/proces-biznesowy/przekazywanie-danych-do-procesu.md)[ ](/documentation/documentation-en/budowanie-aplikacji/proces-biznesowy/przekazywanie-danych-do-procesu.md)
---
# 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.eximee.com/documentation/documentation-en/budowanie-aplikacji/proces-biznesowy/zadania-uzytkownika/formularz-startowania-sprawy.md?ask=&goal=
```
`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.