Understand generated record codes and slugs
Use system-generated references without manually duplicating them.
Exact navigationAdmin Area → Courier & Logistics → Relevant create form
What this guide covers
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.
Exact step-by-step process
- Create the record using the supported form.
- Save once.
- Record the generated code or unique slug shown by the module.
- Use that reference in searches, reconciliation and support.
Fields, choices and supported possibilities
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.
Code-backed validations and workflow rules
- Codes are generated against the destination table.
- Provider slugs remain unique even when names are similar.
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.