Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

You can This page is for application designers who want to create a table and add data components from an ERD. This feels ambiguous to me, what does this mean? We can create sceens? For how to create tables and relationships in an ERD, see Defining Data Structures using ERDsscreen directly from a table in an ERD.

In your application project's Home window, you can select to work on data or on designing a screen. However, at some point you will want to create a screen and connect it to your data. Within an ERD you can directly create a screen and display data on it.

  1. In an ERD, select a table to use as backing data for that contains data you want to show on a screen.
  2. To create a screen backed by this table, in In the toolbar, click Screen from the Create section. PhixFlow guides you through the process of creating a screen.
  3. Select a screen layout template.
  4. Enter the name for the new screen. PhixFlow creates the screen using the selected template.
  5. Select attributes as follows.
    Insert excerpt
    Showing Data on a Screen
    Showing Data on a Screen
    nopaneltrue
  6. Drag attributes onto the screen and drop them onto one of the areas highlighted in light blue.
  7. When you drop the attribute, PhixFlow asks how you want the data to be displayed. Click an option to add a component for a grid, graph, chart or card, which will fit the available space in the parent component.

    Select Form to set the parent as a form component, which is bound to the data view. PhixFlow adds a field to display the attribute being dropped.

    Tip

    Work on one component at a time. So if you start adding fields to one area, add all the fields you need to this area and complete. As you drag subsequent attributes, PhixFlow highlights the same area. There are some data binding logic rules that we may wish to discuss here, let's discuss.


  8. When you click Next, you can set sort and filter options for the data records in the view.

This process creates a data component that is bound to a data view and opens its properties - see View Concepts; see Compiling Views.