> 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/wlasciwosci-formularza.md).

# Form properties

Tab **Properties** allows configuring parameters related to the behavior, appearance, and interaction of the form during its operation.\
These parameters affect how the form is presented to the user, how it communicates with services, and which interface elements are visible. The properties are grouped into thematic sections.

![Figure 1. Appearance of the "Properties" tab](https://content.gitbook.com/content/2CssJT0zIo4SJQLbSZ6l/blobs/hWaMmDtLmDCuYpcnRCdh/wlasciwosci_1_pliki/image2025-8-13_12-42-21.png)

## **Section "General"**

### **Request description**

A text field that allows you to add a short description or comment to the form project. This description is not shown to the end user, but it makes identification in the repository and team work easier.

### **Entry services**

This section contains a list of services that are attached to the request as entry services. These services will start at the beginning of the request lifecycle, if the activity condition is met. Entry services are executed sequentially, according to their order on the list. In edit mode, it is possible to add and remove an entry service and define the service start condition.

<figure><img src="https://2112972046-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CssJT0zIo4SJQLbSZ6l%2Fuploads%2FsWJgJuNBwLFtyycUnSC7%2Fimage2020-5-19_9-46-27.png?alt=media&amp;token=2e93f258-4372-4177-b20e-28afe8a3cd64" alt=""><figcaption><p><em><strong>Figure 2.</strong> The "Entry services" section with added services</em></p></figcaption></figure>

### **Input parameter mapping services**

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

Section **Input parameter mapping services** allows you to connect services whose task is to **populate form fields** with data before it starts.\
These services are launched automatically **when entering the request** - both during standard opening of the form and in the case of its **unparking** (session resumption) and **resumption of a user task** restored from a draft.

Thanks to these services, for example, you can pass customer data from an external system, set initial field values, or open the request on a specific page. The use of a mapping service to indicate the page of a resumed user task is described on the page [Resuming a user task on a selected page](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/tworzenie-formularza/zapis-tymczasowy/wznowienie-zadania-uzytkownika.md).

#### **Characteristic features of mapping services**

* do not have **output parameters**,
* the result of the service is **directly mapped to form fields or session variables**,
* can specify the page on which the form should open,
* are executed **always first** - even before entry services.

#### Implementation example (ServiceProxy)

To populate a field, the service should return in the map a key that will contain the field identifier on the request and a value that will be assigned to it. Do not define **outputFields** for fields returned from the callService() method. To open the request on a specific page, pass the key `_recentlyRequestedPageMid` to the output map and pass the mid of the appropriate page to it.

The value returned by the service does not overwrite the value of a field restored from a draft or a parked request — such a value is frozen. Details in [Resuming a user task on a selected page](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/tworzenie-formularza/zapis-tymczasowy/wznowienie-zadania-uzytkownika.md).

{% hint style="warning" %}
Mapping services attached to one form cannot return the same key, e.g. `_recentlyRequestedPageMid` or the identifier of the same field. If two services return the same key, the service execution will end with an error and the form will not open. Indicate the starting page in only one service.
{% endhint %}

{% code expandable="true" %}

```java
@Component
@Service(AbstractServiceProxy.class)
public class DemoMappingEntryService extends AbstractServiceProxy {

    private final static String TEXT_FIELD = "GesComplexComponent1.GesTextField1";
    private final static String PAGE_MID = "_recentlyRequestedPageMid";

    public DemoMappingEntryService() {
        this.name = "DemoMappingEntryService";
        this.description = "For test purposes ONLY!";
    }

    @Override
    public List<Map<String, String>> callService(Map<String, List<String>> map)
            throws ServiceProxyException {
        return Collections.singletonList(ImmutableMap.of(
                TEXT_FIELD, "Value passed from the DemoMappingEntryService service",
                PAGE_MID, "Page2"));
    }
}

```

{% endcode %}

{% hint style="info" %}
Demo request: demoInputParameterMappingService
{% endhint %}

### **Exit services**

This section contains a list of services that are attached to the request as final services. These services will start before the end of the request lifecycle, if the activity condition is met.

### **Statistics**

This section contains options related to collecting statistics from the request. For each request, it is possible to define which statistics should be collected and how often.

#### External statistics

Additionally, in the Statistics section you can enable exporting Google Tag Manager statistics. You can read about the functionality itself in the GTM documentation: [GTM statistics](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/tworzenie-formularza/statystyki-gtm.md).

## **Section "Appearance"**

This section is responsible for configuring interface elements visible while the request is being filled out.

### **Side and bottom panel**

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

Allows you to enable or disable the visibility of additional panels (e.g. a side menu with information, notifications, or content blocks). Panels can be used to present useful links or cross-sell elements.

Artifacts of type can be attached to panels [Content (TextContent)](https://github.com/Consdata/eximee-docs/tree/main/budowanie-aplikacji/interfejs-uzytkownika/formularze/biblioteka-komponentow-bazowych/tresc-textcontent/README.md), selected from the repository. Editing the panel (adding a visibility condition, listeners, styles, or selecting a slot) requires clicking the pencil icon, and saving changes requires clicking the save symbol. The placement of the added content is determined by the option **Slot**. Panels allow you to define multiple pieces of content that will be displayed one below another.

<figure><img src="https://2112972046-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CssJT0zIo4SJQLbSZ6l%2Fuploads%2Fj0KUe4JyO7c1HxLUk1oA%2Fimage2020-6-1_12-29-55.png?alt=media&amp;token=b607ce42-8af1-4ffe-a3f5-f92f97c396da" alt=""><figcaption><p><em><strong>Figure 3</strong></em><strong>.</strong> <em>Side and bottom panel - example of content definition</em></p></figcaption></figure>

<figure><img src="https://2112972046-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CssJT0zIo4SJQLbSZ6l%2Fuploads%2FElN4b8mH3IFrwkdu4rAf%2Fimage2025-6-17_13-20-39.png?alt=media&amp;token=0972dafd-723e-40b9-b480-cf5e1b4c26eb" alt=""><figcaption><p><em><strong>Figure 4.</strong> Example appearance of the side panel on the request</em></p></figcaption></figure>

The content of the bottom panel is determined by setting the Slot option to the appropriate value, which depends on the deployment.

<figure><img src="https://2112972046-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CssJT0zIo4SJQLbSZ6l%2Fuploads%2Fgit-blob-87035cd54c3895aa37549376c397a233c1575be9%2Fimage2025-12-16_10-09.png?alt=media" alt=""><figcaption><p><em><strong>Figure 5</strong></em><strong>.</strong> <em>Example appearance of the bottom panel on the request</em></p></figcaption></figure>

### **Step visibility**

Controls the display of the top horizontal progress bar (the so-called [form steps](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/tworzenie-formularza/kroki-i-strony-formularza.md)). Its hiding can be used in single-page requests or simplified processes.

In this section you can define the visibility condition of the step bar and indicate the elements that trigger this change (the so-called listening to elements).

<figure><img src="https://2112972046-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CssJT0zIo4SJQLbSZ6l%2Fuploads%2F7BTICP2XvEjmBs7C2B1f%2Fimage2022-12-16_9-24-12.png?alt=media&amp;token=3d9fc765-b6c6-451a-ad30-ff118f2e52af" alt=""><figcaption><p><em><strong>Figure 6</strong></em><strong>.</strong> <em>Example of a defined condition</em> <em>step bar visibility</em></p></figcaption></figure>

<figure><img src="https://2112972046-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CssJT0zIo4SJQLbSZ6l%2Fuploads%2FXRmeJ9SYgAy0jrMaKNCJ%2Fobraz.png?alt=media&amp;token=e31625db-f56a-4d4a-bd18-d081096e512a" alt=""><figcaption><p><em><strong>Figure 7</strong></em><strong>.</strong> <em>Example steps on the request</em></p></figcaption></figure>

### **Visibility of the navigation bar/button**

**Navigation bar visibility** allows you to determine whether the bottom navigation bar (with the Back/Next/Send buttons) should be visible. Whereas in the section **Navigation button visibility** only the condition for showing the Next/Send button is specified. In both sections, remember to also indicate the elements that trigger the given change (so-called listening).

<figure><img src="https://2112972046-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CssJT0zIo4SJQLbSZ6l%2Fuploads%2FvCnhwShG78etwpmPvfKh%2FZaznaczenie_656.png?alt=media&amp;token=a15ca3d7-390c-40ec-b36e-246d68459fd4" alt=""><figcaption><p><em><strong>Figure 8.</strong></em> <em>Section</em> "<em>Navigation button visibility"</em></p></figcaption></figure>

{% hint style="warning" %}
The currentPageId variable is not supported. For proper operation of navigation button visibility, the currentPageMid variable should be used
{% endhint %}

### **Visibility of additional header element**

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

Allows displaying an additional element in the first position of the page header (e.g. an icon, a button propagating an action). The type of element displayed may vary depending on the deployment and its presence is not guaranteed in all implementations.

### **Bottom Bar**

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

Determines whether the form footer is presented to the user. It can be conditionally hidden - e.g. on information or summary pages.

### **Panic Button (FAB)**

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

Specifies whether the floating button on the request page that opens an additional window (FAB - *Floating Action Button*) should be visible on the form.

#### **Visibility**

The button visibility is set in the subsection **Visibility**, where the condition for showing the button and the element that should trigger this change is defined (*listening*). This way, the button can be visible only in specific situations, e.g. after selecting a field or at a given step of the request.

#### **Masking the phone number**

In the section **Masking** you can define whether the phone number in the button popup should be masked (e.g. partially hidden). The visibility of the number is determined by a condition and listening to the element that triggers the change.

#### **Additional settings**

In the subsection **Additional data** you can indicate form components whose values will be passed to the button configuration - phone number, id, or configuration version. This option is available only in selected deployments.

<figure><img src="https://2112972046-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CssJT0zIo4SJQLbSZ6l%2Fuploads%2FIGrehtphmhi7rUrg7sRN%2Fimage2021-7-23_13-49-29.png?alt=media&amp;token=1f7d6503-41b5-406c-bac3-eb533568773b" alt=""><figcaption><p><em><strong>Figure 9</strong></em><strong>.</strong> <em>Visibility of the "Panic Button" section with set conditions and parameters</em></p></figcaption></figure>

#### **Technical configuration**

The size and position of the browser window, as well as the website address it leads to, are defined for a given installation in the webforms.xml configuration file. Example values:

```xml
<floatingActionButton>
    <windowPositionX>100</windowPositionX>
    <windowPositionY>100</windowPositionY>
    <windowSizeX>100</windowSizeX>
    <windowSizeY>100</windowSizeY>
    <actionLink>http://consdata.pl</actionLink>
</floatingActionButton>
```

**Configuration parameters:**

* *windowPositionX* – distance of the window from the left edge (px)
* *windowPositionY* – distance of the window from the top (px)
* *windowSizeX* – window width (px)
* *windowSizeY* – window height (px)
* *actionLink* – address of the website opened in a new window; it may contain form variables available when the request starts, e.g.:

```
<actionLink>http://consdata.pl?nazwawniosku=${formId}&numerwniosku=${formInstanceNumber}</actionLink>
```

#### **Translations and text keys**

The labels on the component can be customized by adding translations in the main form template:

<table><thead><tr><th width="423">Translation key</th><th>Description</th><th>Default content</th></tr></thead><tbody><tr><td><code>iew.fab.need.help</code></td><td>title in the startup popup</td><td>"Need help?"</td></tr><tr><td><code>iew.fab.well.call.up</code></td><td>description in the startup popup</td><td>"We'll call you back as soon as possible..."</td></tr><tr><td><code>iew.fab.order.call</code></td><td>button text in the startup popup</td><td>"Order contact"</td></tr><tr><td><code>iew.fab.thank.you.title</code></td><td>title in the thank-you popup</td><td>"We will call you back soon"</td></tr><tr><td><code>iew.fab.thank.you.desc</code></td><td>description in the thank-you popup</td><td><em>""</em></td></tr><tr><td><code>iew.fab.error.could.not.order.conversation.title</code></td><td>title in the error popup</td><td>"Could not order a call"</td></tr><tr><td><code>iew.fab.error.try.again.desc</code></td><td>description in the error popup</td><td>"Try again in a moment"</td></tr></tbody></table>

{% hint style="info" %}
Demo requests: demoFab, demoFabChangedLetter
{% endhint %}

### **Loading progress style**

Defines how the loading indicator is displayed during form initialization. The default value is "preloader". Available styles may vary depending on the graphic theme (e.g. progress bar, spinner, logo animation).

### **Conditional request titles**

Allows defining different titles displayed in the form header depending on whether certain conditions are met. Each title has an assigned **visibility condition** (e.g. data-dependent), so the header can be changed dynamically depending on the request stage or user role.

#### **Title definition**

Each title definition is presented in a separate table row. A given row contains:

* **Title key** – translation identifier or fixed text displayed in the form header,
* **Visibility condition** – logical expression specifying when the title should be used,
* **Elements triggering change (listening)** – list of components or variables (separated by commas) whose change causes the condition to be re-evaluated,
* **Edit and delete buttons** – allow modification or deletion of the title definition row,
* **Save button** – visible while editing the row; saves the changes made,
* **Reorder handle** – allows you to drag the title and set its priority (order of checking conditions).

{% hint style="info" %}
Rows are processed **from top to bottom**, so if multiple conditions are met, the title from the highest row will be displayed.
{% endhint %}

<figure><img src="https://2112972046-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CssJT0zIo4SJQLbSZ6l%2Fuploads%2F2LK037YnSb4MxaY2cgad%2Fimage2025-7-10_8-25-44.png?alt=media&amp;token=862e3ec6-6c67-43de-9ed5-20a467167734" alt=""><figcaption><p><em><strong>Figure 10.</strong> Example of four conditional titles defined</em></p></figcaption></figure>

{% hint style="warning" %}
If the change of the request title depends on moving between pages, then use the variable *currentPageMid*. This will allow the title to change both when moving to the next page and when going back.
{% endhint %}

{% hint style="info" %}
Demo request: demoFormTitles
{% endhint %}

{% hint style="info" %}
Demo request: demoRequestTemplateProperties
{% endhint %}


---

# 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/wlasciwosci-formularza.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.
