Security, privacy, limitations and troubleshooting

Troubleshoot Letter Manager database errors

Resolve missing table, column or index issues through the module’s portable installer path.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Exact navigationAdmin Area → Setup → Modules → Letter Manager; authorised database diagnostics

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 table, column or index issues through the module’s portable installer path. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Exact step-by-step process

Capture the exact table/column error.
Confirm the active files match v1.0.0.
Run activation/schema upgrade in a controlled environment.
Verify guarded columns and tables.
Retest create, send, verify, sign and read tracking.

Fields, choices and supported possibilities

Action scopeResolve missing table, column or index issues through the module’s portable installer path.

Module version1.0.0

Exact routeAdmin Area → Setup → Modules → Letter Manager; authorised database diagnostics

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

Both install.php and runtime helpers can add selected fields.
Do not repeatedly execute unreviewed ALTER statements directly in production.

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.