============================================================================ SCOPE RESOLUTION SEAM

An EntityAction may be narrowed to ONE configuration record — this Deal Type, this Contract Type, this Pipeline, this Company — via the ScopeEntityID / ScopeRecordID pair. NULL means "applies to every record of the entity", which is the pre-existing behaviour and by far the common case.

The framework stores and filters on the pair; it does not interpret it. How a scope record relates to a subject record is an application concern: Sales knows a Deal reaches its Deal Type through Deal.DealTypeID, and core must not. So the question "does this subject record fall under this scope record?" is answered by a @RegisterClass-resolved resolver, keyed by scope entity name, most-specific wins — the same shape as BasePriceResolver in BizApps Orders and GLAccountResolver in Accounting.

The default implementation below walks the subject entity's foreign keys looking for one that points at the scope entity. That covers the direct case (Sales registers nothing for Deal Types because Deal.DealTypeID is found automatically). An app needing something indirect — scope by Company where the subject reaches Company through a Pipeline — registers its own resolver:

@RegisterClass(EntityActionScopeResolver, 'Companies')
export class CompanyScopeResolver extends EntityActionScopeResolver {
    public override async IsInScope(subject: BaseEntity, scopeEntityID: string, scopeRecordID: string): Promise<boolean | null> {
        // return null to decline and fall back to the default FK walk
    }
}
Copy

Declining returns null, not false. false means "I looked and this record is out of scope"; null means "not my call" and falls back to the default. Conflating them would silently disable every binding a partially applicable resolver didn't recognise.