inspect

Unified record / flow / XML inspector. Four modes selected by --flow and --from-xml.

The inspect command has four modes. Without flags, it pretty-prints a single record with display values and reference links. With --flow, it inspects a live Flow Designer flow, subflow, or action type by sys_id. With --from-xml, it analyzes an exported update-set XML payload. Combining --flow --from-xml walks flows inside an XML export offline.

sn inspect <table> <query|sys_id>

Pretty-print a single record with display values.

Arguments

Name	Required	Description
table	Yes	The table to query.
query\|sys_id	Yes	Encoded query string or 32-char sys_id.

Examples

sn inspect sys_script_include "name=TestUtils"

sys_script_include: TestUtils

name TestUtils

api_name global.TestUtils

active true

script (4,231 chars)

sys_scope Global [global]

sn inspect <sys_id> --flow [--pills] [--grep <pattern>] [--values] [--json]

Inspect a live Flow Designer flow, subflow, or action type.

Arguments

Name	Required	Description
sys_id	Yes	32-char sys_id from sys_hub_flow or sys_hub_action_type_base.

Flags

Flag	Default	Description
--pills	—	Dump label_cache pills (flow / subflow only).
--grep <pattern>	—	Filter --pills output by substring.
--values	—	Include decoded `values` blobs on every step.
--json	—	Machine-readable output.

Examples

sn inspect 57a1088983940310d3cfe5d0deaad330 --flow

Flow: Catalog Flow Binding Test

type=flow status=published active=true

trigger: service_catalog (Hardware Request)

actions (2):

1. Get Catalog Variables

2. Log

sn inspect <source> --from-xml [--only-flow <name|sys_id>] [--pills] [--grep <pattern>] [--table <t>] [--json]

Analyze an exported update-set XML payload — file, sys_id, or <table>:<sys_id>.

Arguments

Name Required Description

source

Yes

Local .xml file path, a sys_update_set / sys_update_xml sys_id, or

: for any record.
 Flags
 Flag Default Description
--only-flow <name|sys_id> — Zoom into one flow within the export. `--flow` is a mode switch; `--only-flow <name>` is the value form.
--pills — Dump label_cache pills (requires --only-flow).
--grep <pattern> — Filter --pills output by substring.
--table <table> — List records of a specific table.
--json — Machine-readable output.
 Examples
   sn inspect export.xml --from-xml
 Source: file export.xml
Shape: update-set
Payloads: 26
Tables (INSERT_OR_UPDATE rows):
  sys_hub_flow                3
  sys_hub_action_instance_v2  14
  sn inspect export.xml --from-xml --only-flow 'Onboarding' --pills
 
sn inspect <file> [<flow-sys_id>] --flow --from-xml [--json] Offline walk of a flow in an update-set XML export — useful before pushing the export to another instance.
 Arguments
 Name Required Description
file Yes Path to a local update-set XML export.
flow-sys_id No Optional 2nd positional — zoom into a specific flow (same effect as --only-flow).
 Flags
 Flag Default Description
--json — Machine-readable output.
 Examples
   sn inspect export.xml --flow --from-xml
 Inspecting export.xml
Flows (3):
  57a1088983940310...  flow      Onboarding
Record counts (12 tables):
  sys_hub_flow                           3
  sn inspect export.xml 57a10889... --flow --from-xml
 
 Use plain sn inspect <table> <query> for routine record browsing. Reach for --flow when debugging live Flow Designer state and --from-xml when analyzing an export before pushing it to another instance.
  Previous
 init Next
 instance