View Node
Overview
When you are designing screens, you use a view to select and filter data for display. In an actionflow, the originating screen or component may not include all of the data that the actionflow requires. In this case, use a
How the actionflow processes the view data depends on whether the view is wired via a driving or lookup connection.
For a driving connection, records are returned individually to the view node and flow one by one through the remainder of the actionflow.
For a lookup connection, the records are returned as an array within one recordset. Lookup views require both:
Data Attributes: the attributes being passed into the view node.
Request Attributes: the attributes from which you need to lookup data.
When you create a view node, PhixFlow prompts you to select the table on which this view is based. PhixFlow opens the Attributes window and the view node properties.
Drag attributes from the Attributes window and onto the Data Attributes or Request Attributes sections. You can add attributes from the base table and from related tables..
Basic Settings
Field | Description |
|---|---|
Name | Enter the name of the action node. |
Primary Table | Read-only. PhixFlow displays the table where the view attribute originates. |
Data Retrieval Options
Field | Description |
|---|---|
Data Range | Select the data range that the view node will use:
|
Include History Records |
|
Default Sort Order | The sort order determines the order the data is displayed. Select a sort order, or click |
Default Filter | A filter determines what data is retrieved. Select a filter, or click |
Output Attributes
Output attributes are the attributes provided by the view or returned by a lookup on the view.
The grid contains a list of the attributes in the view. Click to show the list of available attributes from the primary table. Drag the attributes you want to add to the view into this list.
In the list:
To edit an attribute's properties, double-click the attribute. See View Attribute.
To delete an attribute, select it and click
in the Output Attributes section header.
Field | Description |
|---|---|
Name | Enter the name of the action node. |
Type | Select the type of data this attribute contains; see Understanding Data Types.
|
Aggregate Function | See Aggregating Data |
Filter Parameters
These are used to perform the lookup on a view. They are assigned a value by the mapping screen in the Incoming Mappings tab and are referenced by name no pipe prefix is required.
Create a new attribute
Click
Set the Name and Type; see Attribute.
Change the properties of an attribute
Double-click an attribute in the list; see View Attribute
Delete an attribute
Right-click and select
.
Map a Value to the Parameter
Parameters are used in the request to perform a lookup, obtaining their value from an attribute in the actionflow via the mapping screen.
Click on the connector coming into the Lookup node.
Incoming Mappings
Map attributes from the calling action node e.g. a calculate, to the View.
Parameters can be dynamically created and mapped by dragging attributes from the calling action node into the drag-and-drop area on the parameters side.
Click Next
Outgoing Mappings
Map attributes returned by the view (defined in the output mappings above) to the calling action node.
Attributes can be dynamically created on the calling action node and mapped by dragging attributes from the view attributes into the drag-and-drop area of the calling action node.
Output Connection Points
This section has a toolbar with standard buttons. The grid contains a list of all output connection points.
To add a new output path, in the section toolbar click
to open a new output path and set the expression; see Output Connection Points.To edit an existing output path, double-click it in the list to open its properties.
To remove an output path, select one and in the section toolbar click
.
Learn More
For links to all pages in this topic, see Understanding Actionflows.