Debugging a Call Activity

Call activity steps are always displayed in collapsed form in the process model. When you step into a call activity, the process debugger opens the expanded call activity in a new editor tab and also opens a dedicated Trace view for it.

Call activity steps can be looped. This means all the steps within the call activity can be executed multiple times. Call activity steps, including BPMN Call Activity and webMethods Referenced Process (Deprecated) steps support standard loops. Steps with standard loops display a loop marker

in the process editor.

The process debugger does not support webMethods dynamic referenced process steps. Step Over the step to skip it; there is nothing inside it for the debugger to run, so it is bypassed, and you stop at the next eligible step.