Versions Compared

Key

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

Insert excerpt
HELP100:_BannersHELP100:
_Banners
nameactionflow
nopaneltrue

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 

Insert excerpt
HELP100:_action_viewHELP100:
_action_view
nopaneltrue
node to select and filter additional data to use in the actionflow.

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..

Insert excerpt

HELP100:

_property_tabs

HELP100:

_property_tabs
namebasic-h
nopaneltrue

Insert excerpt
HELP100:_property_toolbarHELP100:
_property_toolbar
nopaneltrue

Insert excerpt
HELP100:_parentHELP100:
_parent
nopaneltrue

Basic Settings

FieldDescription
NameEnter the name of the action node.
Primary Table

Read-only. PhixFlow displays the table where the view attribute originates.

Data Retrieval Options

FieldDescription
Data Range

Select the data range that the view node will use:

  • All: use all the data 
  • Latest: use only the latest data.
Include History Records
Insert excerpt
HELP100:
_check_box_tick
HELP100:
_check_box_tick
nopaneltrue
 to include superseded records in the view data. 
Default Sort Order

The sort order determines the order the data is displayed.

Select a sort order, or click

Insert excerpt
HELP100:_addHELP100:
_add
nopaneltrue
  to create a new one; see Sort Order

Default Filter

A filter determines what data is retrieved.

Select a filter, or click

Insert excerpt
HELP100:_addHELP100:
_add
nopaneltrue
 to create a new one; see Filter.

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
    Insert excerpt
    HELP100:_deleteHELP100:
    _delete
    nopaneltrue
     in the Output Attributes section header.
FieldDescription
NameEnter the name of the action node.
Type

Select the type of data this attribute contains; see Understanding Data Types.

  • String
  • Bigstring
  • Integer
  • Float
  • Decimal
  • Date
  • Datetime
  • Graphic
  • TrueFalse
Aggregate Function

Parameters

Parameters are the attributes used to perform the lookup on a view. They are assigned a value by the mapping screen in the Incoming Mappings tab.

Create a new attribute

  1. Click 
    Insert excerpt
    HELP100:_addHELP100:
    _add
    nopaneltrue
     
  2. Set the Name and Type; see Attribute.

Change the properties of an attribute

  1. double-click an attribute in the list; see View Attribute

Delete an attribute

  1. Right-click and select 
    Insert excerpt
    HELP100:_deleteHELP100:
    _delete
    nopaneltrue
    .

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.

  1. Click on the connector coming into the Lookup node.
  2. Incoming Mappings 
    1. Map attributes from the calling action node e.g. a calculate, to the View.
    2. 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.
  3. Click Next
  4. Outgoing Mappings 
    1. Map attributes returned by the view (defined in the output mappings above) to the calling action node.
    2. 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 buttonsThe grid contains a list of all output connection points.

  • To add a new output path, in the section toolbar click 
    Insert excerpt
    HELP100:_addHELP100:
    _add
    nopaneltrue
     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 
    Insert excerpt
    HELP100:_deleteHELP100:
    _delete
    nopaneltrue
    .

Insert excerpt
HELP100:_descriptionHELP100:
_description
nopaneltrue

Insert excerpt

HELP100:

_property_tabs

HELP100:

_property_tabs
nameaccess-h
nopaneltrue

Insert excerpt
HELP100:_accessHELP100:
_access
nopaneltrue

Insert excerpt
HELP100:_auditHELP100:
_audit
nopaneltrue


Live Search
spaceKey@self
additionalnone
placeholderSearch all help pages
typepage

Panel
borderColor#00374F
titleColorwhite
titleBGColor#00374F
borderStylesolid
titleSections on this page

Table of Contents
maxLevel3
indent12px
stylenone


Learn More

For links to all pages in this topic, see Understanding Actionflows

Insert excerpt
HELP100:_terms_changingHELP100:
_terms_changing
nopaneltrue