FEATURE SPEC

Questions or comments?

Post them as a comment on the tracking issue -- requires a GitHub account with access to this repo.

Saved Queries

Parent Feature Set: ../concept.md.

Note

Following information is reverse engineered for [AI-DLC]. Review and remove this note before proceeding.

Important

To follow the AI-DLC process, fill this spec with PM assistance first.

GitHub Issue Description (verbatim)

Issue #616, titled "[Reporting] Saved Queries":

Summary

Feature set

No Acceptance Criteria, Expected Business Value, or Additional Context sections were present on this issue — stating that fact rather than inventing content.

Matching PRD Content

Reproduced verbatim from ../reference/Reporting_PRD_v3_2026-07-17.docx, §3 (Saved Queries) and §4 (Flows 3–4).

Saved Queries (replaces Pinned Workspace) — Any rendered view can be saved by the user. Novaworks stores the query definition — the natural language query string, interpretation applied, time range, and active segment filters — as a saved record in a Novaworks-owned persistence layer. When the user opens a saved query, Novaworks re-executes it against current live data via the AI Data Explorer integration and renders a fresh result.

ServiceNow AI Data Explorer does not natively support pinning or persistent view auto-refresh. Saved Queries achieve the same user outcome — a recurring report that stays current — through Novaworks-owned persistence and on-demand re-execution rather than a pinned auto-refresh mechanism. Building a native pinning and auto-refresh layer: not in scope.

Saved queries can be renamed, reordered, and deleted by the user. Each saved query displays the last-run timestamp and can be re-run manually. Time range and segment parameters can be adjusted before re-running without creating a new saved query. Saved queries are personal — not shared by default. Explicit sharing with a named, permissioned colleague is Phase 2.

Flow 3 — Save: Every rendered view carries a 'Save this query' action. After saving, Novaworks stores the query definition (query string, interpretation applied, time range, segment filters) in the user's Saved Queries. The user can rename the saved query, adjust parameters before re-running, and delete it. Saved queries re-execute against live data on demand — not on a background auto-refresh cadence.

Flow 4 — Re-run a Saved Query: The user opens Saved Queries / My Workspace, selects a saved query, optionally adjusts the time range or segment filter, and clicks Run. Nova re-executes against current platform data and renders a fresh Canvas view. The last-run timestamp updates. Adjusted parameters become the new saved state automatically.

§5 persistence note: Novaworks owns the persistence layer (query definition stored in x_nova_corehcm_saved_report or equivalent). AI Data Explorer executes on re-run. Auto-refresh is NOT used — re-execution is always user-initiated.

Sources

• GitHub issue #616
• ../reference/Reporting_PRD_v3_2026-07-17.docx, §3, §4, and §5