Properties
A human-readable name for the component.
- 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.
Select the variables that will be iterated. Move a variable from the left column to the right column to select it. Any number of variables can be iterated.
Opens the Iteration Values dialog, which has one column for each variable selected in the Variables to iterate property.For each variable, add as many values as required, one per row. For example, if you have a text variable “City” with three values “London”, “Paris”, and “New York”, the Fixed Iterator will run the attached component three times, once with the “City” variable set to “London”, again with it set to “Paris”, and finally with it set to “New York”.
If a failure occurs during any iteration, the failure link is followed. This parameter controls whether it’s followed immediately or after all iterations have been attempted.
- 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 doesn’t run successfully, fail immediately.
Select Yes to stop the iteration based on a condition specified in the Condition property. The default setting is No.For this property to be available, set Concurrency to Sequential.
Select the method for creating the stop condition.
- Simple: A no-code condition editor opens, where you specify an Input Variable, Qualifier, Comparator, and Value. This is the default setting.
- Advanced: A code editor opens, where you write the condition manually using SQL.
Click the gear icon to open the Condition dialog. Use + and - to add or remove conditions. Each condition has the following columns:Input variable: An input variable to form a condition around.Qualifier: Select whether the condition should be applied (Is, the default) or reversed (Not). Selecting Not reverses the comparator, so Equal to becomes “not equal to”, Less than becomes “greater than or equal to”, and so on.Comparator: Select from:
- Less than: Value of the input variable must be less than the specified value.
- Less than or equal to: Value of the input variable must be less than or equal to the specified value.
- Equal to: Value of the input variable must be equal to the specified value.
- Greater than or equal to: Value of the input variable must be greater than or equal to the specified value.
- Greater than: Value of the input variable must be greater than the specified value.
- Blank: Checks whether the input variable is empty.
Enter the condition manually in the code editor using SQL.This property is only available when Stop on condition mode is set to Advanced.
When multiple conditions are present, they can be separated by And or Or.
- And: All the conditions must be true.
- Or: Any of the conditions must be true.
Use this to set a maximum limit on the number of concurrent iterations that will be attempted. This is important to ensure that the workload is orchestrated to accommodate any source and target constraints.If you leave this property blank, no upper limit will be placed on the number of concurrent tasks that can be attempted.If you stack iterators, concurrency limits will multiply exponentially. For example, if you stack an iterator with Maximum concurrent iterations set to 10 on top of another iterator with Maximum concurrent iterations set to 10, the component could attempt 100 concurrent iterations.This property is only available when Concurrency is set to Concurrent.
If this is set to Yes, the Task history tab and Observability dashboard will show each iterator variable as a name/value pair in the component result message for each iteration. The default is Yes.
If this is set to Yes, the Task history tab and Observability dashboard will show each iterator variable as a name/value pair in the component result message for each iteration. The default is Yes.