Overview

 Startup Actions run when an application is first opened. It can be used for:

1. Opening a landing screen.
2. Opening a custom navigation menu bar.
3. Opening a static menu. 

If you do not want to create your own navigation menu, the startup actions provide the ability to create a static menu bar for your application, on which you can add menu options. These contain top-level menu items, which is the container for menu options. The menu options can be:

• either options that trigger an action
• or sub-menus that list other menu options. 

For applications that are designed for use on both PCs and mobile devices, it is possible to set startup actions independently for either or both. 

Startup Landing Screen (Automated Creation)

Adding a Screen

1. Open an application.
2. On the Screens home page, right-click on a screen.
3. Select Open Screen on Startup
   1. If a Startup Action exists this screen will be added to it.
   2. If no startup action exists, one will be created.
4. More than one screen can be added to the startup Action.

Removing a Screen from the Startup Action

1. Open an application.
2. On the Screens home page, right-click on a screen
3. Select Remove from the Application Startup Action.

Start Landing Screen and/or Navigation

1. In the repository, open  Startup Actions.
2. Click  Add New
3. Enter a Display Name.
4. Toggle on one or both of the following, as appropriate. Typically both are .
   1. Default Desktop Startup Action
   2. Default Mobile Startup Action
5. Click  Apply, this creates the Startup Action.
6. For Action Method select Actionflow.
   1.  List Actionflows: If you have an actionflow which opens the desired screen or screens click the actionflow button to navigate to it and drag it into the place holder.
   2.  Add New: If you need to create an actionflow click add new:
      1. Enter a Name and click Confirm.
      2. The Actionflow opens.
      3. Click on Connect.
      4. Select on Click.
      5. Click  Open Screen on the toolbar.
      6. Drag the desired screens and or navigation menus you want to be present when your application opens for a user.
      7. Now drag the connection point to each of your screens as illustrated below:
      8. 
      9. Changes are automatically saved, so close your actionflow.
7. Click  Apply and Close to save your startup action and close it.
8. Now when you next open the application it will open the selected screens.

To learn more about navigation menus see Adding a Navigation Menu Bar.

 Properties Tab

Parent Details

If this item is within or belongs to another, its parent name is shown here. See the Parent Details section on the Common Properties page for more details.

Basic Settings

Description

We recommend that you always enter a description to explain the purpose of this item.

 Audit Tab

Audit Summary

See the Common Properties page, Audit Summary section.

Learn More

• Understanding Actionflows
• Using Table-Actions

For links to all pages in this topic, see Connecting Events to Actions