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

« Previous Version 24 Next »


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.

Sections on this page

Example

Initially there is an actionflow which opens a new screen containing a dynamic text field. The aim of this example is to populate this dynamic text field with a message set by an attribute in a calculate node. The steps for this are:

  1. Create a  Calculate node by dragging and dropping a node from the create section in the toolbar
  2. Name the calculate something meaningful, e.g. Set Message
  3. Disconnect the  Open Screen node from the  Driving interface connection point
  4. Connect the  Driving interface connection point to the  Calculate node
  5. Connect the  Calculate to the  Open Screen node, using the component input connection point - 'ScreenToOpen'. This is the name of the outermost area/form on the screen, enabling data to be passed to it.
  6. Create a calculate attribute
    1. Name this Message
    2. Add the following expression

      "You have successfully set up a calculate node" 
  7. Map the calculate attribute to the dynamic text field on the screen 
    1. Right click on the connection and click Configure Mappings

    2. Drag the Message attribute from the calculate (LHS) to the Message attribute on the open screen (RHS)
    3. Close the mapping screen
  8. The actionflow configuration is complete.
  9. Always remember to test the actionflow to make sure it works.

 Properties Tab

Parent Details

If this item is within or belongs to another, it's parent name is shown here. See the Common Properties page, Parent Details section for more details.

Basic Settings

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

 Tick to display this node in the repository.

 Untick to omit this 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. 

 Untick to prevent data that is not processed by this node from passing to the next action node. 

 Tick to allow data that is not 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 buttonsThe 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

Parent Details

Basic Settings

Field

Description
NameEnter the name of the calculate attribute.
Type

Select one of the data types:

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

Make sure you select the same data type as that of the attribute to which you are mapping; see Understanding Data Types.

Attribute Name

 Tick to indicate the calculate attribute matches the name of an attribute in the data.

Expression

Enter an expression. To work in a larger pop-up window, click .

See also:

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

  • No labels