Troubleshoot a missing signature image
Check capture, protected file and token evidence in sequence.
Exact navigationAdmin Area → Courier & Logistics → Delivery Notes → Open note
What this guide covers
Check capture, protected file and token evidence in sequence. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects.
Exact step-by-step process
- Confirm the note is signed.
- Confirm a signature path and hash are retained.
- Open the controlled signature route.
- Check deployment storage permissions if the route cannot read the protected capture.
- Do not mark the job complete manually without valid evidence.
Fields, choices and supported possibilities
This action uses the values already stored on the selected source record. Review that record before continuing.
Code-backed validations and workflow rules
- The completion rule requires signed POD and snapshot; evidence paths/hashes must remain intact.
Expected result and verification
- The source record, status/history and any downstream notification, provider, POD or finance record should agree after the action.
Security, audit and operational checks
- Use the exact record and least-privilege role before changing any state.
- Verify the saved record after every action; a browser message alone is not evidence that every downstream step completed.
- Use protected document and image routes rather than exposing server filesystem paths.
- Keep customer, driver, provider, financial and credential data within the authorised workflow.
- For provider, finance, employment, transport and compliance decisions, follow the organisation’s authorised professional process.
Do not bypass the code flowDo not force database values, invent a status, mark a job completed without signed POD evidence, or expose encrypted credentials to make a screen appear successful.