# Case start form

**Case initiation form** plays a key role in launching the workflow process, as it serves as the starting point of the entire workflow. It is used by the user to initiate a new case (that is, 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 information required to correctly start and direct the workflow—for example, applicant data, a description of the problem, or attachments. Thanks to this, the system can 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, completeness, and quality of data.

## Association of the form with the case type

We attach the process definition to the form in the **Steps** tab of the application editor, in the section **Application save point,** by adding the **EximeeRouter2** element and setting in it:

* **Process name** - process definition key, that is, 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**is not filled in, it will take the value of the request number.

Configuring this panel results in the integrated process being started after passing the application save point.

<figure><img src="/files/8915a4851e796655ebb59f189ec986bc07e683b3" alt=""><figcaption><p><em><strong>Figure 1.</strong> Configured application save point</em></p></figcaption></figure>

## Starting the process instance and redirecting to the user task

It is possible to simultaneously save the application, start the process instance, and redirect the user to the next task. To do this, add a component to the application, e.g. [Trigger](/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/biblioteka-komponentow-bazowych/6-interakcje-i-akcje/trigger.md). Then, in the artifact properties, define the action **`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 application to the process

To pass data from the application to the process, it is necessary to add the session variable *use-model-mapping* and set its value to *true*. Then we map data from the application fields to variables in the process in the **Data model**tab. **Mid** column contains the component id, and **UniFlow ID** the name of the variable in the process to which the value from the application is mapped.

<figure><img src="/files/328e6b8ddc1a32d1fc37e8fb3fa0c4308662ff40" alt=""><figcaption><p><em><strong>Figure 2.</strong> Mappings on the application</em></p></figcaption></figure>

More info: [Passing data to the process](/documentation/documentation-en/budowanie-aplikacji/proces-biznesowy/przekazywanie-danych-do-procesu.md)[<br>](/documentation/documentation-en/budowanie-aplikacji/proces-biznesowy/przekazywanie-danych-do-procesu.md)


---

# Agent Instructions: 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:

```
GET https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/proces-biznesowy/zadania-uzytkownika/formularz-startowania-sprawy.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.