Notification and Communication Records Carry No Custom Fields

Context

Custom-field ownership must remain an explicit product designation rather than arise from template merge data.

Decision

Notification and communication records have no enabling custom-field declaration in the examined scope; source-record custom fields are consumed only as merge values.

Alternatives Considered

Adding record custom fields would require Andrew’s designation beyond the purpose’s existing merge contract.

Consequences

Notification screens use dedicated behavior rather than custom record layouts. Source record fields remain owned by their business module when Communications reads them.