> 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/interfejs-uzytkownika/formularze/tworzenie-formularza/prefiks-numeru-wniosku.md).

# Application number prefix

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

## Introduction

Each new application instance receives an application number, available in the predefined session variable `formInstanceNumber`. The number consists of a prefix and a numeric part, e.g.:

`EXI000000052251`

* `EXI` - prefix,
* `000000052251` - numeric part assigned by the number generator.

The number is unique within the prefix in a given environment. Therefore, applications can exist simultaneously `XYZ000000052251` and `ABC000000052251`, but the number `ABC000000052251` will never be generated again.

## Where does the prefix come from

The prefix can come from three places:

| Where                                                                                                  | Who can change                                     |
| ------------------------------------------------------------------------------------------------------ | -------------------------------------------------- |
| Session variable `FormInstanceNumberPrefix` on the application's start form, in Designer               | lowcode developer                                  |
| Service parking configuration file in the deployment configuration repository (list `formDefinitions`) | person with access to the configuration repository |
| Other deployment server settings                                                                       | deployment administrator                           |

A deployment administrator is a person or team responsible for configuring the platform in a given deployment, e.g. the platform team or administrators on the bank's side.

If the prefix is not set, the platform assigns a default prefix, dependent on the deployment - e.g. `EXI` or the first three characters of the form name, written in uppercase.

## Setting the prefix from lowcode

1. Open the business application start form in Designer (application entry point).
2. In the tab **Application** choose in the left menu the option **Session variables** (see [Managing session variables](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/zmienne-sesyjne/zarzadzanie-zmiennymi-sesyjnymi.md)).
3. Click **Add session variable** and in the column **Mid** enter `FormInstanceNumberPrefix`. If the variable already exists, find it in the list.
4. In the column **Default value** enter the prefix, e.g. `RKL`.
5. Save the form.
6. Run the application and check the application number.

<figure><img src="https://2112972046-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CssJT0zIo4SJQLbSZ6l%2Fuploads%2Fgit-blob-ea7b76f8918d965a11677af26f8d24c45b0efb53%2FFormInstanceNumberPrefix1.png?alt=media" alt="Zmienna sesyjna FormInstanceNumberPrefix z wartością domyślną RKL"><figcaption><p><em><strong>Figure 1.</strong> Session variable FormInstanceNumberPrefix with default value RKL</em></p></figcaption></figure>

Example: with the value set `RKL` the number will change from `EXI000000052251` to `RKL000000052251`. After deleting the variable (or leaving it blank), new applications will again receive the default prefix.

{% hint style="warning" %}
Variable `FormInstanceNumberPrefix` works only in deployments where the platform reads it. If after launching the application the number still has the current prefix, the prefix in that deployment is set on the platform side (see [When the prefix is configured by the platform](#kiedy-prefiks-konfiguruje-platforma)). The variable does not report an error - it is simply ignored.
{% endhint %}

The variable's value is read once, at the moment the application instance is created. Changing the prefix does not change the numbers of applications that already exist.

## When the prefix is configured by the platform

The prefix is defined in the platform settings, not in lowcode, when:

* **the number passed to an external institution must have a specific format** - it is assigned according to the platform configuration and may have a different prefix than the application number in Eximee. The prefix of the number in Eximee can be defined both in the platform configuration and using a variable on the form - before changing, check where it comes from;
* **deployment assigns the prefix based on the form name** - the prefix comes from the entry assigned to the form in the server configuration, and if such an entry does not exist, from the first three letters of the form name (e.g. form `changeAddress` gets prefix `ZMI`). The variable `FormInstanceNumberPrefix` is then ignored, and the prefix is changed by the deployment administrator;
* **the application is launched by the parking service** - in some deployments the service creates the application before the client opens it. The prefix then comes from the configuration of that service, which must take into account the given application to allow it to be launched.

{% hint style="info" %}
Creating an application by the parking service is a separate operation from [parking and unparking the application](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/tworzenie-formularza/zapis-tymczasowy/parkowanie-i-odparkowanie-wnioskow.md), i.e. saving and resuming the started session. The prefix assigned when creating the application is not related to temporary saving.
{% endhint %}

## Rules for determining the prefix

* The prefix should have **3 uppercase letters**.
* The prefix should derive from the **Polish name of the process**, e.g.:
  * `RKL` - ROR Logged-in Client,
  * `PPW` - Salary Transfer Process.
* The prefix should be **unambiguous and unique within the environment (system)**. Two applications with the same prefix share one counter, and from the number it cannot be determined which application the application comes from.
* Each lowcode process should have its own prefix, instead of using the default one `EXI`. It should also not use prefixes reserved for applications requiring a specific number format. The list of used prefixes can be obtained from the deployment administrator.
* The prefix should be agreed with the business already at the process analysis stage. Its later change does not affect numbers of existing applications, which may matter for reports, case search and integrations.

## Related pages

* [Predefined session variables](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/zmienne-sesyjne/predefiniowane-zmienne-sesyjne.md) - variable `formInstanceNumber` with application number
* [Managing session variables](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/zmienne-sesyjne/zarzadzanie-zmiennymi-sesyjnymi.md) - adding a variable and setting a default value
* [Form, process and data model identifiers](https://docs.eximee.com/documentation/documentation-en/zarzadzanie-aplikacja-biznesowa/testowanie-i-debugowanie-aplikacji/audyt-aplikacji-biznesowej/identyfikatory-formularza-procesu-i-modelu-danych.md) - application number as an identifier in the audit
* [Passing data to the process](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/proces-biznesowy/przekazywanie-danych-do-procesu.md) - application number as `businessKey` process


---

# 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/interfejs-uzytkownika/formularze/tworzenie-formularza/prefiks-numeru-wniosku.md?ask=<question>&goal=<user_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.
