Press \
anywhere in ServiceNow.

Find the script the index can't see

Search fourteen sources of everyday script and configuration — Script Includes, Business Rules, Client Scripts, UI Actions, catalog variables, reference qualifiers, transform logic, record producers, Script Actions, Scripted REST. Where the platform's own Code Search is installed it runs first and the rest fill the gaps, because its search groups are configured field by field: UI Action conditions are indexed nowhere, so nothing but the fallback will ever find them.

Every hit is verified against your term in the browser before it is shown. That is not belt-and-braces — an invalid field in an encoded query is silently dropped by the Table API, and the unfiltered result that comes back looks exactly like a match. The Source status drawer keeps the same honesty: no matches, access denied, timed out and capped are four different answers, and it tells you which one you got.

What affects this catalog item

Open a catalog item and get every client script and UI policy bound to it or its variable sets, grouped by the variable they watch. Rows that cannot fire while ordering — inactive, or scoped to RITM and Task views only — are flagged, so "why isn't my script running" answers itself before you open a single record.

Per-variable insight icons

An icon beside every variable on the form. Click one and the panel narrows to that variable alone: the onChange scripts watching it, and what each UI policy does to it — hides, mandatory, read-only, sets value. Attribution is matched on sys_id, not guessed from script text.

Show variable values

Every variable on the item with its current value, variable sets included — and crucially the ones you cannot see. Filter to hidden to find the variable a policy quietly set behind your back.

Debug Timeline

Record one page's interaction and read back what happened: public g_form calls, native field events, GlideAjax timing, and JavaScript errors on a filterable timeline. Best-effort by design — it shows you what ran, not which script ran it, and says so rather than guessing.

GlideAjax rows carry what you would otherwise open the Network tab for: the Script Include, the method, every parameter added, and the decoded response, next to how long the call took and in order with the rest of the interaction — rather than pieced back together from a list of XHRs. Parameter and response names that read like secrets are redacted before anything is shown.

Translation records, one click away

A globe on every label, for the label, plural and hint. Alongside it, a languages glyph — but only on fields whose dictionary type can actually hold per-record value translations, so an icon appearing means there is somewhere for it to go. The defining table is resolved by walking super_class, so a field inherited from task lands on the right dictionary record rather than a dead end.