Understand open, signed and void statuses
Apply the complete status model implemented by the module.
Exact navigationAdmin Area → Delivery Note → Open note → Status
What this guide covers
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.
Exact step-by-step process
- 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, choices and supported possibilities
- open: default at creation
- signed: set after valid one-time signature
- void: set by the permission-protected void action
Code-backed validations and workflow rules
- 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.
Expected result and verification
- Staff interpret each record consistently and do not invent unsupported transitions.
Checks, security 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.