Operator guideENemailtemplatesform

Email Templates / Form

Create and edit workflow for one email template, including per-language subject and HTML body, dynamic variables, translation helpers, and test-send.

Reader view

Clean portal guidance

This page keeps the operator explanation, field and action descriptions, and screenshots visible without exposing repo paths, raw sidecars, or editorial-only implementation details.

Narrative content

Page body

What this form does

This surface is used to create a new email template or edit an existing one.

Operators use it to maintain:

  • the internal template label
  • subject text per language
  • HTML body per language
  • template type and its available variables
  • test delivery before trusting a change

Create vs edit

Create

The create flow defines the template label, type, subject, and HTML body. It can also receive a notificationId from the route query when the template is being linked from a notification workflow.

Edit

The edit flow first loads the stored template from the backend, then lets the operator:

  • change subject per language
  • change HTML body per language
  • insert AI or translated content
  • send a backend test email
  • save the updated template

How preview works

The page editor renders the current HTML body with dynamic-value substitution in the frontend. This helps operators review layout and placeholders, but it is still not the same thing as a delivered message.

Important actions

  • Save
  • Send test email
  • Translate
  • Cancel

Known caveats

  • Send test email exists only on the edit flow because it depends on the stored template context.
  • Translation helpers are FE-driven utilities layered on top of the saved template workflow. They are not the primary backend save action.
  • notificationId and notificationActive can be linked through the same email-template save/update route, so email and notification semantics meet on one record.
Field dictionary

Fields

field

Template Label

Internal template name used to identify the template family in CRM.

Data Type
string
field

Language Tab

Selects which locale version of subject and HTML body the operator is editing.

Data Type
enum
field

Subject

Outgoing email subject for the currently selected language.

Data Type
string
field

Template Type

Backend email type that determines variable availability and downstream delivery meaning.

Data Type
integer-enum
field

Template Body

HTML body that is stored and later rendered for delivery.

Data Type
html
field

Available Variables

Placeholder variables the operator can safely use for the selected template type.

Data Type
key-list
field

Notification Link

Optional linked notification identifier used when email and notification behaviors are tied together.

Data Type
integer
Operational notes

Notes

item

The edit form is the authoritative place for backend-backed test-send through `test-email-template`.

item

Form preview is FE-only and uses the current editor value plus settings substitutions.

item

`update-email-template` handles both full content saves and lightweight toggles such as `isActive`, `notificationActive`, and `notificationId`.

Related references

Related pages

pageEmail Templates

Operator workspace for email-template inventory, subject and body maintenance, test-send checks, and notification linkage.

pageEmail Templates / List

Grouped template inventory with untranslated-template context, CSV export, HTML preview, activation toggle, and edit navigation.

pageAffiliate Deals / Form

Create and edit form for affiliate deals, including PID, date window, commercial terms, and responsible person.

pageAffiliate Payment Settings / Form

Create and edit form for one affiliate payment-setting record, with visible PID targeting, minimum deposit threshold, and active-state control.

pageAuto Tags Manager / Create

Full rule-builder for a new automatic tagging rule, including tag actions, coupon actions, KPI field selection, and draft impact estimation.

pageAutomatic Withdrawal / Form

Create and edit form for one automatic-withdrawal rule, including thresholds, KYC, countries, methods, tags, and per-currency limits.