Press \
anywhere in ServiceNow.

Which translations are missing, and where they would go

A read-only report over every field, catalog variable, choice and getMessage key on the surface in front of you, against every active language. A gap links to the record that would hold the translation, prefilled with the exact keys — so closing it is a save, not a search. It runs on a classic form, a catalog item's definition form and a Service Portal catalog item; on a Workspace record the same command offers a link to the record's classic form, where it runs.

The store depends on the dictionary type, and getting that wrong is silent: translated_field values live in sys_translated keyed by the source string, not in sys_translated_text. Labels resolve through super_class, so a field inherited from task lands on the right dictionary record. Absent data is never counted as coverage: a denied read stays Unavailable and stays out of the denominator.

Variable Values, including the ones you cannot see

On a classic RITM or record-producer target, compare the raw value stored in the database with the raw value now held by g_form, so an onLoad change is visible without mistaking reference or choice labels for differences. On a verified Workspace record — a Service Operations Workspace request item, or a supplier case or supplier task in Source-to-Pay Workspace — the same command checks a narrower evidence-backed set after confirming the visible record, the Variable Editor, read permission, and each raw value's shape. Each supported surface has its own verified type list rather than inheriting another's. Partial and stored-only results say plainly what was not compared; every other Workspace experience and table remains unsupported. On an ordering form, the same command keeps its current best-effort live-value and hidden-variable view.

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.

Catalog Logic: what actually affects this 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.

Record Lens: find the record, skip the list-page detour

Find a table by label or technical name without loading the full table catalog. GlideLens can preselect the current page's verified table — including on a classic *_list.do list page — then shows exactly which live dictionary-confirmed fields it will search: no guessed column silently becoming an unfiltered read.

Only the sys_id and up to six selected fields come back. Safe presets are intersected with the live dictionary and sensitive value/body fields are not automatic. Every text result is checked against the complete term in the browser; copy an ID or URL, open the form, or open only the verified set as a platform list.

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.

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.