Loop End

Node at the end of a loop. It is used to mark the end of a workflow loop and collects the intermediate results by row-wise concatenation of the incoming tables. The start of the loop is defined by the loop start node, in which you can define how often the loop should be executed (either fixed or derived from data, e.g. the "group loop start"). All nodes in between are executed that many times.

You can add more input and ouput tables using the “…” menu.

Options

Row ID policy
Specifies how to deal with the row IDs for each table.
  • Generate new row IDs - row IDs are newly generated (Row0, Row1, ...)
  • Unique row IDs by appending a suffix - the iteration number is added to each row ID from the incoming table, thus making the row IDs unique over all iterations
  • Leave row IDs unmodified - the incoming row IDs are not altered. In this case you have to make sure that there are not duplicate row IDs in different iterations. Otherwise an error occurs.
Add iteration column
Allows you to add a column containing the iteration number to the output tables.
Propagate modified loop variables
If checked, variables whose values are modified within the loop are exported by this node. These variables must be declared outside the loop, i.e. injected into the loop from a side-branch or be available upstream of the corresponding loop start node. For the latter, any modification of a variable is passed back to the start node in subsequent iterations (e.g. moving sum calculation). Note that variables defined by the loop start node itself are excluded as these usually represent loop controls (e.g. "currentIteration").
Ignore empty input tables
If this option is checked, empty input tables and their structures are ignored and will not cause the node to fail.
Allow variable column types
If checked, the loop does not fail when the column types between different table iterations change. The resulting column will have the common super type of the different column types.
Allow changing table specifications
If checked, the table specifications between iterations can differ. If column have been added or removed between iterations, missing values are inserted accordingly in the result table. If not checked and the table specifications differ, the node will fail.

Input Ports

Icon
Any data table
Icon
Any data table

Output Ports

Icon
Collected results from the loop body
Icon
Collected results from the loop body

Views

This node has no views

Workflows

Links

Developers

You want to see the source code for this node? Click the following button and we’ll use our super-powers to find it for you.