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 Version History

« Previous Version 22 Next »

This page is for application designers who want to configure actions.

Overview

Record-Action Concepts

To make changes to the data in a table use a record-action. Each record-action is a single operation that can happen to a record in the table. Record-actions can create, read, update or delete a record, so are sometimes called CRUD actions. To configure PhixFlow to perform several operations to the data  record-actions directly to a table. Alternatively, to configure PhixFlow to perform several operations

  • in one table, add a list of record-actions to a table or to a table-action associated with the table.
  • in different tables, add a list of record-actions to an action that is not associated with a specific table. The record-actions affect the different tables.

An action/table-action can potentially run any of the record-actions in its list. To decide which record-action to run, create a rule associated with each record-action. When the rule evaluates to true, the record-action runs, making a change to the data in the table. See Record-Action and Record-Action Rule properties.

When you are creating a stream-item-action for a table, use this property tab to add an expression that evaluates to the new value for that table attribute.

  1. Create a Stream Item Action. 
  2. In the Basic Settings →  Attributes to Update section there is a grid of attributes.
  3. In the grid, double-click on a attribute.
  4. PhixFlow opens the stream-item-action attribute property tab. 

Properties

This property tab is not available from the repository. It only opens from the Record-actions properties.

For information about the properties toolbar, and about the sections Parent Details, Analysis Models, Description and Audit Summary, see Common Properties.  We recommend you always add a Description that explains the purpose of the item you are creating. 

For a full list of all the PhixFlow property tabs and windows, see Properties, Windows, Menus and Toolbars.

Basic Settings

FieldDescription
OrderEnter the order in which the attribute expression will be evaluated. 
AttributeSelect the name of the table attribute that will be populated.
Expression

Enter an Expression to generate a new attribute value. 

To refer to table attributes, pipes and screen zones in the expression, use:

  • <attribute-name> to refer to the current value of the stream-item you are about to update.
  • <pipe-name> to refer to lookup pipes on the same table as the action. The pipe cannot reference _out variables directly.
  • <screen-zone-name> refers to selected stream-items from other views using their screen zone names.
Example

For example:

  • A screen zone name is ACCTS.
  • In the screen, the user will select stream-items in a grid view.
  • For the selected stream-items, you want the action to sum the values in the amount attribute.

Enter an expression:

sum(ACCTS.amount)

You can also use the following prefixes:

  •  _prompt.<form-field-name> to refer to fields from any user input form associated with this action.

  • _form.<form-field-name> to refer to the current value displayed in a field on the form.

    Example

    In the screenshot below, the expressions use _form to refer to fields Unit Price, Quantity and VAT Percentage. The user sees these fields on a form.


  • _out.<attribute-name> to refer to the current value of an attribute in the action.
    For example, in the screenshot above, you could refer to the value for the attribute ChargeAmount in VATAmount with the expression _out.ChargeAmount.

  • _context.<context-variable-name> refer to any context variable defined for this action.

  • _gridRow.<table-view-attribute-name> to refer to the edited value of an attribute when the Filter Type is Edited Items.
     _gridRow contains a streamset pointing to an individual row that has been modified.

Messages

You can use the following message functions in the expression. When the action runs, any messages are written to the system console and logs.

If PhixFlow reports an error, it stops the action from being completed for the current stream-item in the table.  However, the error does not stop the action from updating or inserting other stream-items.


  • No labels