Understand the dispatch-email automation
Know when the module sends the initial recipient message and what it contains.
Exact navigationAutomatic after supported Delivery Note creation
What this guide covers
Know when the module sends the initial recipient message and what it contains. This guide follows the supplied Delivery Note module’s live hooks, controller actions, model rules, views and stored side effects.
Exact step-by-step process
- Create the note with Recipient Email populated.
- Verify the note saved and status is Open.
- Check the recipient mailbox for the subject Action Required: Delivery Note {reference}.
- Open the View & Sign Delivery Note button and verify the correct note.
- If absent, troubleshoot global email configuration.
Fields, choices and supported possibilities
- Recipient Email
- Recipient Name used in greeting when present
- Generated public link
- Company name and sender from global CRM email options
Code-backed validations and workflow rules
- Creation attempts the dispatch email only when an email address is stored.
- The email contains a secure bearer link and no attachment.
- The module uses global SMTP when configured, otherwise its fallback mail initialisation.
- The supplied code has no dispatch-email resend button or email-success event.
Expected result and verification
- The intended recipient receives a branded call to review and sign the open note.
Checks, security and troubleshooting
- Confirm the recipient before saving; editing the email later does not automatically resend.
Stay within the supported flowDo not force database values, expose secure tokens, bypass permission checks, replace a stored signature or invent a status or interface that the supplied code does not implement.
