One of the coolest developer tools in the Quebec release is the Script Tracer. Script tracer helps you identify scripts that perform the GlideRecord operations down to the exact line of code during execution. This reduces the number of scripts that may have issues and need to be debugged. This saves time and improves productivity. Note:b /Script Tracer requires the admin role. You can find the Script Tracer by navigating to System Diagnostics > Script Tracer.
Debugging in ServiceNow is am essential skill to master. An array of tools are available to help developers understand what the system is doing and narrow down where unexpected behavior is happening. Today we will look specifically at several ways to debug when doing scripting. Session Debug A feature released in the New York release unified the session debugging modules. A session is a unique login for a unique user - typically one browser on one device.
It is quite common when developing and troubleshooting integrations that a ServiceNow developer may need some logging around API access. This logging can be required in both directions - in outbound API access of some external service or when providing an API for an external service to integrate inward to your instance. In this blog post, we will examine strategies for outbound logging. Log Levels There are three levels of Outbound Web Service Logging: Basic, Elevated and All.
Have you ever run into unexpected behavior when making inbound REST calls to your ServiceNow instance? Perhaps the result of a GET doesn’t contain all of the records you expect it to, or nothing happens when you try to modify a record. In this post, we’ll explore some of the options available for debugging inbound REST API calls and the Business Rules / ACLs that might be impacting those calls.