Templates and content authoring

Start a fresh template after closing the modal

Use the modal-reset behaviour so a previous edit does not carry into a new template.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Exact navigationAdmin Area → Letter Manager → Templates → close modal → New Template

Before you begin

Use an authorised account and confirm the customer, external recipient, template, letter or configuration is the intended one.
Follow the exact route shown above and verify the stored record, generated file and delivery evidence instead of relying on an alert alone.

What this guide covers

Use the modal-reset behaviour so a previous edit does not carry into a new template. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Exact step-by-step process

Close the template modal after editing or cancelling.
Select New Template again.
Confirm the hidden ID, normal inputs and content editor are empty.
Create the new template and save.

Fields, choices and supported possibilities

Action scopeUse the modal-reset behaviour so a previous edit does not carry into a new template.

Module version1.0.0

Exact routeAdmin Area → Letter Manager → Templates → close modal → New Template

EvidenceVerify the history row, PDF, email metadata, open evidence, signature, public page, client view or postal fields produced by this flow.

Code-backed validations and workflow rules

The hidden.bs.modal handler resets the form, clears the hidden ID and empties the TinyMCE content.

Expected result and verification

The requested letter, template, setting, file or tracking detail is created or updated through the supported route.
The history row, generated PDF, email/send metadata, public verification, signature evidence, client view or postal display agrees with the action.
Any warning, missing file or failed send is investigated rather than bypassed.

Security, privacy and operational checks

Apply least privilege and verify recipient identity before sending or exposing public links.
Protect PDFs, enclosures, signatures, verification URLs, email-open metadata, IP addresses and customer data under organisational policy.
Test configuration and deployment changes with controlled records before production-wide use.
Interpret email opens and e-signatures according to their documented technical limitations.