Understand Delivery Note route options and safety fallbacks

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

Interpret the installed route options and helper validation without presenting a nonexistent settings screen.

What this guide helps you do

Interpret the installed route options and helper validation without presenting a nonexistent settings screen. This guide follows the supplied Delivery Note module’s live hooks, controller actions, model rules, views and stored side effects.

Follow these steps

1. Check the default admin, public-view and public-sign option values.
2. Use the helper-generated admin and public URLs in module code.
3. Verify configured public route values do not use legacy/hyphen forms rejected by the helper or contain `admin/`.
4. Test generated links after any approved change.
5. Restore defaults when validation falls back unexpectedly.

Fields and options

• delivery_note_admin_route
• delivery_note_public_view_route
• delivery_note_public_sign_route
• delivery_note_route_mode

Rules and limits

• The helper normalises slashes and rejects unsafe public route values.
• Default public view/sign values are `delivery_note/public_view` and `delivery_note/public_sign`.
• Routes.php contains compatibility aliases, but current generated links use the supported controller/query-token pattern.
• There is no user-facing route settings form.

Check it worked

• All admin and recipient links resolve through approved module routes without creating an admin exposure.

Safety checks and troubleshooting

• Do not change core routes or `.htaccess` to compensate for an invalid module option.

Related guides