Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

This page is for data modellers and application designers who want to select specific attributes to appear in a screen, and to format how the data will be displayed.

Overview

The menu item properties panel is accessed from the view properties → Actions tab → Menu Item grid. Use the menu item properties to create menus and sub-menus that appear in the header of a view component. Associate the menu item with a table-action or actionflow that will run when the application user clicks on the menu item.

The view component on the screen is designed with a header bar. You can configure buttons, menus and sub-menus that are displayed in the view's header bar. Each button or menu item also has an associated table-action that runs when the application user clicks the item. You can only add table-actions from view's parent table.

There are three ways to add lists and buttons:

  1.  Click on the  Actionflow icon in the section's toolbar.
    • PhixFlow opens a list of the table-actions available on the parent table.
    • Drag a table-action from this popup form onto the grid.
    • If you drop onto an existing menu item, PhixFlow prompts you to:
      • either create a new button 
      • or add the action to the menu item.
    • If you drop onto an existing menu item, PhixFlow adds the dragged action to the list
  2. Open the Table properties. Drag actions into Properties tab→ Actions section list.
  3. Click the  Add New icon in the toolbar to create a button, menu or sub-menu.



Property Pane Toolbar

For information about the toolbar options, see the Common Properties page, Toolbars and Controls section.

 Properties Tab

Parent Details

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

Basic Settings

FieldDescription

Click Action

Select the type of action that PhixFlow will run when the user clicks on the menu or sub-menu item.

  • No Action
  • Stream Action (table-action)
  • Actionflow
Actionflow

Available when Click Action is Actionflow. Save a new menu item before setting this property.

To add an actionflow:

  1. Click  Actionflow to display a list of available actionflows in the repository.
  2. Drag the actionflow from the list into this field.

To create a new actionflow, click  Add New; see Creating Actionflows.

Action

Available when Click Action is Stream Action

To add a table-action:

  1. Find a table-action:
    • To reuse a table-action from a different table, click  List Tables to display a list of tables. Expand a table to see its associated table-actions.
    • To display a list of table-actions available to the parent table of this view, click Table-action.
  2. Drag the table-action from the list into this field.
Name

Available for sub-menus.

Enter a name of the action button. PhixFlow stores the menu item with this name. Use this name if you need to refer to this menu item elsewhere in PhixFlow. This is not the text that appears to the application user.

Display Name

Enter the menu text that an application user sees.


Order

Specify a number that is the order that the menu item appears:

  • either on the header bar, with 1 being the leftmost
  • or in a sub-menu, the order in the list, with 1 being the first.
Menu Items

Available for sub-menus.

The grid lists the menu items nested in this menu item. To add more menu items, click  Add New.


 Audit Tab

Audit Summary

See the Common Properties page, Audit Summary section.

Sections on this page

  Learn More

For links to all pages in this topic, see Designing Screens.



Terminology changes in progress

As part of the redesign of PhixFlow, we are changing the following terms:

dashboard → screen   
stream → table
stream attributes → attributes
stream item → record
stream set → recordset
stream view → view
stream item action → record-action 
stream action → table-action
driver class → database driver

  • No labels