Dynamic Apps Platform : webMethods BPM Process Development Help : Process Engine Processing : About Looping : About Standard Looping
About Standard Looping
When a subprocess or call activity is configured for standard looping, Software AG Designer marks the step with a loop marker .
To implement standard looping, you define a loop expression on the Loop page in the Properties view for the step. As long as the conditions defined in this loop expression are true, the step will loop back to its input upon completion. The first loop iteration receives the incoming pipeline, and after that, the output of that loop becomes the input to the next loop iteration. For more information, see:
*Configuring a Subprocess Standard Loop
*Configuring a Call Activity Standard Loop
For subprocesses and call activities created before Designer version 8.2, the loop expression is tested after completion of the activity. With Designer version 8.2 and later, you can configure this behavior to occur either before the activity or after the activity.
With Designer version 8.2 and later, when you configure standard looping behavior, you can also specify a Maximum loop count. This enables you to specify an absolute maximum number of loop iterations, regardless of the evaluation of the loop expression. You can set this number as a static integer value, or as a pipeline field value.
You can monitor loop data stored in the Process Engine. With Designer version 8.2, a loop logging level is available in the process audit logging Minimum logging level property (6-Process and all events, activities, and looped activities). In Designer version 9.0, level 6 is eliminated and logging is included in level 5 (5-Process and all events, activities, and looped activities).
After each loop is executed, the value of the LoopCounter parameter in the document pub.prt:ProcessData is incremented. To create a complex loop expression that makes use of the LoopCounter parameter, you can map the parameter into the generated service for the step that is being looped.
When you are looping over a subprocess or call activity step, the LoopCounter parameter value is accessed with the input data mapping and output data mapping services within the process package in Integration Server. If these services are not modified, the LoopCounter value will remain at zero while the steps inside the subprocess or call activity step execute another iteration.
Copyright © 2017 Software AG, Darmstadt, Germany.

Product LogoContact Support   |   Community   |   Feedback