Understand the dispatch-email automation
This guide explains that when the module sends the initial recipient message and what it contains. 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 goAutomatic after supported Delivery Note creation
What you’ll accomplish
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.
Follow these steps
- Create the note with Recipient Email populated.
- Check the note saved and status is Open.
- Check the recipient mailbox for the subject Action Required: Delivery Note {reference}.
- Go to the View & Sign Delivery Note button and verify the correct note.
- If absent, troubleshoot global email configuration.
Fields and options to review
- Recipient Email
- Recipient Name used in greeting when present
- Generated public link
- Company name and sender from global CRM email options
Rules the system enforces
- 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.
How to confirm it worked
- The intended recipient receives a branded call to review and sign the open note.
Safety checks and troubleshooting
- Verify 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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.