...
| Field | Description |
|---|---|
| Stream Item Action | Select from a drop down of all of them, or drag one in from the repository - easier to find SIAs for a specific stream |
| Filter Type | Select an option from the drop-down list:
|
| Target View | If specified, changes the view the action applies to (gets records from if selected Filter Type = Selected Items, Edited Items or View Filter). |
| Condition | This is only available if you have selected Filter Type = Action Filter. Create a filter to specify the records that an Update or Delete will apply to. Any expressions on this filter can reference the Form View fields, Context Parameters and any attributes from any record selected on the view or dashboard from which this action was initiated. Configure this filter in the same way that you would a pipe filter. |
Action Attributes
The list of attributes that will be populated by the action - whether an update or insert.
This section includes the button 
- this brings up the list of attributes for the stream that you are building the action on. Drag any attributes you want from this list into the action, or add them by pressing 
.
For each attribute, configure the following fields:
...
The expression used to generate the new attribute value. This is written as a PhixFlow Expression.
- Dashboard Element Name You can reference selected records from other dashboard views by using their dashboard element names within the expression. E.g.
| Code Block |
|---|
sum(ACCTS.amount) |
will sum up all values in amount from the records select in the view with dashboard element name ACCTS.
- No Prefix If you want to refer to the current values of the record you are about to update, then simply refer to the attribute name with no prefix.
- _prompt You can reference fields from any user input form associated with this action by referencing the form field name prefixed by _prompt.
- _form You can reference the current value displayed in a field on the form by using _form as a prefix.
For example: In the screenshot below, the expressions use _form to reference fields that are displayed on the form (Unit Price, Quantity and VAT Percentage).
The usual message functions debug(message), info(message), warning(message), and error(message) are all available to be used in these expressions and will result in messages being written to the system console logs.
Be careful when using the error(message) function - this will stop the action from being completed for the current stream item. However, it will not stop the action from updating/ inserting other stream items.
- _out You can also use the prefix _out to reference the current value of an attribute in the action. Note that in the above example, to use the value for the attribute ChargeAmount in VATAmount the expression uses _out.ChargeAmount.
- _context Reference any context variable defined on this Action or passed through to this Action.
- _gridRow When the Filter Type is Edited Items this object contains a recordset pointing to an individual row that had been modified.
- "pipe" Expressions can refer to lookup pipes on the same stream as the action. Note that at version 7.6.0, lookup pipes used in this way can only be driven by $ variables i.e. if the lookup filter or cache lookup needs to be driven by values from the action, then those values nust be passed in by $ variables. The pipe cannot reference _out variables directly.