Understand external-letter field validation
Know which fields the supplied UI and controller actually require.
Exact navigationAdmin Area → Letter Manager → Dashboard → Manual Entry (External)
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
Know which fields the supplied UI and controller actually require. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.
Exact step-by-step process
- Treat recipient identity, address and email as operationally required when relevant even though labelled optional.
- Always enter Subject.
- Enter meaningful PDF content.
- Test the output before formal issue.
Fields, choices and supported possibilities
Action scopeKnow which fields the supplied UI and controller actually require.
Module version1.0.0
Exact routeAdmin Area → Letter Manager → Dashboard → Manual Entry (External)
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
- Only Subject has an HTML required attribute in the external form.
- Name, company, address, phone and email are optional in the view.
- The controller does not add server-side required validation for those fields.
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.
Important code-backed limitationA technically accepted record can still be operationally unusable. Apply organisational completeness checks before dispatch.