Understand the one-time e-signature lock
Know how repeated visits and repeat posts behave after the first successful signature.
Exact navigationSecure public Delivery Note link → Signed document
What this guide covers
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.
Exact step-by-step process
- Complete one valid signature.
- Reload the public link.
- Confirm the signature form is replaced by signed confirmation details.
- Try no further signing action.
- Use the PDF or sealed page for later review.
Fields, choices and supported possibilities
- Status changes from open to signed
- Signature form renders only when status is not signed
- Model sign method returns false for already signed notes
Code-backed validations and workflow rules
- 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.
Expected result and verification
- The delivery record remains sealed against ordinary module changes.
Checks, security 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.