Templates and content authoring

Edit a Letter Manager template

Load the stored template by AJAX, change its fields and update the same record.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Exact navigationAdmin Area → Letter Manager → Templates → Edit icon

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

Load the stored template by AJAX, change its fields and update the same record. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Exact step-by-step process

Open Templates.
Select the pencil icon beside the required template.
Wait for the modal to load the template ID, name, subject and content.
Make the approved changes.
Select Save and retest the template in the dashboard selector.

Fields, choices and supported possibilities

Action scopeLoad the stored template by AJAX, change its fields and update the same record.

Module version1.0.0

Exact routeAdmin Area → Letter Manager → Templates → Edit icon

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

get_template returns the selected row as JSON.
The hidden ID causes save() to update rather than insert.

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.