Understand the one-time e-signature lock
This guide explains that how repeated visits and repeat posts behave after the first successful signature. 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 goSecure public Delivery Note link → Signed document
What you’ll accomplish
Know how repeated visits and repeat posts behave after the first successful signature. This guide follows the supplied Delivery Note module’s live hooks, controller actions, model rules, views and stored side effects.
Follow these steps
- Complete one valid signature.
- Reload the public link.
- Verify the signature form is replaced by signed confirmation details.
- Try no further signing action.
- Use the PDF or sealed page for later review.
Fields and options to review
- Status changes from open to signed
- Signature form renders only when status is not signed
- Model sign method returns false for already signed notes
Rules the system enforces
- The first stored signature is retained.
- The supplied code has no re-sign, unlock, countersign or signature replacement feature.
- Admin edit and void are also blocked for signed status.
How to confirm it worked
- The delivery record remains sealed against ordinary module changes.
Safety checks and troubleshooting
- Any dispute or correction after signing must follow the organisation’s external authorised process.
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.