To Debug Scripts

• Script Debugger must be open
• Script must have a breakpoint set
• Script must be executing in the same interactive session as the user with the breakpoints

Script Debugging is session and user specific

• Only you are affected by your breakpoints
• Cannot step through scripts running asynchronously (Async Business Rules, Scheduled Jobs, Workflow Scripts)

The Script Debugger only debugs server-side synchronous scripts. It is not possible to step through scripts running asynchronously as they are not running in the same session as the logged in user.

A debugger transaction remains open as long as the user session is valid. If the user logs out, or the session times out (which will occur if paused for too long), the system stops the debugger transaction. If this occurs, it can be re-enabled by selecting the on button, pressing F2, or by closing and re-opening the debugger

TIP FROM THE FIELD

Breakpoints do not need to be removed from a script. If you would like to debug at another time with the same breakpoints, simply close the Script Debugger window to turn off debugging. The Script will execute without pausing at breakpoints until you open the Script Debugger again. This strategy makes it easy for you to control when you want to debug your scripts.