afv-library/skills/investigating-agentforce-d360/assets/dc/discover_sessions.sql

37 lines
2.3 KiB
MySQL
Raw Normal View History

@W-22707610 feat: add investigating-agentforce-d360 skill Data Cloud 360° view of a single Agentforce session — DC-only, zero Splunk dependency. Pulls 24 STDM + GenAI DMOs via the Data Cloud Query REST API, assembles a hierarchical session tree (Interaction → Step → Generation → GatewayRequest), and renders a human-readable markdown summary with transcript + per-turn topic/action invocations + LLM generations + tool calls + audit chain. Migrated as a standalone Apache-2.0 skill from an internal hub plugin — self-contained, no sibling-skill or plugin dependencies. What this skill answers: - "Trace session <uuid>" / "Summarize what happened in <0Mw…>" - "Find escalated sessions today on Messaging in <org>" - Session discovery by time / agent / channel / outcome / conversation text when the user has no session id What it does NOT answer (use a different surface): - Design-time architecture — use investigating-agentforce-architecture - Runtime planner availability — DC alone can't tell you which topic/action was eligible for the classifier on a given turn Skill layout: - 8 Python pipeline modules (fetch_dc, assemble_dc, render_dc, discover_sessions, resolve_session, dc, storage, config) - 4 _shared helpers (paths, fs_guard, sql, __init__) with skill-scoped DATA_ROOT (~/.claude/data/investigating-agentforce-d360/) - 26 SQL templates under assets/dc/ - 27 test files (367 tests + 18 subtests, 100% passing) - 3 reference docs (artifacts.md, dc_dmo_fields.md, dc_pipeline_contract.md) - SKILL.md (sf-skills frontmatter, license: Apache-2.0, metadata.version: "1.0") - README.md (external-facing quick-start) - tools/grant_allowlist.py (idempotent first-run permission grant) - tools/archive_data_dir.sh (opt-in stop-hook tarballer) Quality gates: - pytest scripts/tests/: 367 passed + 18 subtests, 0 failures - npm run validate:skills: 62 of 62 skill(s) checked, 0 errors - Live end-to-end runs against 3 real Salesforce sessions exercising both the full-tree and STDM-lag gateway-direct render branches - 4 independent code-review rounds (correctness, security, markdown, architecture-critic) — all findings addressed Customer-data hygiene: no live tenant ids, no internal sprint markers, no hub/sibling-skill references. Synthetic fixtures look obviously synthetic (`019dface-…` UUIDs, `0MwTESTMSG…` MessagingSession ids, `00DTESTORG…` org ids, `MyAgent` placeholder agent name). Sibling skill: investigating-agentforce-architecture (PR #278) — same migration pattern, design-time metadata; complementary scope.
2026-05-28 18:57:52 +08:00
-- Session discovery — find candidate sessions by time/agent/channel/outcome/grep.
-- Produces a short row-per-session shape for the picker rendered by
-- scripts/discover_sessions.py. NOT used by the trace pipeline — once the user
-- picks a UUID, the full pipeline runs fetch_dc.py against the 24-DMO waterfall.
--
-- Placeholders (substituted by scripts/dc.py.load_sql):
-- SELECT_LIST — either `s.ssot__Id__c, s.ssot__StartTimestamp__c, s.ssot__EndTimestamp__c,
-- s.ssot__AiAgentChannelType__c, s.ssot__AiAgentSessionEndType__c`
-- OR `DISTINCT <same columns>` when JOINs are present (DC SQL requires
-- ORDER BY columns to appear in a DISTINCT projection).
-- JOINS — zero or more JOIN clauses, newline-separated, or empty string:
-- * `JOIN ssot__AiAgentSessionParticipant__dlm p ON s.ssot__Id__c = p.ssot__AiAgentSessionId__c`
-- (required when filtering by --agent)
-- * `JOIN ssot__AiAgentInteraction__dlm i ON s.ssot__Id__c = i.ssot__AiAgentSessionId__c
-- JOIN ssot__AiAgentInteractionMessage__dlm m ON i.ssot__Id__c = m.ssot__AiAgentInteractionId__c`
-- (required when filtering by --grep)
-- WHERE_CLAUSE — composed by the caller. No "WHERE" keyword. Always non-empty
-- (at minimum the time-range predicate). All user-supplied string
-- literals are single-quote-escaped by doubling quotes (O'Brien → O''Brien).
-- LIMIT — integer, 1..N. Default in caller is 20.
--
-- Field reference:
-- time range → s.ssot__StartTimestamp__c >= '<startISO>' AND s.ssot__StartTimestamp__c < '<endISO>'
-- outcome → s.ssot__AiAgentSessionEndType__c = '<USER_ENDED|ESCALATED|TRANSFERRED|TIMEOUT|NOT_SET>'
-- channel → s.ssot__AiAgentChannelType__c = '<Builder|SCRT2 - EmbeddedMessaging|Voice|...>'
-- agent → p.ssot__AiAgentApiName__c = '<AgentApiName>' (requires participant JOIN)
-- grep → m.ssot__ContentText__c LIKE '%<escaped-pattern>%' (requires interaction+message JOIN)
--
-- All STDM timestamps are UTC.
SELECT {{SELECT_LIST}}
FROM ssot__AIAgentSession__dlm s
{{JOINS}}
WHERE {{WHERE_CLAUSE}}
ORDER BY s.ssot__StartTimestamp__c DESC
LIMIT {{LIMIT}};