Using HolySN.
What every part of the extension does, what it asks of your instance, and how it behaves when the platform does not cooperate.
Getting started
- InstallWhat HolySN needs from your browser, and how to add it from the Chrome Web Store.
- Quick startThe first ten minutes: the palette, the update set panel, and the three settings worth changing before anything else.
- KeyboardEvery chord the extension claims, where each one is bound, and which of them the platform can take away.
- The panelEvery block of the panel, top to bottom, and what each of the five tabs holds.
Using it
- Command paletteOne prompt for navigation, queries, scripts and toggles, with a listener the platform cannot swallow.
- Dark modeA recolour of the platform's own design tokens, not a filter over the page.
- Update setsThe guards on a save, Auto-Insert, the checks that read a set before you ship it, and the deploy to your other instances.
- In-page tabs and split viewRecords as tabs inside the instance, split panes by dragging, and the rules that keep it from breaking navigation.
- Record and replayCapture a click path once, then have it prove itself again later.
- Table inspectorEverything attached to a table, in one drawer, read through the ancestry and exportable as XML.
- Code searchEvery script field on the instance, including the ones the platform's own search leaves out, and how the results page gets a token without putting it in a URL.
- Background scriptsRunning a script without leaving the page, the panel beside the editor, and why this is the most careful code in the extension.
- The code editorWhere a real editor replaces a text area, what it knows about ServiceNow, the widget toolbar, and the four traps that cost a day each.
- Comparing recordsTwo records, the same record on two instances, and the line diff that replaces the platform's own compare panel.
- Flows and catalog itemsReading a flow from its own tables, and answering what breaks if you change a catalog variable.
- ThemesRepainting the instance in your own colours, what the editor can honestly show you, and why the preview cannot disagree with what is saved.
- Saved scriptsYour own script library, the four kinds, libraries pulled in with a comment, and handing one to a colleague.
- InstancesTelling your instances apart at a glance, marking one production, choosing where a deploy goes, and moving to a faster node.
- Attachments and versionsReading every attachment of a record in one place, checking and fixing a data file, the version history of a record, and who a highlighted name belongs to.
- VS CodeEditing a ServiceNow script field in VS Code, with the editor never talking to the instance and your session never leaving the browser.
- Choosing list columnsSearch, technical names and dot-walked fields inside ServiceNow's own Personalize List Columns dialog.
- Script blameWho wrote each line of a script field, when, and in which update set, the way git blame says it.
- Form rewindThe form itself, as it was after any earlier save, with who changed each field.
- Collision radarWhen a form opens, see whether someone else is changing the same record in another update set.
The assistant
Account and team
- Account and syncSigning in, what follows you to another machine, and what the session does in a second tab.
- ProfilesWhat a profile carries, what it deliberately does not, and why the active one is remembered per account.
- Vault and securityWhere credentials live, what the server holds, and which realm is allowed to ask for what.
- The shelfPublishing something you wrote, installing something somebody else wrote, and the four rules that make that safe.
- Free, Plus and ProWhat each plan holds, the Pro tools, the three devices a paid account may use, and how the assistant's monthly allowance is counted.
- People and messagesFollowing by @handle, profiles, who may write to you, blocking, and the chat inside the instance.