Understand the signed Delivery Note lock
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
This guide explains that which actions stop once a valid signature has been stored.
Where to goAdmin Area → Delivery Note → Open signed note
What this guide helps you do
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
- status signed
- signature_data
- ip_address
- user_agent
- signed_at
- signature_hash
Rules and limits
- 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.
Check 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.
Related guides
Was this guide useful?Your response is stored only in this browser.