> 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/changelog/changelog-en/readme.md).

# Changelog

{% updates format="full" %}
{% update date="2026-11-06" %}

## Suggesting data model keys in list notation

{% hint style="info" %}
Eximee Platform version: `4.1230.0` and `3.876.0`
{% endhint %}

Field **Data model key** in the form editor suggests data model keys in list notation, e.g. `klient.adresy[].miasto`, and the selected suggestion can be edited further, e.g. by entering an index in brackets. More information in the documentation: [Data model on the interface](https://docs.eximee.com/budowanie-aplikacji/interfejs-uzytkownika/formularze/praca-z-komponentami-bazowymi/model-danych-na-interfejsie)
{% endupdate %}
{% endupdates %}

{% updates format="full" %}
{% update date="2026-11-06" %}

## Text Area component height in properties

{% hint style="info" %}
Eximee Platform version: `4.1230.0` and `3.876.0`
{% endhint %}

In the properties of the Text Area (TextArea) component, in the section **Styling**, field **Height (px)** for setting the minimum height of the field in the application without manually editing the source. The feature is available only in specific deployments. More information in the documentation: [Text Area - TextArea](https://docs.eximee.com/budowanie-aplikacji/interfejs-uzytkownika/formularze/biblioteka-komponentow-bazowych/1-wprowadzanie-danych-inputs/obszar-tekstu-textarea#wysokosc-pola)
{% endupdate %}
{% endupdates %}

{% updates format="full" %}
{% update date="2026-11-06" %}

## Form authorization in form properties

{% hint style="info" %}
Eximee Platform version: `4.1228.0`
{% endhint %}

A section has been added in the form properties **Form authorization** for setting the condition and parameters of application authorization with an OTP code or mobile token without manually editing the source. The availability of the functionality depends on the license. More information in the documentation: [Form authorization](https://docs.eximee.com/budowanie-aplikacji/logika-biznesowa/przeplywy/autoryzacja-formularza#konfiguracja-autoryzacji)
{% endupdate %}
{% endupdates %}

{% updates format="full" %}
{% update date="2026-11-06" %}

## Extension of the PIN control with the ability to choose the number of fields

{% hint style="info" %}
Eximee Platform version: `4.1198.0`
{% endhint %}

The ability to set the number of fields in the PIN control from 4 to 8 has been added. The feature is available only in specific deployments. More information in the documentation: [PIN component - PinField](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/biblioteka-komponentow-bazowych/1-wprowadzanie-danych-inputs/komponent-pin-pinfield)
{% endupdate %}
{% endupdates %}

{% updates format="full" %}
{% update date="2026-10-22" %}

## Statement document in the Service-fed Statements component

{% hint style="info" %}
Eximee Platform version: `4.1199.0` and `3.853.0`
{% endhint %}

The service feeding the Service-fed Statements component (FedStatements) can specify in the statement, including a subordinate one, a document from an external source with the attributes `documentSource` and `externalDocumentId`, and optionally the name of the downloaded file in `documentFileName`. The platform downloads the document on the server side, and the document identifier does not reach the browser. Selected skins display, in place of the button expanding the description, a link to download the document with the label `showMoreTextLabel` (default: "Download document"). Clicking the link does not change the statement selection. A service that does not return new fields works as before. More information in the documentation: [Statement document](https://docs.eximee.com/budowanie-aplikacji/interfejs-uzytkownika/formularze/biblioteka-komponentow-bazowych/7-komponenty-specjalne/oswiadczenia-statements/oswiadczenia-zasilane-z-uslugi-fedstatements#dokument-oswiadczenia)
{% endupdate %}
{% endupdates %}

{% updates format="full" %}
{% update date="2026-10-19" %}

## Content selection in the properties of the Rollable Rich Text and Radio components

{% hint style="info" %}
Eximee Platform version: `4.1190.0` and `3.850.0`
{% endhint %}

In the properties of the Rollable Rich Text and Radio components, a field has been added **Content**, working the same as in the Rich Text component. Selecting the artifact **Content** sets the external data source *TextContentService*, so the service no longer has to be configured manually in the section **Interactions** or in the application source. In the Radio component, the selected content becomes the field label. The preview of the Rollable Rich Text component in Designer shows the selected content. More information in the documentation: [Rollable Rich Text - RollableTextContent](https://docs.eximee.com/budowanie-aplikacji/interfejs-uzytkownika/formularze/biblioteka-komponentow-bazowych/4-tresci/tresc-formatowana-zwijana-rollabletextcontent#podpiecie-w-komponencie-zrodla-tresci), [Radio](https://docs.eximee.com/budowanie-aplikacji/interfejs-uzytkownika/formularze/biblioteka-komponentow-bazowych/2-pola-wyboru/radio)

## Variables and Wiki Markup in the Radio label fed from Content

{% hint style="info" %}
Eximee Platform version: `4.1190.0`
{% endhint %}

Fixed the Radio component fed with content from the service: the label and description once again have variable values substituted, e.g. `${GesTextField1}`, and when the property is enabled **Formatting with Wiki Markup** Wiki Markup tags are converted to HTML. Text from the service takes precedence over translation of the property **Field text label**. More information in the documentation: [Radio](https://docs.eximee.com/budowanie-aplikacji/interfejs-uzytkownika/formularze/biblioteka-komponentow-bazowych/2-pola-wyboru/radio)
{% endupdate %}
{% endupdates %}

{% updates format="full" %}
{% update date="2026-10-15" %}

## Sub-statements in the Service-fed Statements component

{% hint style="info" %}
Eximee Platform version: `4.1184.0` and `3.848.0`
{% endhint %}

The service feeding the Service-fed Statements component (FedStatements) can return in the statement a list of `subStatements` with subordinate statements (one nesting level). A subordinate statement cannot be selected until the parent statement is selected, and deselecting the parent deselects its subordinate statements. The requiredness of a subordinate statement applies only when the parent is selected. The flag `descriptionBelowSubStatements` moves the description of the parent statement below its last subordinate statement. The hierarchy is shown by selected skins, while the others show statements from both levels as a single list. A service that does not return new fields works as before. More information in the documentation: [Sub-statements](https://docs.eximee.com/budowanie-aplikacji/interfejs-uzytkownika/formularze/biblioteka-komponentow-bazowych/7-komponenty-specjalne/oswiadczenia-statements/oswiadczenia-zasilane-z-uslugi-fedstatements#oswiadczenia-podrzedne)
{% endupdate %}
{% endupdates %}

{% updates format="full" %}
{% update date="2026-10-15" %}

## Document window height in the PdfViewer component

{% hint style="info" %}
Eximee Platform version: `4.1183.0` and `3.849.0`
{% endhint %}

The PdfViewer component now allows setting the document window height separately for desktop and mobile. More information in the documentation: [Document window height](https://docs.eximee.com/budowanie-aplikacji/interfejs-uzytkownika/formularze/biblioteka-komponentow-bazowych/5-dokumenty-i-zaloczniki/podglad-pdf-pdfviewer#wysokosc-okna-dokumentu)

## Document from an external source in the PdfViewer component

{% hint style="info" %}
Eximee Platform version: `4.1183.0` and `3.849.0`
{% endhint %}

The following fields have been added to the PdfViewer component **Document source** and **Document identifier**. The component can display a document from an external source configured in the installation, specified directly by identifier or via a session variable. The document is downloaded on the server side, and the document identifier does not reach the browser. Changing the identifier loads a new document, and an empty identifier does not interrupt filling out the application. The list of sources is determined by the Designer configuration key `eximee.console.pdf-viewer.document-sources`; without configured sources, the fields are hidden and the component works as before with the field **Link to PDF**. More information in the documentation: [Document from an external source](https://docs.eximee.com/budowanie-aplikacji/interfejs-uzytkownika/formularze/biblioteka-komponentow-bazowych/5-dokumenty-i-zaloczniki/podglad-pdf-pdfviewer#dokument-ze-zrodla-zewnetrznego)
{% endupdate %}
{% endupdates %}

{% updates format="full" %}
{% update date="2026-10-15" %}

## Automatic removal of translation keys together with the application element

{% hint style="info" %}
Eximee Platform version: `4.1183.0` and `3.846.0`
{% endhint %}

Deleting a component, page, step, validator, service, or component item (context help, dynamic section title, dynamic button labels) in the application editor also deletes its translation keys in all application languages. A key used by another application element remains, and the editor lists it in the message. Validator error keys and service message keys disappear only together with the last validator or service that declares them. A key entered only in a condition or script does not protect the key from deletion. One undo (**Ctrl+Z**) restores the element together with its keys and their texts. Until the keys are calculated, the editor is locked and shows a progress indicator. More information in the documentation: [Deleting keys together with the application element](https://docs.eximee.com/budowanie-aplikacji/interfejs-uzytkownika/formularze/tworzenie-formularza/tlumaczenia/usuwanie-kluczy-razem-z-elementem-wniosku)
{% endupdate %}
{% endupdates %}

{% updates format="full" %}
{% update date="2026-10-14" %}

## Eximee internal redirects

{% hint style="info" %}
Eximee Platform version: `3.845.0`
{% endhint %}

The ability to mark a redirect in navigation actions and in the REDIRECT action as an Eximee internal redirect has been added. For such a redirect, the platform appends environment-configured parameters to the address, for example the input source or channel. Parameters already present in the address are not overwritten, and parameters without a value are not appended. The availability of the functionality depends on the license. More information in the documentation: [Eximee internal redirects](https://docs.eximee.com/eksploatacja-aplikacji/webforms/konfiguracja/przekierowania-wewnetrzne)
{% endupdate %}
{% endupdates %}

{% updates format="full" %}
{% update date="2026-08-19" %}

## The way data model tree branches are collapsed has been changed

{% hint style="info" %}
Eximee Platform version: `4.1055.0`
{% endhint %}

The way data model tree branches are collapsed has been changed. Clicking an item expands it, but there is an option to collapse the branch using a separate button. More information in the documentation: [Data model structure](https://docs.eximee.com/budowanie-aplikacji/model-danych/edycja-modelu-danych#struktura)

## Word wrap in the Monaco editor has been fixed

{% hint style="info" %}
Eximee Platform version: `4.1052.0`
{% endhint %}

Word wrap in the Monaco editor has been fixed for the Script Tasks, Formatter, Kafka Consumers tabs.
{% endupdate %}
{% endupdates %}

{% updates format="full" %}
{% update date="2026-08-18" %}

## Displaying the PageService condition

{% hint style="info" %}
Eximee Platform version: `4.1045.0`
{% endhint %}

Fixed displaying the full PageService condition in Designer when working in read-only mode.
{% endupdate %}
{% endupdates %}

{% updates format="full" %}
{% update date="2026-08-13" %}

## Line wrapping in the Monaco editor

{% hint style="info" %}
Eximee Platform version: `4.1039.0`
{% endhint %}

Automatic line wrapping has been added in the Monaco editor. The change mainly affects the "Source" tab in the Designer editor.
{% endupdate %}
{% endupdates %}

{% updates format="full" %}
{% update date="2026-08-13" %}

## Auto-formatting on script save

{% hint style="info" %}
Eximee Platform version: `4.1037.0`
{% endhint %}

Automatic script formatting on save has been added for artifacts such as script validators, script tasks, Kafka consumers, formatters, custom components, content, and emails.
{% endupdate %}
{% endupdates %}

{% updates format="full" %}
{% update date="2026-08-12" %}

## Displaying the description of the data model key when selecting a key

{% hint style="info" %}
Eximee Platform version: `4.1030.0`
{% endhint %}

Displaying the description of the data model key when selecting. If the key has no description, the data model key is shown again. If a custom value is entered, the information "Constant value" is displayed.
{% endupdate %}
{% endupdates %}

{% updates format="full" %}
{% update date="2026-08-11" %}

## Ability to change the order of fields in the data model tree

{% hint style="info" %}
Eximee Platform version: `4.1027.0`
{% endhint %}

The ability to change the order of fields at one level in the data model tree has been added. Changing the order does not affect the logic. Reordering is possible while working on the draft version of the data model. More information in the documentation: [Data model structure](https://docs.eximee.com/budowanie-aplikacji/model-danych/struktura-modelu-danych)
{% endupdate %}
{% endupdates %}

{% updates format="full" %}
{% update date="2026-08-07" %}

## Searching base components by technical name

{% hint style="info" %}
Eximee Platform version: `4.1023.0`
{% endhint %}

Searching base components in the designer palette is also done by technical names (e.g. GesText).
{% endupdate %}
{% endupdates %}

{% updates format="full" %}
{% update date="2026-08-06" %}

## Selecting a data model key from a list

{% hint style="info" %}
Eximee Platform version: `4.1013.0` and `3.781.0`
{% endhint %}

The ability to select a data model key from a drop-down list has been added. If there is no suitable key, it can be defined manually. More information in the documentation: [Selecting a data model key from a list](https://docs.eximee.com/budowanie-aplikacji/interfejs-uzytkownika/formularze/praca-z-komponentami-bazowymi/model-danych-na-interfejsie)
{% endupdate %}
{% endupdates %}

{% updates format="full" %}
{% update date="2026-07-31" %}

## Information about the set starting point

{% hint style="info" %}
Eximee Platform version: `4.1007.0` and `3.779.0`
{% endhint %}

If any application or process is the starting point of the application, information is displayed in the form of a tag with a flag and the text "Starting point" More information in the documentation: [Starting the application](https://docs.eximee.com/budowanie-aplikacji/aplikacja-biznesowa/uruchamianie-aplikacji)
{% endupdate %}
{% endupdates %}

{% updates format="full" %}
{% update date="2025-12-19" %}

## Data model data sources editor in Eximee Designer

{% hint style="info" %}
Eximee Platform version: `4.355.0`
{% endhint %}

In Eximee Designer, we have made it possible to browse, add, and edit data sources in the data model. Additionally, sources can now be attached directly to fields and objects from the Structure tab.

The new data sources editor uses a convenient two-column layout: the list of sources is on the left, and the details of the selected source are on the right. It allows defining the key, documentation, parameters, output mapping, and JavaScript code.

We have also expanded the data model editor itself. Adding fields works contextually for the ROOT and individual nodes, and newly added elements appear at the top of the list. We have also introduced key validation and a virtual ROOT tile, which makes it easier to start working with an empty model.

The application view also now includes an option to create a data model and automatically attach it to the application, without the need for manual technical operations.

More information in the documentation: [Data sources editor](https://docs.eximee.com/budowanie-aplikacji/model-danych/edycja-modelu-danych#zrodlo-danych)
{% endupdate %}
{% endupdates %}

{% updates format="full" %}
{% update date="2025-12-05" %}

## Exporting a process diagram to an image file

{% hint style="info" %}
Eximee Platform version: `4.348.0`
{% endhint %}

In Eximee Designer, it is now possible to **download the BPMN diagram as an image with one click**.\
This is a quick way to enrich documentation, presentations, or workshop materials — regardless of the project stage.

#### Analytical use cases

Regardless of the project phase: from early discussions and shaping the vision to finalizing the last details in implementation, a process diagram can greatly facilitate communication. A graphic of the process can supplement formal documentation or support discussions during workshops.

<figure><img src="https://2158968046-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FanLdWm8RCwjgOhBGbmDM%2Fuploads%2FrVdrk6xVfcDHFEZp4A9c%2Fselect%2025-12-05%2012-11-44.png?alt=media&amp;token=a3251f6c-99db-419a-8e39-a6dfad155129" alt=""><figcaption><p>BPMN process preview with the option to download the graphic</p></figcaption></figure>

It has long been possible to model processes in Eximee Desinger. Even at the early stages of analysis. Now Eximee Designer has a convenient button that lets you download an image you can use anywhere.

More information in the documentation: [Exporting the process to an SVG image](https://docs.eximee.com/budowanie-aplikacji/proces-biznesowy/tworzenie-procesu-biznesowego-w-bpmn-2.0#tworzenieimodyfikacjaprocesu-eksportprocesudoobrazusvg)
{% endupdate %}
{% endupdates %}


---

# 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/changelog/changelog-en/readme.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.
