Data Model and ER Diagrams

Purpose

This section documents the data architecture behind Document Insights — the Salesforce objects it uses, how they relate, and how data flows through them. It gives developers and architects a clear picture of where extracted data lives and how the pieces connect, for building, integrating, reporting, and troubleshooting.

Schema Models

Each provider has its own schema model. (See note below on whether to keep these as four pages or group them like the other sections.)

What the Documentation Covers

Across these models, the documentation describes:

• Objects & fields — standard and custom object definitions and key field descriptions

• Relationships — lookup and master-detail relationships, and parent-child dependencies

• ER diagrams — high-level system diagrams and provider-specific models

• Data flows — source-to-target mapping and integration data flows

• Supporting models — OCR/AI result storage, analytics and reporting objects, audit/logging, and platform events

What Each Schema Page Documents

For consistency, each schema page follows the same structure:

• The objects (standard and custom) in this model

• Key fields and their descriptions

• Relationships and dependencies between objects

• An ER diagram of the model

• Source-to-target data flow for the integration

• Where the data is used downstream (analytics, reporting)

Important Note

Treat this as a living reference: update it whenever objects, relationships, integrations, or processing frameworks change. Validate data-model changes against business requirements, integration dependencies, and reporting impacts before deployment.

Intended Audience

Salesforce developers, technical architects, and integration engineers (primary), and administrators, QA, and support teams (reference).