When you are debugging routines, you can set line breakpoints and variable breakpoints. Both breakpoint types are saved upon termination of a debug session.
When the workbench is running a routine and encounters a breakpoint, the routine temporarily stops running. Execution suspends at the breakpoint before the statement is executed, at which point you can check or edit the contents of variables. You can then step over (execute) and see what the effect of the statement is.
With the debugger, setting breakpoints is easily accomplished by way of pop-up menus in the debugger editor and Variables view. Once set, you can disable breakpoints so they do not suspend execution and then, later, enable them again.
When you are editing routines, you can set and remove line breakpoints in the routine editor if the routine has been deployed to a database.
The breakpoints that you set in the routine editor are saved in the workspace. If the routine is moved to a different workspace or the routine is renamed, the breakpoint information will be lost.
If you move or copy the routine to a different data development project and do not change the routine name, the breakpoint information remains with the routine. The projects must have the same database connection information.