What this form does
This form is used to create or edit one notification template.
Operators use it to maintain:
- the internal notification title
- localized notification content
- sender display name and avatar
- notification priority
- notification-email merge variables shown to operators as a helper reference
- the email-template link that gives the notification an HTML shell
Create vs edit
Entry paths
Notificationslist starts a new notification template without a preselected linked email template.Email Templates -> Notificationscan start the same create flow from an existing email-template row that is not yet linked to a notification.
Create
The create flow can start with or without an existing linked email-template ID.
If no linked email-template ID is present, the system first prepares a minimal email-template shell, then creates the notification template, and finally links the two records together.
Edit
The edit flow loads and saves the notification template by Notification ID.
The operator stays focused on localized notification HTML content. The linked email-template HTML shell stays outside this surface and is still previewed from the list page.
Visible helper surfaces
Language Tabswitches the locale shown in the content editor.Translatefills only missing non-English locales from the current EN body.Force Translateoverwrites every non-English locale from the current EN body.Available Variablesshows the merge keys that are safe to use in notification content.Sender Avatar Sourceswitches between direct URL mode and asset-library mode.
Important actions
Create & Continueon createSaveon editTranslateForce TranslateCancel
Known caveats
- The operator form does not currently expose a send-now or preview-send action.
- The form does not render a standalone preview card. HTML preview still lives on the list page through the linked email-template row.
- Create can use a multi-step linkage flow: prepare the email shell when needed, create the notification template, then link the shell back to the notification.
- The current interface has no visible
Notification Typeselector. Operators should treat this form as template-notification management. - The current interface requires English content before translation, but a missing title can still fail during save.
- Edit starts in
URLavatar mode by default. Existing image URLs are loaded, but they are not automatically resolved back into the asset picker. - The visible priority slider shows labels up to
Max, but the current selectable range is effectivelyRegularorImportant.