Templates and content authoring

Edit a Letter Manager template

Load the stored template by AJAX, change its fields and update the same record. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Jump to steps

Where to goAdmin Area → Letter Manager → Templates → Edit icon

Before you start

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 you’ll accomplish

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.

Follow these steps

Go to 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 and options to review

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.

Rules the system enforces

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

How to confirm it worked

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.

Was this guide useful?Your response is stored only in this browser.