Parameter Types 

When writing expressions, it is important to consider the type of the result. For example, you can write an expression to return the integer 3 but have defined the type of the stream attribute to be a string. If there is a mis-match between data types, when the expression is evaluated, PhixFlow stops evaluating the expression and reports an error.

The full list of types handled by PhixFlow is shown in the following table. 

Assigning Values to Variables

In PhixFlow, you can create your own variables using a $ symbol, for example $variableName; see Using Variables.

In expressions that have complex calculations, you may need a variable to hold the result of a calculation. You can then reference the variable later in the expression, or in other attribute expressions for the same table.

The following expression uses do() function and $-variables for a simple calculation.

When to Use $-variables

$-variables are not really needed in simple calculations. They are useful:

• in forEach loops
• calculating attibute names from pipes; see Assigning Values From a Pipe.
• to store a value from a look-up pipe, when you need the value in multiple attributes
  1. In the first attribute, look-up the value.
  2. Use a $-variable to store the value that is returned by the look-up.
  3. When you need the value in another attribute, reference the $-variable instead of repeating the look-up.
• in complex expressions, to break up multiple consecutive functions into separate lines. In this case, use a $-variable to store the intermediate values; see Multiline Statements and $-variables.

Assigning Values From a Pipe 

Stream attribute expressions are commonly used to fetch the value returned by a Pipe. This is simply done by suffixing the pipe name with the name of the attribute to be returned. For example: 

  in.accountRef

This expression causes PhixFlow to look at the pipe named "in" and return the value in the field called "accountRef".

Calculating an Attribute Name

If the name of the attribute whose value you want has to be calculated based on other factors, you can assign the attribute name to a $-variable. You then use the variable instead of the attribute name itself. For example:

  in.$attrName

Handling Invalid Characters

There are two options for handling an attribute name that contains invalid characters.

• Either assign that name to a variable and use the variable instead of the actual attribute.
• Or enclose the name in quotes, for example:  in.'account-ref'.

Mathematical Operators (+, -, *, /)

Several values can be combined using the usual basic mathematical operators. For example when in.numProducts has the value 9:

The usual calculation precedences apply, so * and / operations are carried out before + and -. When the mathematical statements involve multiple calculations, use brackets ( ) to force the correct processing order.

String Concatenation (+)

The + operator also serves as the string concatenation operator. This means you can use + to  join strings together. For example if in.customerName returns "Smith" and in.title returns "Mr":

Internal Variables

Sometimes when youWhen you pass a a value that is passed between programs, subroutines or functions. Arguments are independent items, or variables, that contain data or codes.

PhixFlow has a list of functions you can use in an expression.

 expression within an expression

internal variable

_out. tells PhixFlow that it has already "seen" the attribute AppleHarvestDate in this stream.

You can refer to

<pipe_name>.<attribute_name> and pipe names default to "in", so  in.AppleHarvestDate which signals that AppleHarvestDate is being sourced down a pipe going into the stream called 'in'. The internal variable preceding an attribute name should reflect where the attribute is being source from.

There are many other internal variables, see /wiki/spaces/HELP80/pages/1456964453.

Regular Expressions - Regular expressions can be used to match patterns within strings or arrays as arguments within jep expressions, for example replaceAll, replaceFirst and matches. See Regexp ToDelete.

Simple integers or strings. In the above case 1 and 0 are simple integers. They tell PhixFlow to return the number 1 if NumberOfApples > 1 and 0 if it is not. A string could be returned instead eg. if(_out.NumberOfApples > 1, 'True', 'False') would return the string True if NumberOfApples >1 and False if it is not. Note strings need to be wrapped in ' marks. 

(To find the correct syntax for an expression - find it in the list below or search in confluence)

If() Statements

It is common to want to evaluate whether or not data meets a condition. To do this use an if() statement; see the if page.

Multiline Statements and $-variables

When you are working with more complex expression, you may have several different statements to evaluate first. To group statements together, use the do() function.

In multi-line statements, you usually need to assign the value of an expression to a $-variable, to use later in the expression. For example:

The value of an expression that is used, is the value of the last statement to be evaluated. In simple expressions, such as the example above, the last statement to be evaluated is the last line. However, in Conditional Statements, the last statement evaluated is not always the last statement in the expression. For example:

Adding Comments

It is always a good idea to add comments to your scripts to explain its steps. Comments help anyone who needs to modify the script in future.

There are two ways to tell PhixFlow that a line is a comment, and can be ignored.

For some examples using comments, plus other style tips for expressions, see Expression Style.

See Also

• Expressions and Scripts topic page for links to more information.