Practice Using the Script Debugger - Call Stack
- Navigate to System Definition > Script Includes
- Locate and open the SlaTargetNotification Script Include
- Set a breakpoint in this script by clicking in the gutter to the left of the line beginning with gs.log
- Select the Open Script Debugger button on the Syntax Editor toolbar. The Script Debugger opens in another window
- Notice the list of breakpoints now includes the one you just set in step-3
- Select any one of the Lab 5.1 Business Rule Debugging lines to load that script in the code pane
- Update the breakpoints so only the line of code beginning with var createdValue and try are set
- Keep the Script Debugger window open. Forcte the Lab 5.1 Business Rule Debugging Business Rule to execute ->
- Open any active Incident, change the State value to anything except Closed
- Save (not Submit) the record, remain on the form
- Select Start Debugging
- You are stopped at the first breakpoint in the Lab 5.1 Business Rule Debugging script. Review the information displayed in the Call Stack and Transaction Detail on the left-side of the screen
- How can you be sure which script you are currently debugging? What does the Code Pane Header read?
- Notice the very next line in the script after the breakpoint you are currently paused at calls the SlaTargetNotification Script Include. Select the Next Breakpoint button one time
- Notice the information in the Call Stack now includes the Scripts Includes breakpoint details
- How can you be sure which script you are currently debugging? What does the Code Pane Header read?
- Select the Next Breakpoint button one time
- Notice the information in the Call Stack on the left-side of the screen changed
- What does the Code Pane Header read?
- Select the Next Breakpoint button one last time to complete the execution of the script
- Close the Script Debugger window