Anatomy of the Script Debugger

The Script Debugger is session specific; no other users are impacted. Each user can only have one Script Debugger console open and executing at a time.

Administrators can use the Script Debugger while impersonating another user, but only if the impersonated user has the admin or script_debugger role and has read access to the target script.

While impersonating another user you can:

• See and change breakpoints that belong to the impersonated user
• View and pause on scripts that the impresonated user has read access to
• The Script Debugger step-through controls also use the read access of the impersonated user. For example, if the impersonated user does not have read access to a function in the call stack, any Step into action insted becomes a Step over action

The impresonated debugging session lasts until:

• You stop impersonating the user
• You log out or the user session ends
• You pause the Script Debugger
• You close the Script Debugger