template-record-preview
Enterprise Part of the commercial Kumiko Enterprise offering — not in the open framework.
Renders a mail or document template with the values of one real record instead of sample values. records lists the records of the entity a notification maps its variables to (record on the notification), preview-record maps one record to the template variables and renders it through template-resolver’s own preview, so the preview and the real send share one render path. Both run as the caller: tenant scope and read access of the entity apply. Requires template-resolver; the editor’s record picker comes from the ./template-preview/web client plugin.
Build it yourself
Section titled “Build it yourself”This Enterprise implementation is optional. If you need a narrower or domain-specific version, you can build an app-owned feature, handler, or job with Kumiko’s public extension points.
Use this package when you want the maintained implementation, its existing contracts, and the surrounding operational behavior. A custom implementation is not drop-in compatible automatically: your app owns its authorization, validation, integrations, tests, security review, and production operations.
Start with Features and composition and Custom write handlers.
How it fits
Section titled “How it fits”What this feature needs to run (Requires).
flowchart TB
n_template_record_preview["template-record-preview"]
subgraph how_reqs["Requires"]
n_template_resolver["template-resolver"]
end
n_template_resolver --> n_template_record_preview
Dependencies
Section titled “Dependencies”- Requires:
template-resolver - Activation: always on (not toggleable)