Iterator properties
To attach the iterator to another component, use the connection ring beneath the iterator to connect to the input of the other component. The two components will automatically "snap" together, with the iterator component sitting on top of the other component, and can be dragged around the canvas as a single component. For more information about stacking and detaching iterators, read Stacking and detaching iterators.
If you need to iterate more than one component, put them into a separate orchestration pipeline or transformation pipeline and use a Run Transformation or Run Orchestration component attached to the iterator. In this way, you can run an entire pipeline flow multiple times, once for each row of variable values.
Query = code editor
Manually write the SQL query if Mode is set to Advanced.
Concurrency = drop-down
- Concurrent: Iterations are run concurrently.
- Sequential: Iterations are done in sequence, waiting for each to complete before starting the next. This is the default setting.
Full SaaS deployments are limited to 20 concurrent tasks, with additional tasks being queued. Hybrid SaaS deployments have 20 concurrent tasks per agent instance, with a maximum of 100 instances if configured accordingly.
Column Mapping = column editor
Map the columns in the target table to environment variables. Click + to add a mapping and enter the following:
- Column Name: Select a table column name.
- Variable Name: Select an existing variable name.
Order By = dual listbox
Move columns to the right-hand box to define the "order by" sequence.
This property is only available when Concurrency is set to Sequential.
Sort = drop-down
Choose to order by ascending or descending. The default is ascending.
This property is only available when Concurrency is set to Sequential.
Break on Failure = drop-down
- No: Attempt to run the attached component for each iteration, regardless of success or failure. This is the default setting.
- Yes: If the attached component does not run successfully, fail immediately.
If a failure occurs during any iteration, the failure link is followed. This parameter controls whether it is followed immediately or after all iterations have been attempted.
This property is only available when Concurrency is set to Sequential. When set to Concurrent, all iterations will be attempted.