Check Letter Manager strict-SQL compatibility
Test record creation where the installed history schema has non-null audit columns without defaults. 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.
Where to goControlled staging environment → Letter Manager → Dashboard → send a test letter
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
Test record creation where the installed history schema has non-null audit columns without defaults. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.
Follow these steps
- Activate the module in a staging copy using the same SQL mode as production.
- Create one client letter and one external letter.
- Verify both history rows are inserted and PDF generation completes.
- If insertion fails on a non-null audit column, correct the module schema or insert payload through an approved release rather than disabling database safeguards.
Fields and options to review
Action scopeTest record creation where the installed history schema has non-null audit columns without defaults.
Module version1.0.0
Exact routeControlled staging environment → Letter Manager → Dashboard → send a test letter
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
- The base CREATE TABLE declares added_from as NOT NULL.
- The supplied send payloads do not explicitly set added_from.
- Behaviour may depend on the existing schema and database SQL mode.
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.
Important code-backed limitationDo not weaken production SQL mode merely to mask a schema/payload mismatch. Use a tested module correction if the controlled test fails.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.