It could possibly be one of the most welcomed features of Microsoft SharePoint Designer 2013 and the Windows Azure Workflow (WAW) framework. There has been many an occasion where the ability to iterate or loop through a set of tasks was highly desired yet, to the dismay of most of us, it required a little bit of code cutting.
Looping shows a huge change in mindset from the development team. My guess for the delay in the release of such a capability was the potential risk, mainly in performance, that a poorly defined loop would cause within the SharePoint farm. It is extremely important to note that this risk hasn’t completely been removed as we can still define the number of iterations, but the key point is that the grunt work is now handled outside the farm by WAW.
We have two looping options within SharePoint Designer 2013: the “for loop” and the “while loop”.
The for loop is labelled as Loop n Times where ‘n’ is the number of times that the loop will execute. The value ‘n’ can be supplied directly or retrieved through a workflow lookup.The while loop is labelled as Loop with Condition where the loop will run continuously whilst the specified condition evaluates true.
Defining far more complex workflows is now at the fingertips of the power user. SharePoint admins need not fret too much as the direct impact on farm performance has been greatly minimised. Everyone wins it seems.
I am definitely sold on the idea.
You can read more about Professional Advantage and SharePoint here.