Understand Delivery Note event types
Follow this guide to use the exact lifecycle event names written by the supplied model and controllers. 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 goAdmin Area → Delivery Note → View note → Compliance Log
What you’ll accomplish
Use the exact lifecycle event names written by the supplied model and controllers. This guide follows the supplied Delivery Note module’s live hooks, controller actions, model rules, views and stored side effects.
Follow these steps
- Go to the note.
- Read each event type and message.
- Match `created` to record creation and `updated` to unsigned edits.
- Match `viewed` and `sign_failed` to public access attempts.
- Match `signed` to the sealed status.
- Match `pdf_viewed_from_invoice` to authorised client PDF access.
- Match `void` to withdrawal.
Fields and options to review
- created
- updated
- void
- viewed
- sign_failed
- signed
- pdf_viewed_from_invoice
Rules the system enforces
- Event rows include IP, user agent, metadata JSON, staff actor when available and created time.
- Public access events may not have a staff actor.
- Admin PDF generation and email outcomes are not dedicated event types in the supplied build.
- The event table is removed on uninstall.
How to confirm it worked
- Reviewers use only implemented event meanings and can identify gaps that require external evidence.
Safety checks and troubleshooting
- Do not invent dispatched, email_failed, downloaded or expired events.
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.