This page provides details of the properties for the calculate action node and associated expressions. These are part of actionflows.
Overview
A calculate action is used to manipulate data that is passed to it. Calculate actions have their own attributes which can reference incoming data via expressions using one or more of the 115+ functions available in PhixFlow.
Example
Properties Tab
Parent Details
If this item is within or belongs to another, its parent name is shown here. See the Parent Details section on the Common Properties page for more details.
Basic Settings
| Field | Description |
|---|---|
| Name | Enter the name for the action node. |
| Show in the Repository | An application can have many actionflows, and an individual actionflow can have many nodes. This can lead to many items being listed under Actionflow in the repository. Use this option to omit the node from the repository.
|
| Pass Through | Specify whether or not to allow data that has not been processed to pass through to the next action node.
|
Calculate Attributes
Calculate actions process data using expressions; see pages in the topic Expressions and PhixScripts.
This section has a toolbar with standard buttons. The grid contains a list of the expressions that the calculate action will perform.
- To add a new expression, in the section toolbar click
Add New to open a new expression and set the properties. - To edit an existing expression, double-click it in the list to open its properties.
- To remove an expression, select one and in the section toolbar click
Delete.
Calculate Attributes Properties
Basic Settings
Field | Description |
|---|---|
| Name | Enter the name of the calculate attribute. |
| Type | Select one of the data types:
Make sure you select the same data type as that of the attribute to which you are mapping; see Understanding Data Types. |
| Attribute Name |
|
| Expression | Enter an expression. To work in a larger pop-up window, click See also: |
| Order | Where the calculate action runs multiple expressions, enter a number to indicate the order in which this expression will be run. Remember that an expression that generates a value should run before an expression that uses the value. |
Description
We recommend that you always enter a description to explain the purpose of this item.
Access and Audit Tab
Security Tab
Access Permissions
See the Common Properties page, Access Permissions section.
Audit Tab
Audit Summary
See the Common Properties page, Audit Summary section.