Script Debugger - Support and Troubleshooting

Script Debugger Summary The Script Debugger allows application developers to debug server-side JavaScript. The Script Debugger can assist in debugging unexpected results when steps to reproduce an issue are available. A generic flow to use the script debugger would be to:

Review code Set breakpoints in places of interest Open the debugger Reproduce the issue Live view code in debugger to understand behavior Release All currently supported environments.

Instructions When a CI is created, a business rule calls script include AssetandCI.createAsset() to create an asset for such CI. Let's use this OOB process as an example on how to use the Script Debugger.

Open the script include AssetandCI. Click on the line number for the line of interest to create a breakpoint. Click on the "Open Script Debugger". Reproduce issue and the code should stop at the breakpoint. Open the tab with the script debugger. On Script Debugger further investigate issue. Above we can see the three main sections of the Script Debugger: Left: Breakpoints/Call Stack Middle: Javascript code Right: Objects in memory Issues

Script Debugger not called

Not all scripts work with script debugger, discovery_sensor scripts is an example. Furthermore, the debugger is for the current user session only. Therefore scripts running in a different user session will not be debugged. The debugger is used often with Business Rules and Script Includes. As a workaround, create a script include and call it from the code which needs to be debugged.In the following example a script include DebugSensor was created to be called by a discovery sensor in order for it to be caught by the Script Debugger.

Note: Discovery inputs are processed in a different session. In order to be able to debug such scripts, see Ecc Queue Processing section "Debug Processing of ECC Queue Records".