Stepping Through the Application

Stepping enables you to view the execution of the application step by step.

A debug step can be one of the following:

A step in the execution of the application, such as copy, map, or transition
A predefined action, such as Clear or Prompt

While stepping through the application, you see the progress of the execution on the Design board: the current step is marked red, and the steps that have already been executed are marked orange.

Note Note

A breakpoint takes priority over a step instruction, and always causes the application execution to stop.

End of the note.

The Visual Composer debugger enables you to use the standard Eclipse debug buttons (and hotkeys) to control the runtime execution.

The following table describes the debug buttons that are available in the Debug perspective:

Button	Description
(Resume)	Causes the application to continue to run until a breakpoint is reached, and then the control returns to the modeler.
(Suspend)	Causes the application to stop at the beginning of the next step.
(Terminate)	Causes the debugger processes to terminate. As a result, the browser closes.
(Step Into)	Enables debugging a referenced model, such as a nested model or a modeled service. If the next step is in the same model, then the behavior is the same as for Step Over.
(Step Over)	Continues to execute the next step, and stops at the end of the step. Multiple uses of this button enable you to execute the model step by step. Step Over executes the next step in the current model, even when the next step is a nested model, and stops on the following step in the model. The nested model is executed until completion but you cannot see its steps in Debug View. However, if there is a breakpoint in the nested model, execution stops at the beginning of the corresponding step in the nested model. Note If the last step executed is the last step of a nested model, and Step Over is chosen, the behavior is the same as for Step Return. End of the note.
(Step Return)	Completes the execution of the current nested model, and returns to the next step in the parent model. When the execution is not within a nested model, the behavior is the same as for Step Over.