Page Comparison

An application user triggers an action by clicking on a button. When you design a screen, you This page is for application designers who want to add a button that opens a different screen.

When using your application, the application user needs to be able to navigate to different screens. You can provide navigation to different screens using:

• menus; see Adding a Navigation Menu Bar.
• buttons that open a different screen. In this case you must configure an actionflow for the button.

PhixFlow provides an easy way to wire a button to configure an "open screen" actionflows on a buttonan actionflow that opens a screen.

1. Open the screen on which you want to add a the button to open another screen.Unlock .
2. Right-click and 

   Insert excerpt
   _unlock _unlock nopanel true

   the screen.
3. In the repository, find the screen that you want the button will open and drag it to open. Drag the screen onto the screen canvas. Drop and drop it where you want the button to be.
4. PhixFlow adds a button to the screen canvas.
   The button design is from the default component, which is set in the application properties →  → Styles tab → Default Components section→ Table Action Component.
5. PhixFlow also creates an actionflow to open the second screen and wires it to the button.
6. To test the button, either

   Insert excerpt
   _lock _lock nopanel true

   the screen or switch to

   Insert excerpt
   _app_mode _app_mode nopanel true

   . Click the button to check that it opens the required screen.

Learn More

• If PhixFlow puts the button in the wrong place, you can move it; see Moving Items Components on a Screen.
• You can check the actionflow configuration or add additional functionality to the button; see Wiring Actionflows.
• You can also add actions user interaction to charts and grids; see Actions on Grids and Charts.
• To add navigation menus, see Adding a Navigation Menu Bar.
• For applications made in version 8.3 or earlier, PhixFlow provided table-actions or record-actions instead of actionflows; see Using Table-Actions.