Question first
Start with the support question: “Which active items need attention?” rather than an implementation detail.
CLEAN-ROOM RECREATION
ServiceNow List Link Builder — Demonstration
Make a support question easier to act on.
A static demonstration of how a small, guided filter recipe can turn a recurring support question into an understandable sample list query—without contacting a live system.
- SYNTHETIC SCHEMA
- NO LIVE INSTANCE
- OFFLINE EXAMPLE
01 / The problem
Useful filters should not require a decoding exercise.
Service-management lists are powerful, but repeated searches can feel opaque when people must translate a question into fields, operators and ordering every time. This recreation focuses on the explanatory layer: a safe recipe that makes the intent visible before any query exists.
Guided choices
Choose a small record type, then an explicit field, operator, value and optional sort.
Readable result
Return a plain-language statement beside a clearly labelled illustrative fragment—not a destination link.
02 / My bounded contribution
I shaped the workflow, not a live tenant.
The work represented here is workflow simplification, metadata modelling, interface design, validation and iterative testing. The private-source prototype informed the capability story; this page is independently written and does not reproduce its code, schema or links.
- Turn frequent questions into a short, repeatable decision path.
- Model only the fields needed to explain a safe example.
- Make the generated outcome understandable enough to check.
- Keep privacy and non-live boundaries visible throughout.
Evidence status
Private source: a metadata-backed browser prototype for repeatable list-filter construction.
This page: a hand-written, clean-room recreation using invented fields and sample values only.
03 / How the approach works
A small recipe, checked before it is explained.
The architecture deliberately stops at a sample fragment. It has no authentication, API call, record read, record write or outbound navigation.
- Synthetic metadataA small hand-written field list with fictional record types.
- Guided controlsRecord type, field, operator, value and optional sort.
- ValidationOnly compatible choices form a coherent demonstration recipe.
- Human explanationPlain language plus an illustrative encoded fragment.
04 / What this page demonstrates
A deliberately small synthetic schema.
These labels are newly authored for this portfolio. They are not a mapped, filtered or anonymised copy of any workplace configuration.
| Record type | Demonstration fields |
|---|---|
| Demo Incident | Number · Short description · Active · State · Priority · Updated · Caller · Assigned team |
| Demo Request | Number · State · Requested for · Opened · Description |
| Demo User | Display name · Department · Location · Active |
| Demo Team | Name · Active |
05 / Sample presets and recipe
Three reusable starting points.
The examples below are static evidence of the intended interaction. A visitor can understand the approach without submitting data, logging in, or sending anything away from the browser.
Preset menu
- 01 — Active high-priority incidentsDemo Incident · Active is true · Priority is high · newest update first
- 02 — Open requests for a demo userDemo Request · State is open · Requested for is Casey Rivera
- 03 — Incidents assigned to a demo teamDemo Incident · Assigned team is Demo Support Team · Active is true
Recipe / 01
Active high-priority incidents
Question: Which active demonstration incidents deserve early attention?
Plain-language explanation: Find active Demo Incidents with high priority and place the most recently updated examples first.
Illustrative encoded fragment
active=true^priority=high^ORDERBYDESCupdatedThis is a sample fragment only. It cannot be opened, copied from a live system, or connected to an instance.
06 / Learning
Clarity is a support feature.
A good shortcut does more than generate syntax. It makes the choice legible, gives people a reusable starting point, and exposes enough reasoning that the result can be checked. Keeping a fixture deliberately small also makes privacy review and maintenance more manageable.
Transferable capabilities
- Support workflow analysis
- Business and systems analysis
- Metadata modelling
- Interface design
- Validation design
- Privacy-aware delivery
07 / Boundaries
Useful as an explanation. Deliberately not a live tool.
What this does
- Demonstrates a generic filter-building pattern.
- Uses a hand-written synthetic schema and fictional examples.
- Shows a qualitative workflow and sample output.
What this does not claim
- No live instance, tenant, records, API, login or data connection.
- No production compatibility, performance result or adoption claim.
- No reproduction of original Power App code or private configuration.
ServiceNow is a trademark of ServiceNow, Inc. This independent portfolio demonstration is not affiliated with, endorsed by, or connected to ServiceNow or any customer instance.