How can we help?

The extension looks for an active tab with a *.service-now.com URL. Make sure you have a ServiceNow tab open and that you're logged in. If you're behind a custom domain or a VPN that rewrites URLs, the extension may not detect the instance automatically — in that case, fields won't load, but you can still type a query manually.

First, make sure your ServiceNow session is active — open the SN tab and check that you're not on a login page. If your session is fine, try clicking the ↻ refresh button next to the Field label to force a fresh fetch and clear the cache. Fields are cached for 1 hour per instance, so a stale cache can sometimes cause issues after a SN upgrade.

Templates are stored in Chrome's local extension storage. They persist through browser restarts but are cleared if you uninstall and reinstall the extension. To prevent data loss, use the Export button in the Templates section to save a JSON backup before uninstalling. You can re-import this file after reinstalling using the Import button.

Yes — PDIs are standard *.service-now.com instances and are fully supported. The extension will detect your PDI automatically as long as you're logged in on that tab.

No. The extension never reads, stores, or transmits your password or session token. It uses your browser's existing session cookie passively (via credentials: 'same-origin') to fetch field metadata from your instance — the same way the ServiceNow UI itself does. All data (templates, field cache, last-used state) is stored locally in Chrome's extension storage and never leaves your machine.

When you select a field that is a reference type (marked with a REF badge in the dropdown), a resolver panel appears below the field. Type a display name — for example a user's full name for assigned_to — and matching records will appear. Click a result to populate the Value field with the correct sys_id automatically.

The Advanced field lets you paste raw ServiceNow query syntax that gets appended to your built conditions with a ^ separator. This is useful for complex encoded queries, JavaScript conditions like javascript:gs.getUserID(), or any query fragment that the builder doesn't cover directly.