---
title: "Set up application event procedure"
slug: "set-up-application-event-procedure"
description: "Set up application event procedures for actions like On load and On logoff, defining sequences and conditions for mobile device interactions."
tags: ["Flow", "Anywhere Mobility Studio"]
updated: 2026-03-20T12:44:25Z
published: 2026-03-20T17:46:51Z
canonical: "docs.staedean.com/set-up-application-event-procedure"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.staedean.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up application event procedure

You can set up an application event procedure with actions that are done in a specific sequence. An application event procedure has one action or a series of actions that are done on one of these application events:

- **On load** - An application is loaded to a mobile device.
- **On logoff** - A user logs off from the application. The user session is stopped and removed from the active sessions list. **Note**: On logoff does not take place if a user session expires.
- **On menu select** - A menu is opened on the mobile device.

Use the **Up** and **Down** buttons to define the action sequence.

Optionally, you can run an action under specific conditions. For conditions, you can use functions that are available for the application.

### Steps

1. Click **Mobility design**.
2. On the **Applications** tab, click **Edit**.
3. Click the **Events** tab.
4. You can set up an event procedure for several application events. As an example, in these steps, you set up an event procedure for the On load application event.

Next to the **On load** field, click the **Edit OnLoad (+)** button.
5. Sub-task: Add actions.
  1. On the **Event procedure** dialog, on the **Actions pane**, click **Add** to open the drop dialog.
  2. In the list, find and select the desired actions.
  3. Click **OK**.
6. Sub-task: Fill in parameters.
  1. On the **Actions pane**, in the list, select an action.
  2. For each action, the relevant parameters are defined in the action class. Each action can have a different set of parameters.

Usually, these are input or output parameters. For these parameters, you can define the value. Only define a value for the parameters that are applicable to the event procedure.

Sometimes, an action has a different type of parameters or no parameters.

In the **Value** field, you can use a variable, a function, or a fixed value. In this step, as an example, you enter a variable.

On the **Parameters** tab, in the **Value** field, enter or select a value.

> [!NOTE]
> **Note**
> 
> If the parameter is of type enum, and you define a fixed value, you can only select an enum as defined for the parameter.
7. Sub-task: Define conditions.
  1. Optionally, you can run an action under specific conditions.

Click the **Conditions** tab.
  2. Click **Add** and fill in the fields.

> [!NOTE]
> **Note**
> 
> In the first **Value** field, you can use a variable or a function.
> 
> In the second **Value** field, you can use a variable, a function, or a fixed value.
8. Click **Close**.

## Related

- [Design application event procedure](/design-application-event-procedure.md)