---
title: "Develop action class"
slug: "develop-action-class"
description: "Learn how to implement actions in event procedures using the DAWActionRun class in Mobility studio for seamless user session management."
tags: ["Task", "Anywhere Mobility Studio"]
updated: 2026-03-20T12:50:29Z
published: 2026-03-20T17:46:51Z
canonical: "docs.staedean.com/develop-action-class"
---

> ## 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.

# Develop action class

You can use an action on an event procedure. If the event occurs, the action is done.

For an action, a class is required. To develop this class, extend the DAWActionRun class.

A set of predefined action classes is available:

- Back (DAWActionRunReturnFrom) - Goes back to the previous form in the form stack of the user session.

> [!NOTE]
> **Note**
> 
> This action can only be used for the On button clicked event procedure.

> [!NOTE]
> **Note**
> 
> This action starts the On reactivate event procedure of the previous form, if defined.
- Form (DAWActionRunPage) - Opens a form as defined for the application in Mobility studio.

> [!NOTE]
> **Note**
> 
> This action starts the On deactivate event procedure of the form that was open, if defined.
- Logout (DAWActionRunLogout) - Logs the user out of the current user session. This session is removed from the active sessions list.

> [!NOTE]
> **Note**
> 
> This action can only be used for the On button clicked event procedure.
- Main menu (DAWActionRunMainMenu) - Opens the main menu for the application.

> [!NOTE]
> **Note**
> 
> This action can only be used for the On button clicked event procedure.

**Prerequisite**: Develop the extension of the DAWActionRun class in the AOT before you start the steps. **Note**: The steps are to have the developed action class uploaded as action to the related library.

### Steps

1. Click **Mobility design**.
2. Click the **Libraries** tab.
3. In the list, find and select the desired record.
4. Click **View**.
5. Click the **Actions** tab.
6. Click **Refresh**.
7. Close the page.

> [!NOTE]
> **Notes**
> 
> If you deploy (export/import) an application as built in Mobility studio, make sure the related custom action classes are deployed as well. You can do so with a Microsoft Dynamics Lifecycle Services project.

## Related

- [Design application event procedure](/design-application-event-procedure.md)
- [Design control event procedure - Check box](/design-control-event-procedure-check-box.md)