Understand the signed Delivery Note lock
This guide explains that which actions stop once a valid signature has been stored. 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 signed note
What you’ll accomplish
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.
Follow these steps
- Go to the signed note.
- Check status Signed, signed time, IP, user agent-derived evidence and signature hash.
- Verify the Edit action is absent.
- Verify an attempted direct edit redirects with a locked warning.
- Use the sealed public view or PDF for evidence.
Fields and options to review
- status signed
- signature_data
- ip_address
- user_agent
- signed_at
- signature_hash
Rules the system enforces
- 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.
How to confirm it worked
- The first accepted signature remains the final stored confirmation for that note.
Safety checks 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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.