Templates and content authoring

Troubleshoot Letter Manager template loading

Resolve missing options, JSON errors or content-editor population failures.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Exact navigationAdmin Area → Letter Manager → Templates / Dashboard

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

Resolve missing options, JSON errors or content-editor population failures. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Exact step-by-step process

Confirm the templates table exists and contains the expected row.
Open Templates and verify the row is listed.
Use the edit icon and inspect the browser request to templates/get_template/{id}.
Confirm TinyMCE has initialised on content or content_external.
Reload the dashboard and select the template again.

Fields, choices and supported possibilities

Action scopeResolve missing options, JSON errors or content-editor population failures.

Module version1.0.0

Exact routeAdmin Area → Letter Manager → Templates / Dashboard

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 dashboard reads all templates once when the page loads.
Template selector changes populate TinyMCE when available and fall back to the textarea value otherwise.

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.