Understand the Courier model workflow map
Trace validation and side effects to model methods.
Exact navigationTechnical reference → models/Courier_logistic_management_model.php
What this guide covers
Trace validation and side effects to model methods. 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
- Open Technical reference → models/Courier_logistic_management_model.php.
- Review the source record and choose the supported action.
- Save or submit once, then reopen the record and verify the result.
Fields, choices and supported possibilities
Recordssave_driver, save_vehicle, save_customer, save_job, saveStops.
Dispatch/statusassign_job, calculate_driver_pay, change_job_status, addJobHistory.
PODcreate_delivery_note, ensure_delivery_note_for_job, email_delivery_note, sign_delivery_note and submit_delivery_note_to_provider.
Compliancerecalculate_driver_compliance, compliance alerts.
Financesettlements, expenses, reports, provider invoices.
Integrationsproviders, live sync, import_external_job, import_provider_invoices, process_webhook, BP connection/cards/transactions.
Automationrun_automation, send_daily_digest_if_due.
Controlssoft_delete, audit, encrypt/decrypt, redaction and code/slug generation.
Code-backed validations and workflow rules
- Use the supported screen and permission; do not bypass validation or edit database records directly.
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.