Understand editable fields and form defaults
This guide explains that which values can be changed and which values remain system-controlled. 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.
Where to goAdmin Area → Delivery Note → View note → Edit
What you’ll accomplish
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.
Follow these steps
- Go to an unsigned note.
- Check 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 and options to review
- 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
Rules the system enforces
- 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.
How to confirm it worked
- Only delivery-operational fields change; identifiers and retained evidence remain stable.
Safety checks 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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.