Versions Compared

Old Version 1

changes.mady.by.user Fiona Sargeant

Saved on

compared with

New Version Current

changes.mady.by.user Zoe Baldwin

Saved on

Key

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



Action Concepts

A stream has a set of  Stream Item Actions (SIA). These represent the smallest, specific operation that can happen to the data in the stream.

You can configure one action to run on the data in different streams. This is because the action contains:

  • a list of stream item actions (SIA) from different streams. The action can potentially run any of these SIA.
  • with each SIA, is the rule that specifies the conditions for that SIA to be run.

To use a SIA in an action:

  • Open the Action properties.
    • In the toolbar of the Stream Item Action Rules section:either click   to create a new SIA rule. or click  to open a repository list of streams.
    Expand the branch for the stream, then drag its SIA into the action properties → Stream Item Action Rules grid.
    Double-click on a SIA rule in the grid to open its properties. 
    Excerpt
    Insert excerpt
    _add_add
    nopaneltrue
    Insert excerpt
    _action_SIA_action_SIA
    nopaneltrue
    Excerpt

    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.