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
This action can only be used for the On button clicked event procedure.
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
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
This action can only be used for the On button clicked event procedure.
Main menu (DAWActionRunMainMenu) - Opens the main menu for the application.
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
Click Mobility design.
Click the Libraries tab.
In the list, find and select the desired record.
Click View.
Click the Actions tab.
Click Refresh.
Close the page.
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.