GlideLens

A lens on ServiceNow forms, catalogs and code: code search, catalog debugging, translation inheritance, form tracing.

GlideLens is a developer's lens on a ServiceNow instance. It answers the questions that cost the most time on a form: what runs here, why did that field change, and where is that string actually defined? Everything happens in your browser, against the instance you are already signed in to, using your own session and your own permissions. WHAT IT DOES Code search across 14 configuration sources Search Script Includes, Business Rules, Client Scripts, UI Actions, Script Actions, Scripted REST operations, catalog client scripts, catalog variables, record producers, transform maps and entries, reference qualifiers and dictionary override logic — for plain text or a "quoted phrase". Where your instance has ServiceNow's own Code Search plugin, that index is queried first and these sources fill in what it does not reach. UI Action conditions, for example, are indexed nowhere and are found only by the fallback. Results are read-only and open the owning platform record. Record Lens Find a table by label or technical name, then search it read-only. The fields it will search are confirmed against the live dictionary and shown to you before the search runs, rather than guessed. Only the sys_id and up to six selected fields are retrieved, every result is re-checked against your complete search term in the browser, and results can be copied, opened, or opened together as a normal platform list. Sensitive value and body fields are never selected for you. Catalog Logic Every catalog client script and catalog UI policy bound to an item or its variable sets, in one panel, with the ones that will not run here marked as such. Per-variable attribution for onChange scripts and UI policy actions. Variable Values Every variable on a Service Portal catalog item with its current value, and whether it is visible, a Hidden type, or switched off by a UI policy or client script. Useful when a form is behaving as though a field exists that you cannot see. Debug Timeline Record one page interaction and read back what happened, in order: g_form calls, native field events, GlideAjax timing and JavaScript errors. GlideAjax rows expand to the Script Include, method, parameters and decoded response alongside the duration, so a call can be read without the Network tab. Translation Lens A read-only report of which field labels, choices, catalog text and getMessage keys have a translation in each active language, on a classic form, a catalog item's definition form or a Service Portal catalog item. Each gap links to the platform record that would hold the translation, prefilled. Every field is routed to the store its dictionary type actually uses, and inherited fields resolve to the table that defines them. A denied or failed read is reported as unavailable, never as missing. On a Workspace record it offers a link to the record's classic form instead. Prefill variables from a ticket Fill a catalog form's variables from an existing request for the user to review before submitting. It waits on the form's own GlideAjax activity rather than a fixed delay, so values set by onChange scripts are not overwritten. A command palette Press \ on any ServiceNow tab. Every command above, plus record helpers and navigation, without hunting through menus. Each command has a short name and a one-line description of what it does, and typing matches either, so you do not have to remember the exact wording. It is fully keyboard-driven, one command can be pinned to the top, and whatever a command opens appears in a tab beside the one you ran it from. WHAT IT DOES NOT DO GlideLens never writes to a record and never submits a form. The single exception is Prefill, which fills unsaved fields on the catalog form in front of you, for you to review — that is the whole point of it. It runs no code from your instance, and renders no instance-provided HTML. Field and parameter names that look like secrets are redacted before display. The Debug Timeline is best effort: it reports the runtime calls it observed and does not promise named Client Script or UI Policy attribution. PRIVACY There is no GlideLens server, no account, and no telemetry. The extension can only reach *.service-now.com, so it could not contact a third party if it tried. Three small things are cached locally in your browser: your pinned palette command and two per-instance maps of what code search can reach. Full detail: https://rushipatel92.github.io/GlideLens/privacy.html REQUIREMENTS A ServiceNow instance you can already sign in to, on a *.service-now.com address. Most features read configuration tables, so an account with developer or administrator roles gets the most from it. Instances on a custom domain are not currently supported. GlideLens is an independent project. It is not affiliated with, endorsed by, or sponsored by ServiceNow, Inc. "ServiceNow" and related marks are trademarks of ServiceNow, Inc.