Understand editable fields and form defaults
Know which values can be changed and which values remain system-controlled.
Exact navigationAdmin Area → Delivery Note → View note → Edit
What this guide covers
Know which values can be changed and which values remain system-controlled. 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
- Open an unsigned note.
- Review the editable delivery fields.
- Leave system identifiers unchanged because they are not exposed in the form.
- Save required changes and verify the detail page.
Fields, choices and supported possibilities
- Editable: delivery_date, delivery_method, delivered_by, tracking_reference, recipient_name, recipient_email, delivery_address, notes
- System-controlled: ID, invoice ID, client ID, reference, secure token, status, snapshots, signature evidence, created/updated metadata
Code-backed validations and workflow rules
- On create, Delivery Date defaults to today and Address defaults from client billing data.
- On edit, the stored values populate the form.
- The supplied form does not change invoice items, prices, client record or token.
Expected result and verification
- Only delivery-operational fields change; identifiers and retained evidence remain stable.
Checks, security and troubleshooting
- Do not use direct database edits to change system-controlled fields.
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.