Technical configuration, lifecycle and troubleshooting

Run the Delivery Note post-install functional test

Verify every live branch without changing unrelated CRM code. 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: Administrators and implementation testersPermission: Administrator plus Delivery Note capabilitiesModule v1.0.0
Jump to steps
Where to goAdmin Area → Setup → Modules, then Invoices and Delivery Note

What you’ll accomplish

Verify every live branch without changing unrelated CRM code. This guide follows the supplied Delivery Note module’s live hooks, controller actions, model rules, views and stored side effects.

Follow these steps

  1. Activate the module and confirm both tables/options.
  2. Create a test invoice without Add Delivery Note and confirm no note.
  3. Create a second invoice with Add Delivery Note and confirm one open note.
  4. Go to the secure link and submit an empty signature to confirm validation.
  5. Submit a valid signature and confirm lock, events and confirmation email.
  6. Generate admin PDF and test QR/secure link.
  7. Go to the client invoice PDF in the authorised customer context.
  8. Test edit on an open note and confirm signed edit/void protection.
  9. Void a separate open test note through an authorised action and create its replacement.

Fields and options to review

  • Module menu and permissions
  • Invoice optional branches
  • Public view/sign
  • PDF/QR
  • Emails
  • Events
  • Client PDF access
  • Status protections

Rules the system enforces

  • Use controlled test customers and addresses.
  • Do not sign or void production evidence during testing.
  • The module has no cron/API/webhook tests because those features are not implemented.

How to confirm it worked

  • The installed module’s complete supported user flow passes end to end with attributable evidence.

Safety checks and troubleshooting

  • Record test references and remove or retain them according to the organisation’s test-data policy.
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.