Skip to content

Salesforce ITR Evidence

LeafEnterprise owns the full Salesforce ITR evidence mirror for automation, agent retrieval, and savings/audit handoff.

Mirror Coverage

The mirror includes:

  • request rows,
  • status and field history,
  • ContentDocumentLink,
  • ContentVersion,
  • legacy Attachment,
  • ContentNote,
  • FeedItem,
  • FeedComment,
  • extracted file and attachment chunks.

Library Responsibilities

Module Responsibility
LeafEnterprise/salesforce_it_requests/sql_registry.py Azure SQL schema and sync registry.
LeafEnterprise/salesforce_it_requests/evidence.py Evidence bundle and search-document payloads.
LeafEnterprise/salesforce_it_requests/materialize.py Backend-only file body download, immutable storage, text extraction, chunk persistence.
LeafEnterprise/salesforce_it_requests/service.py Workbench run-plan and optimization evidence composition.

API Surfaces

Route Role
POST /api/ops/it-requests/sync/full-mirror Refresh the full Salesforce mirror.
GET /api/ops/it-requests/{request_number}/evidence-bundle Return sanitized request-scoped evidence.
GET /api/ops/it-requests/{request_number}/search-documents Return Azure AI Search / Foundry IQ-ready documents.
POST /api/ops/it-requests/{request_number}/evidence-refresh Materialize files and update evidence chunks.
POST /api/ops/it-requests/{request_number}/run-plan Resolve queueability and exact scope candidates.

Search Document Rule

Foundry IQ / Azure AI Search should index extracted, hashed, request-scoped evidence documents. Do not index opaque raw source links as the primary retrieval record.