--- title: "Set up form event procedure" slug: "set-up-form-event-procedure" description: "Set up form event procedures for actions like On init, On load, and On submit, defining sequences and conditions for mobile forms effectively." tags: ["Task", "Anywhere Mobility Studio"] updated: 2026-03-20T12:45:41Z published: 2026-03-20T17:46:51Z canonical: "docs.staedean.com/set-up-form-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 form event procedure You can set up a form event procedure with actions that are done in a specific sequence. A form event procedure has one action or a series of actions that are done on one of these form events: - **On init** - A form is created in the form stack of the user session. Usually, this is done once for a user session. - **On load** - A form is opened on the mobile device. - **On submit** - The user submits data on the mobile device. For example, scans a barcode or enters a number. - **On deactivate** - Another form is opened with an event action of type **Form**. - **On reactivate** - The previous form is opened with an event action of type **Return from**. 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 variables or functions that are available for the application or form. ### Steps 1. Click **Mobility design**. 2. Click the **Forms** tab. 3. In the list, find and select the desired record. 4. Click **Edit**. 5. Click the **Events** tab. 6. You can set up an event procedure for several form events. As an example, in these steps, you set up an event procedure for the **On init** form event. Next to the **On init** field, click the **EditOnInit (+)** button. 7. Sub-task: Add activities. 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**. 8. 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. 9. Sub-task: Define conditions. In the second **Value** field, you can use a variable, a function, or a fixed value. 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. 10. Click Close. ## Related - [Design form event procedure](/design-form-event-procedure.md)