> 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/punkt-zapisu-wniosku-i-mechanizm-ostatnich-stron.md).

# Request save point and last page mechanism

## **Application save point**

**Application save point** is a key element of the form workflow in the Eximee system. It defines when application data is transferred to the form repository and related actions are triggered—such as starting a BPMN process, saving data to an external system, or displaying final information pages to the user.\
It is configured in the **Steps** tab of the application editor and appears as one of the items in the form step sequence. It is most often placed as the **last step of the application**. All pages in steps **after** the application save point are treated as **completion pages**.

![Figure 1. Application save point view in the "Steps" tab](https://content.gitbook.com/content/2CssJT0zIo4SJQLbSZ6l/blobs/ESdWNrbU8OZ7NoyGyZfd/zapis_koncowy_pliki/image2025-6-6_11-49-47.png)

When the application progresses past this point, it is saved to the form repository along with all the data entered in it.

### Properties of the application save point step

The **Application save point** step has the following properties:

* it can be moved anywhere **by dragging and dropping** using the *drag & drop* mechanism in the step structure,
* **it cannot be deleted**, because it is an integral part of the template,
* **pages cannot be placed in it** —it serves a technical rather than visual function.

### Configuring the application save point

When the application passes the save point, the system saves the data.\
To start a BPMN process at this point, add the **Application save point** element **EximeeRouter2**.

Configure this element by specifying:

* **Process name** —the BPMN process definition key (matching the process identifier in EximeeBPMS).
* **Business key** —the application's business identifier. It can reference a form component or a session variable containing a unique case number.\
  If this field is left blank, the system automatically uses the application number as the business key.\
  The case number must be unique: if another case already has that number, even a completed one, the platform refuses to start the process and the form displays an error page—see [Case Number Uniqueness](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/proces-biznesowy/unikalnosc-numeru-sprawy.md).

![Figure 2. Application save point view with an EximeeRouter2 process attached](https://content.gitbook.com/content/2CssJT0zIo4SJQLbSZ6l/blobs/bvDzl9ibkT3v0En0rOiN/zapis_koncowy_pliki/image2025-6-6_13-54-8.png)

Example XML configuration in the form's **Source** tab:

```
<saveActions>
  <action xsi:type="eximeeWorkflow">
    <processDefinitionKey>nazwa_procesu</processDefinitionKey>
    <businessKeyMapping>numer_sprawy</businessKeyMapping>
  </action>
</saveActions>
```

Setting these parameters causes the system to do the following when the application passes the save point:

1. Save the form data to the repository (FormStore),
2. Start a BPMN process in the **EximeeBPMS**,
3. Passes data from the form to the process according to the mapping in the **Data Model**.

## Final pages mechanism

After the application save point is passed, the system displays the so-called **final pages of the application** — the final screens shown after the form is submitted. If no completion pages are configured, the system automatically displays the default thank-you page defined at the Forms application level.

Completion pages can be used to:

* display a submission confirmation message (e.g. a thank-you message or reference number),
* provide information about the next steps in the process,
* invoke additional services or validators.

Characteristics of final pages:

* data from completion pages **is not saved** **in the repository** along with data collected from standard application pages,
* components on completion pages **work like regular components**, and can perform validations, invoke services, or display dictionary data,
* after submitting the application and moving to the completion pages, the user **cannot return to previous pages**,
* **the application cannot be parked** after it has been submitted,
* after passing through the completion pages, the application **is not added to the pool of abandoned applications**,
* completion steps work in the same way as regular steps, and their basic properties can be defined according to the [instructions](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/tworzenie-formularza/kroki-i-strony-formularza.md).

### Defining the final pages of an application

The process for creating final pages is similar to that for defining regular form pages.\
The only difference is their **position** — they must be placed in a step **below the Application Save Point**.

The illustration below shows the steps in an example application template. This template contains:

* three application pages placed in the steps **Step1** and **Step2**
* **an Application Save Point** that determines where the thank-you page appears,
* one completion page in the step **Step3**.

![Figure 3. Example steps with a thank-you page](https://content.gitbook.com/content/2CssJT0zIo4SJQLbSZ6l/blobs/C0690OaxMdckY5u2ZaOq/punkt_zapisu_pliki/image2024-9-27_13-29-32.png)

All pages placed in steps located below the **Application Save Point** are treated as completion pages.


---

# 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/punkt-zapisu-wniosku-i-mechanizm-ostatnich-stron.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.
