Overview

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

Opening a landing screen.
Opening a custom navigation menu bar.
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

Open an application.
On the Screens home page, right-click on a screen.
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.
More than one screen can be added to the startup Action.

Removing a Screen from the Startup Action

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

Start Landing Screen and/or Navigation

In the repository, open
.
Click
Enter a Display Name.
Toggle on one or both of the following, as appropriate. Typically both are
.
1. Default Desktop Startup Action
2. Default Mobile Startup Action
Click
, this creates the Startup Action.
For Action Method select Actionflow.
1. : 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. : 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
    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:
  9. Changes are automatically saved, so close your actionflow.
Click
to save your startup action and close it.
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.

Basic Settings

Field	Description

Field	Description
Name	Only available for the top-level menu item and sub-menu items. Enter the repository name for the menu item.
Display Name	You can only enter a display name for sub-menus. Enter the sub-menu name for PhixFlow to display either on the menu bar or in another menu. For menu options, PhixFlow shows the display name inherited from the action. To change the action's display name, Find the action in the repository. Change the action properties Basic Settings → Display Name.
Order	Enter the order in which the menu will appear, either on the menu bar or in the sub-menu list. PhixFlow reorganises existing entries if you add an order that is already in use. The order for menu items is: On the menu bar, left to right, with the last option aligned to the right of the screen. In a sub-menu, top to bottom in the list.
Default Action	Only available for the top-level menu item. Optionally, select an action that will run when the menu is opened.
Action	Only available for menu options. Select an action that will run when the user clicks the option in the menu.
Hide the Menu Bar	Only available for the top-level menus. to display the menu bar at the top of your application; see Design and Application Mode for screenshots showing the default menu bar. to hide the menu bar. Use this option for a cleaner look to your application if it does not require menu options for the user. You can have a different setting for default desktop and default mobile menus.

Learn More

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