Understand invalid, missing and void public-link errors
Interpret each access-denied branch implemented by the public controller.
Exact navigationSecure public Delivery Note link
What this guide covers
Interpret each access-denied branch implemented by the public controller. 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
- If the page says Invalid Request, check whether the link includes its token.
- If it says Document Not Found, request a fresh exact link from authorised staff and verify the note exists.
- If it says Document Voided, contact the sender for the replacement note.
- Do not retry by altering token characters.
Fields, choices and supported possibilities
- Missing/blank token → Invalid Request
- Unknown token → Document Not Found
- Known note with status void → Document Voided
- Valid open/signed token → public document
Code-backed validations and workflow rules
- The controller does not disclose another record when the token is wrong.
- Void status is checked before rendering or signing.
- A signed link remains viewable in sealed mode.
- There is no token-expired message because expiry is not implemented.
Expected result and verification
- Users receive a safe, specific outcome without revealing unrelated delivery data.
Checks, security and troubleshooting
- Support should verify the note from the admin register rather than ask the recipient to share the full token publicly.
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.