The Debugger Toolbar is located at the top of the Debugger tab and allows you to interact with the suspended request that is currently selected.
Debug in the Public Area: starts the Debugger in the Public Area. See more about Debugging in Public and Personal Areas;
Step Over (F10): steps the execution trace to the next element in the same flow or screen "level";
Step Into (F11): steps the execution trace to the first element "inside" elements like:
Execute Process elements;
Execute Action elements which execute user-defined actions;
Assignments of Assign elements.
Stepping into any other element has the same result as a Step Over;
Step Out (Shift+F11): continues the execution trace to the next element in the outer "level" of the flow or screen, i.e., it "gets out" of the current flow or screen;
Break On All Errors: forces the Debugger to suspend the execution of requests whenever handled or unhandled exceptions occur;
You have an alternative command to execute the request until it reaches an element on the canvas. For that, you have to right-click on the element on the canvas (or in the eSpace tree) and select the Continue To Here option in the pop up menu.
All the above commands stop the execution of the request at breakpoints, except for the Abort Request command, and obviously the Break On All error option.
You may also find all these commands in the Debug menu.
Using Step Commands on Widgets
Step commands have a particular behavior on widgets:
They don't stop on widgets unless the widget has a breakpoint, or is designed using elements to be evaluated at runtime as, for example, widgets designed using user-defined functions.
The order that step commands follow widgets on the screen is the same by which they are rendered and not the order the widgets are displayed on the screen.
Debug an eSpace | Debugger Tab | About Requests | About Breakpoints | Analyzing the Scope Tabs | About Watches | Debug Menu