> 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/zapis-tymczasowy/zmienna-sesyjna-wasparked.md).

# Session variable wasParked

To check on the application whether the application was previously saved temporarily, we add to the session variables ***wasParked*** (this variable is set automatically by the platform when the application is resumed):

<figure><img src="/files/bc9e6238c80ba2a8125d1530ceb1284d4e712eaf" alt=""><figcaption><p><em><strong>Figure 1.</strong> The wasParked variable in Eximee Designer</em></p></figcaption></figure>

## How it works *wasParked*

The following label has been added to the application:

<figure><img src="/files/68408ed18502eb3549d8dd364cfa64a19f6254a1" alt=""><figcaption><p><em><strong>Figure 2.</strong> Label with the wasParked variable in Eximee Designer</em></p></figcaption></figure>

Using it as an example, you can see how the variable value works *wasParked*.

On the first entry to the application, the variable *wasParked* is empty:

<figure><img src="/files/b5d0399f9b8174b0c2e6c29d77d5b60047dac605" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/82119b477ed4a10ecd40be86849cd0762301fbea" alt=""><figcaption><p><em><strong>Figures 3 and 4.</strong> Label with an empty wasParked variable on the application</em></p></figcaption></figure>

After saving the application and entering it again, you can see that the variable has been automatically filled in:

<figure><img src="/files/66924d9d85dc56cbc8d1ba5d5406a795596b0ae7" alt=""><figcaption><p><em><strong>Figure 5.</strong> Label with the wasParked variable on the application (after re-entering the application)</em></p></figcaption></figure>

## How to use the variable *wasParked*?

A label has been added to the application:

<figure><img src="/files/bfa0f0b63f61bcb1b2caaa8ae2a21f06fb0a924a" alt=""><figcaption><p><em><strong>Figure 6.</strong> Label with the wasParked variable in Eximee Designer</em></p></figcaption></figure>

Visibility condition set on this label:

```java
getValue("wasParked")=="true"
```

On the first entry to the application, it is not visible:

<figure><img src="/files/7543cd1143a029e52ef29b74745def93c50e51fd" alt=""><figcaption><p><em><strong>Figure 7.</strong> No visible label on the first entry to the application</em></p></figcaption></figure>

However, when the application is saved, the label appears upon re-entry:

<figure><img src="/files/8c6e3f048d8db15f722d54cfe8b0d6956c1d0d89" alt=""><figcaption><p><em><strong>Figure 8.</strong> Visible label upon re-entry to the application</em></p></figcaption></figure>

## Session change *wasParked*, and services

The operation of a service can also depend on the state of the variable *wasParked*. To make this happen, remember to add an invocation condition:

```java
getValue("wasParked")=="true"
```

<figure><img src="/files/c5d24f3e7c0088427bee46feae1e1bbffae8ff2c" alt=""><figcaption><p><em><strong>Illustration 9.</strong> Example service with an invocation condition</em></p></figcaption></figure>

After attaching the label and on the first entry to the application, the service is not called:

<figure><img src="/files/b5d0399f9b8174b0c2e6c29d77d5b60047dac605" alt=""><figcaption><p><em><strong>Figure 10.</strong> Unchanged label - the service was not called on the first entry to the application</em></p></figcaption></figure>

After saving the application and re-entering it:

<figure><img src="/files/372cf570d2c9e36540ee949cbd5505f6b76c0c37" alt=""><figcaption><p><em><strong>Figure 11.</strong> Changed label - the service was called on re-entry to the application</em></p></figcaption></figure>


---

# 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/interfejs-uzytkownika/formularze/tworzenie-formularza/zapis-tymczasowy/zmienna-sesyjna-wasparked.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.
