Rhythm 2.0 Specifications

Appearance

ADR-CRM-REG-007Regions and the Policy Carry No Custom Fields

Markdown

ADR-CRM-REG-007

Regions and the Policy Carry No Custom Fields

Markdown
  • DocumentProposed

KindDecision recordProduct areaCRMModuleRegionsRevision2

Read atservices-crm a8d1364freact-console baf6dae3

Regions and the Policy Carry No Custom Fields ​

Context ​

Older regional definitions carried custom values. The recorded custom-field architecture choice excludes that regional extension.

Decision ​

The regional registration does not declare custom-field capability, and regional request validation accepts the definition’s own fields. The recorded regional customization gap is closed rather than awaiting implementation.

Alternatives Considered ​

Carry older regional custom values into the new definition. The recorded opt-in decision limits CRM custom fields to contacts and organizations, and geographic matching has no use for those regional values.

Consequences ​

Metadata exposes the regional definition’s declared fields without a custom-field contract. A carry-through comment in the console refers to historical custom-field support and does not establish current capability.

Decision
Regional definitions, policy, rules and runs do not opt into custom fields; CRM custom-field ownership remains with contacts and organizations.

The Markdown files under specs/ in rhythmsoftware/rhythm-v2-docs are the canonical source of truth. This reader is a generated, read-only projection of them.

Rhythm Software