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

54 lines
2.0 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 interactions (turns + session-end event) — reusable for any WHERE.
-- DMO: ssot__AIAgentInteraction__dlm
--
-- Placeholders (substituted by scripts/dc.py.load_sql):
-- WHERE_CLAUSE — the filter expression, no "WHERE" keyword
-- ORDER_BY — full "ORDER BY <col>" or empty string
--
-- One row per turn plus one SESSION_END row per session.
-- Type enum: TURN | SESSION_END.
--
-- Casing gotcha: DMO name uses `AIAgent` (uppercase AI). Field names use
-- `AiAgent` (lowercase i). See references/dc_dmo_fields.md.
--
-- trace_id gotcha: `ssot__TelemetryTraceId__c` is often empty on real orgs
-- (verified live). The runtime trace_id lives inside
-- `ssot__AttributeText__c` as HTML-escaped JSON, key `internalTraceId`.
-- Consumers must `html.unescape()` + regex-extract. Used to join with
-- GenAIGeneration (generationId via Step) and TelemetryTraceSpan.
SELECT
ssot__Id__c,
ssot__AiAgentSessionId__c,
ssot__AiAgentInteractionType__c,
ssot__TopicApiName__c,
ssot__StartTimestamp__c,
ssot__EndTimestamp__c,
ssot__PrevInteractionId__c,
ssot__SessionOwnerId__c,
ssot__IndividualId__c,
ssot__InternalOrganizationId__c,
ssot__TelemetryTraceId__c,
ssot__TelemetryTraceSpanId__c,
ssot__AttributeText__c
FROM ssot__AIAgentInteraction__dlm
WHERE {{WHERE_CLAUSE}}
{{ORDER_BY}};
-- ============================================================================
-- EXAMPLE WHERE clauses (pass via where_clause=)
-- ============================================================================
-- All interactions for one session
-- WHERE → ssot__AiAgentSessionId__c = '<session_id>'
-- ORDER BY → ORDER BY ssot__StartTimestamp__c
-- TURN rows only (exclude SESSION_END)
-- WHERE → ssot__AiAgentSessionId__c = '<session_id>'
-- AND ssot__AiAgentInteractionType__c = 'TURN'
-- Interactions handled by a specific topic across sessions
-- WHERE → ssot__TopicApiName__c = 'Order_Management'
-- AND ssot__StartTimestamp__c >= '2026-01-01T00:00:00.000Z'