Problem/Motivation
When building emails, there is often configurable data
- required field, for example user emails require configuring body and subject; contact form emails require configuring to address
- optional extra fields can be configured on any email: addresses, other headers, user language, theme, mailer transport, plain text alternative, etc
In the old mailsystem, each module created its own config form with underlying configuration data. Typically only a few select fields were available. We can improve on that with a single shared mechanism available for use by any module for configurable emails.
Proposed resolution
@EmailAdjusterplug-in for each field that can be configuredMailerPolicyconfig entity carrying the set of configured fields, indexed by email ID- GUI for editing policy: page listing of all policy leading to policy add/edit forms
- Embedding policy editing: when editing the settings of a module or of a config entity, a GUI appears for editing the related policy
Comments