Understand the signed Delivery Note lock
Know which actions stop once a valid signature has been stored.
Exact navigationAdmin Area → Delivery Note → Open signed note
What this guide covers
Know which actions stop once a valid signature has been stored. 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 signed note.
- Verify status Signed, signed time, IP, user agent-derived evidence and signature hash.
- Confirm the Edit action is absent.
- Confirm an attempted direct edit redirects with a locked warning.
- Use the sealed public view or PDF for evidence.
Fields, choices and supported possibilities
- status signed
- signature_data
- ip_address
- user_agent
- signed_at
- signature_hash
Code-backed validations and workflow rules
- Both the controller and model protect against editing a signed note.
- The void model also refuses a signed record.
- A repeated public signing request returns to the sealed view rather than replacing the signature.
- The supplied code does not implement an unlock or countersign action.
Expected result and verification
- The first accepted signature remains the final stored confirmation for that note.
Checks, security and troubleshooting
- Correction after signing requires an authorised business process outside the module’s unsupported unlock path.
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.