ENTITY_DEFINITION_STANDARD_OBJECTS

const ENTITY_DEFINITION_STANDARD_OBJECTS: ReadonlySet<string>

Defined in: packages/simply-aep-core/src/entityDefinitionEligibility.ts:37

Standard objects known to satisfy EntityDefinition’s Metadata Relationship eligibility rule, per Salesforce’s Custom Metadata Types Implementation Guide (“Custom Metadata Relationships”): supports custom fields, supports Apex triggers, supports custom layouts, isn’t an activity object (Task/ Event), isn’t User, isn’t a Trialforce object. Salesforce doesn’t publish a single canonical, current list of which standard objects satisfy that rule, and it isn’t fixed across releases, so this is a best-effort baseline, not an authoritative table — extend it as a real binding confirms an object works, or as a consuming rule false-positives on one that does. See docs/design/0014-domain-process-binding-entity-definition-eligibility.md.

Custom objects are never checked against this list — see isCustomObjectApiName — since a custom object always satisfies the rule.

Shared across every MetadataRelationship-to-EntityDefinition field this package validates: DomainProcessBinding__mdt’s RelatedDomainBindingSObject__c (0014), ApplicationFactory_{Selector,Domain}Binding__mdt’s BindingSObject__c (docs/design/0015-at4dx-binding-validate-create-set.md), and SelectorConfig_FieldSetInclusion__mdt’s BindingSObject__c (docs/design/0016-at4dx-selector-config-field-set-inclusion.md).