Module setup, access and navigation

Understand generated record codes and slugs

Follow this guide to use system-generated references without manually duplicating them. 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.

Audience: Courier operations staffPermission: Courier: CreateModule v2.0.0
Jump to steps
Where to goAdmin Area → Courier & Logistics → Relevant create form

What you’ll accomplish

Use system-generated references without manually duplicating them. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects.

Follow these steps

  1. Create the record using the supported form.
  2. Save once.
  3. Record the generated code or unique slug shown by the module.
  4. Use that reference in searches, reconciliation and support.

Fields and options to review

Driver codeGenerated with the DRV prefix.
Other entity codesGenerated from the prefix configured in the model save path.
Provider slugDerived from the provider name and made unique.

Rules the system enforces

  • Codes are generated against the destination table.
  • Provider slugs remain unique even when names are similar.

How to confirm it worked

  • 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.