Understand Delivery Note event types
Use the exact lifecycle event names written by the supplied model and controllers.
Exact navigationAdmin Area → Delivery Note → View note → Compliance Log
What this guide covers
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.
Exact step-by-step process
- Open 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, choices and supported possibilities
- created
- updated
- void
- viewed
- sign_failed
- signed
- pdf_viewed_from_invoice
Code-backed validations and workflow rules
- 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.
Expected result and verification
- Reviewers use only implemented event meanings and can identify gaps that require external evidence.
Checks, security 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.