#SERVICENOW SCRATCHPAD HOW TO#
#SERVICENOW SCRATCHPAD CODE#

Set Catalog Variables from URL Params (Free tool) Using Custom Search Engines in Chrome to Quickly Navigate ServiceNow Handling 'text/plain' and Other Unsupported Content Types in ServiceNow Scripted REST APIs Getting Help from the ServiceNow CommunityĬan ServiceNow Script Includes Use the 'current' Variable?

#SERVICENOW SCRATCHPAD HOW TO#

'Processors', SRAPIs, and How to Run a Script and Redirect a User From a URL in ServiceNowīetter ServiceNow Notifications (& Another FREE Tool!)ĭebugging Client & Catalog Client Scripts in ServiceNow Use Automated Tests to Validate 'Guided Setup' Completion & Functionality. How to return a CSV file from a Scripted REST API (SRAPI) in ServiceNowĪdding a Guided Setup to Your ServiceNow Application How to Set or Change ServiceNow Application's Repository URL, Credentials, or SSH Key New tool: Get Latest Version of ServiceNow Docs Page How to Get and Parse ServiceNow Journal Entries as Strings/HTML addJoinQuery() & How to Query Records with Attachments in ServiceNowįree, Simple URL Shortener for ServiceNow Nerds (snc.guru) Your ACLs and Business Rules are Broken (Here's How to Fix Them)Ī Faster, More Efficient Client-side GlideRecord (Free tool!)Īnimated Loading Message & Collapsible Details on ServiceNow Form or Field (Client-side)

#SERVICENOW SCRATCHPAD CODE#

The manager field is updated asynchronously when the Assigned to field is updated, so when our logic runs, the assigned_to.manager field has not yet been populated.ĥ Ways to Check your ServiceNow Instance for DANGEROUS CODE in Less Than 5 minutes (You can’t trigger a client script on change of a dot-walked/derived field). I could change that line to g_form.getValue(‘assigned_to.manager’), but that wouldn’t work either because the client script triggers when the Assigned to field is changed, not when the dot-walked Manager field is changed. This means that my g_form.getValue(‘manager’) line would not work. In this case, the issue is being caused by the fact that the Manager field is a dot-walked field. Now that the debugger has helped us figure this out, we might go and investigate why this is. This is causing the script to return early, and not do what I expected it to do. I can use the buttons at the top-right of the debugger to step line-by-line through my code, or even into or out of a given function-call, or I can use step over to remain at the current level of the call stack (meaning, keep the debugger on my code).īy advancing step-by-step through my code, I can see that it’s evaluating my if block to be true, because assigneeMgrID is blank.

Since the code paused after that variable was assigned, we would expect that variable to have a value! that’ll show you the values of the variables in your code at the moment the code halted.Īs you can see in the image to the right, the variables in the local function scope in my code look as you’d expect, except for assigneeMgrID. In the Scope section, Local is usually going to be the most relevant bit. Collapse Call Stack, and you’ll see Scope. By default (in Chrome), this will be just below the Call Stack section on the right side of the debugger. This can all look pretty overwhelming at first, but the main thing to pay attention to, is the Scope section.

Join me after the jump, for a walk-through! In this short article, we’re going to see exactly how to do that, using a not-very-smart Client Script that runs on the Incident form. In fact, you can! Better yet, you can put calls to the debugger directly in your code! The question then becomes: “ How do I trigger the client-side debugger? I can’t easily put breakpoints in my code that runs client-side, especially if it runs on-load right?” The good news is, modern browsers already have an incredible debugger that’s at least as good as the server-side script debugger in ServiceNow, built right in! So, how do you troubleshoot client-side scripts in ServiceNow? Well, since those scripts execute inside the user’s browser, you’re going to have to use some browser-magic to make that happen.

When available, that tool is incredibly useful but unfortunately, it does not work with client scripts. When dealing with server-side scripts, the ServiceNow Debugger makes debugging relatively easy (most of the time), as you can actually see into the call stack, and the contents of your server-side variables as you step through your code, line-by-line.

Servicenow scratchpad