Embedded Loops
Updated: May 13, 2016
Applies To: System Center 2012 SP1 - Orchestrator, System Center 2012 - Orchestrator, System Center 2012 R2 Orchestrator
In System Center 2012 - Orchestrator, looping can be configured for any runbook. By using loops, you can build automatic retries and monitor at any location in a runbook.
Each activity can create a loop so that you can retry operations if they fail or test the output information of the activity for valid data. You can also use these mechanisms to build wait conditions into your workflows.
When a loop is configured for an activity, it continues to run with the same input data until a desired exit looping criteria is reached. The exit criteria is built in a similar way as smart link configurations. You can use any published data item from the activity as part of the exit or do not exit configuration. Included in the common published data are special data items such as Loop: Number of attempts and Loop: Total duration that let you use information from the loop itself in the looping conditions.
Loops run one time for each incoming piece of data that is passed to the activity. For example, consider a runbook that uses a Query Database activity followed by Append Line. If the Query Database activity returned three rows, the Append Line activity would run three times. If you have a loop on the Append Line activity, it would run three separate loops. After the first data item has looped through the Append Line activity, the next item goes through Append Line and loops until it exits, and then the third begins. After all three items have been processed, the next activity in the runbook runs.
Configuring Looping
Use the following procedure to configure looping.
To configure looping
Right-click an activity in the runbook to select Looping. The Looping Properties dialog box opens.
On the General tab, click Enable.
In the Delay between attempts box, type the number of seconds to pause between each attempt to run the activity.
Exit and Do Not Exit Conditions
The rules on the Exit tab specify the conditions that determine whether the loop exits. The rules on the Do Not Exit tab specify the conditions that cause the loop to continue.
Important
The rules on the Do Not Exit tab supersede the rules on the Exit tab.
The rules within each tab are joined by using an Or condition. Only one of the conditions on a tab must be true for the entire tab to be true.
Use the following procedure to add or remove an Exit condition.
To add an exit condition
In the Looping Properties dialog box, click either the Exit tab or Do Not Exit tab, and then select the condition listed in the box, or click Add to add a condition.
Important
To change the values that make up the rule, you have to select each underlined portion of the link condition.
Click the listed activity in the condition to open the Published Data dialog box.
Check the Show common Returned Data box to display properties that are common to all activities.
Select a property from the published data, and then click OK. The criteria expression is changed depending on the type of data that the property returns.
To change the different parts of the expression, select the underlined text and either select or type in an appropriate value. For more information about criteria, see Smart Link Criteria.
Click Finish.
To remove an exit condition
In the Looping Properties dialog box, click either the Exit tab or the Do Not Exit tab.
To select the condition you want to remove, click Or to the right of the link condition, and then click Remove.
Click Finish.
See Also