Understand open, signed and void statuses
Apply the complete status model implemented by the module. 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 → Open note → Status
What you’ll accomplish
Apply the complete status model implemented by the module. This guide follows the supplied Delivery Note module’s live hooks, controller actions, model rules, views and stored side effects.
Follow these steps
- Treat Open as awaiting or available for recipient signing.
- Treat Signed as cryptographically sealed and read-only.
- Treat Void as withdrawn and publicly inaccessible.
- Use event history to confirm how the status was reached.
Fields and options to review
- open: default at creation
- signed: set after valid one-time signature
- void: set by the permission-protected void action
Rules the system enforces
- The module does not implement draft, sent, delivered, rejected, expired or revoked statuses.
- Signed blocks edit and void.
- Void is excluded from active invoice lookup and public access.
- A direct admin edit route blocks only signed, so a void note can technically display the edit form in the supplied code.
How to confirm it worked
- Staff interpret each record consistently and do not invent unsupported transitions.
Safety checks and troubleshooting
- Operational policy should normally avoid editing void records even though the supplied controller does not block that direct route.
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.