wasParked session variable

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 1. The wasParked variable in Eximee Designer

How it works wasParked

The following label has been added to the application:

Figure 2. Label with the wasParked variable in Eximee Designer

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:

Figures 3 and 4. Label with an empty wasParked variable on the application

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

Figure 5. Label with the wasParked variable on the application (after re-entering the application)

How to use the variable wasParked?

A label has been added to the application:

Figure 6. Label with the wasParked variable in Eximee Designer

Visibility condition set on this label:

getValue("wasParked")=="true"

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

Figure 7. No visible label on the first entry to the application

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

Figure 8. Visible label upon re-entry to the application

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:

getValue("wasParked")=="true"

Illustration 9. Example service with an invocation condition

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

Figure 10. Unchanged label - the service was not called on the first entry to the application

After saving the application and re-entering it:

Figure 11. Changed label - the service was called on re-entry to the application