Business Entities in this Connected System

Each Business Entity models one governed business resource from a Connected System — customers, contracts, documents, or executable capabilities — listed in the system workspace and configured in the Business Entities band.

Why it matters

Enterprise Knowledge is built per Business Entity. This page covers listing and high-level structure only; field mappings, sync, and policies are configured per entity.

Prerequisites

Connected System JSON with authentication configured
Entity basics, types, and resource type

Where it lives

integration/<systemKey>/
  <datasourceKey>.json    # one file per Business Entity
  application.yaml        # lists every datasource file

Manifest section: system.businessEntities (list in UI; files on disk).

Builder MCP


Manifest section	`system.businessEntities`
UI tab	Business Entities (`?tab=datasources`)
Help topics	`connectedSystemUi`, `section`
Repair hooks	datasource file list in `application.yaml`

Per-entity modeling: open the Business Entity in dataplane or edit <datasourceKey>.json — see Business Entities band.

How to set

Copy a known-good fixture for your entityType — record storage or document storage.
Set root identity — align systemKey with the system file and list the file in application.yaml.
Configure vocabulary and policies in the Business Entities band.
Repair manifest drift:

aifabrix repair <systemKey> --dry-run
aifabrix repair <systemKey> --expose --rbac

Validate:

aifabrix datasource validate <datasourceKey>
aifabrix validate <systemKey>