> 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/aplikacja-biznesowa/uruchamianie-aplikacji.md).

# Running applications

If you do not want to start by launching the form, but only the application, the first step to perform will be setting **the starting point** of the application (form or process).

## Setting the application's starting point

The application's starting point can be set directly in the module **Applications** – in the tabs **Forms** or **Processes**.

{% hint style="info" %}
For the application to start correctly, it is necessary to first create the data model described in [Data model](/documentation/documentation-en/budowanie-aplikacji/model-danych.md).
{% endhint %}

### Setting a form as the application's starting point (recommended) and launching the application

As the starting point, we can set one of the forms added to a given application. After entering the tab **Forms** we click the context menu of the appropriate form and select the option **Set starting point**:

![Figure 1. Context menu with the option to set the form as the starting point.](/files/4ace97621d9cd66194c482ec627a51734697795b)

{% hint style="warning" %}
Note! After changing the starting form, an "invalidate cache" in webforms may be necessary (if the application has already been run before). To do this, run the following cURL command (replace USER and PASSWORD with the appropriate data):
{% endhint %}

{% code title="Invalidate cache" %}

```bash
curl -u USER:PASSWORD -X POST "http://webforms-dev.consdata.local/cache/invalidate?cacheType=PUBLISHED_TEMPLATE"
```

{% endcode %}

To run the application, e.g. named wiki\_przyklad\_app, use the following link:

```
https://przykladowy.link.demo/stkn=#/wiki_przyklad_app
```

When the application is launched, the **request**, which was set as the starting point, will be opened.

### Setting a process as the starting point and launching the application

{% hint style="info" %}
Availability of functionality depends on the license and may not be available in all deployments.
{% endhint %}

In some cases, the application should start with a process that controls the logic of its operation.

To set a process as the starting point, after entering the tab **Processes** we click the so-called "kebab menu" and in the context menu of the appropriate process select the option **Set starting point**:

![Figure 2. Context menu with the option to set the process as the starting point.](/files/093a719ac7bacd77dd7afa46f3c8a6cc4bea6d57)

If a process is set as the application's starting point instead of a form, additionally in the tab **Properties** of the form, go to the tab **Flows** and in the section [**Actions**](https://wiki.consdata.pl/display/IED/Akcje) define the following event:

* **Component handling the action:** e.g. *Trigger or Page*
* **Event type** *:* *depending on the selected component triggering the change*
* **Form action:** *START\_APPLICATION*
* **Application name:** name of the application to be launched (the application will launch **process** set as the starting point) or the name of the process to be started
* **Redirect to next process step:** condition *JAVASCRIPT* - determines whether automatic redirection to the next step should occur (*user task*); default value: *false.*

![Figure 3. Example of defining the START\_APPLICATION action triggered by clicking the Trigger.](/files/ffa756f80c4467a69a0f56e59092744a5a3dbd87)

*Launching the application will occur after the event handled by the START\_APPLICATION action is triggered.*


---

# 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/aplikacja-biznesowa/uruchamianie-aplikacji.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.