For Each Node

Overview

Use a  For Each when it is necessary to iterate over a set of records, or a list of values, and generate an output record for each one.  

 Properties Tab

FieldDescriptionExample Value
NameThe name given to the node and displayed on the canvas.MyForEach
Input Expression

The Input Expression iterates over the data provided in the Input Parameters and the records are passed to the Output Attributes in the form _result.value.

Input Parameters are referenced using their name, prefixed with the name of the connector. For example, in.MyAttribute . If an empty record set or empty list is provided then no output will be generated.

This field is mandatory (PhixFlow version 11.1 +).

// Receives a list of Invoice IDs, these are iterated over using

in.InvoiceID    

Inputs Parameters

Can accept a single  Driving input connection point.

The grid contains a list of all input connection points and their type.

  • To add an Input Parameter, in the section toolbar click  Add New and set its properties.
  • To edit an existing Input Parameter, double-click it in the list to open its properties.
  • To remove an Input Parameter, select one (or more) from the list and in the section toolbar click  Delete.

Input Parameters can be mapped to by clocking on the incoming connector.

Output Attributes

The grid contains a list of all Output Attributes.

  • To add an Output Attribute, in the section toolbar click  Add New and set its properties.
  • To edit an existing Output Attribute, double-click it in the list to open its properties.
  • To remove an Output Attribute, select one (or more) from the list and in the section toolbar click  Delete.

New Output Attribute

FieldDescriptionExample Value
NameThe name given to the attribute.Invoices
Type

Defines the type of data to be returned.

See Understanding Data Types

String   

Expression

This is a PhixScript expression. Values returned by the Input Expression are available in this expression as:

_result.value

To work in a larger popup window, click  Show field in a large editor.

See also:

_result.value

Advanced

FieldDescription

Prioritise Throughput Over Ordering

When enabled, records are processed in parallel to optimise performance. This means the order records are processed is nondeterministic.

When disabled (default), records are processed in the order they are provided.

 Audit Tab

Audit Summary

See the Common Properties page, Audit Summary section.