---
id: ADR-PFM-INT-013
title: No integration-area record carries custom fields
product_area: platform
module: integrations
revision: 1
status: proposed
design_intent: confirmed
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
decision: >-
  Keep these objects outside custom-field, configurable-form and configurable-layout support. Registered
  workflow configuration objects do not enable metadata capabilities.
constrains:
  - DOM-PFM-INT-001
  - DOM-PFM-INT-002
  - DOM-PFM-INT-003
  - DOM-PFM-INT-004
  - DOM-PFM-INT-005
  - DOM-PFM-INT-006
  - SVC-PFM-INT-integrations
  - SVC-PFM-INT-extensions
  - SVC-PFM-INT-workflow-actions
alternatives:
  - option: Enable custom fields on integration configuration.
    why_not: The approved classification does not designate a Platform object for this support.
consequences:
  - Purpose-built screens use existing shared UI components.
  - Any new custom-field designation requires an explicit product decision.
origin: 'docs/standards/custom-field-capability.md §2 (R2-ARCH-001, Andrew 2026-10-19)'
supersedes: []
evidence:
  - >-
    services-platform at ad3f6a65: docs/standards/custom-field-capability.md; docs/metadata.md (Capabilities);
    modules/workflow-actions/workflow-actions-objects.ts
---

# No integration-area record carries custom fields

## Context

Metadata registration alone does not imply custom-field support.

## Decision

Keep these objects outside custom-field, configurable-form and configurable-layout support. Registered workflow configuration objects do not enable metadata capabilities.

## Alternatives Considered

Enable custom fields on integration configuration. The approved classification does not designate a Platform object for this support.

## Consequences

Purpose-built screens use existing shared UI components.

Any new custom-field designation requires an explicit product decision.