Understand Delivery Note route options and safety fallbacks | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/understand-delivery-note-route-options-and-safety-fallbacks Publisher: Pixie Technologies LLC Technical configuration, lifecycle and troubleshooting 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. Audience: System administrators and developers; Permission: Technical configuration access; Module v1.0.0; Where to goNo staff-menu screen exists → Authorised deployment/configuration review 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 - Check the default admin, public-view and public-sign option values. - Use the helper-generated admin and public URLs in module code. - Verify configured public route values do not use legacy/hyphen forms rejected by the helper or contain `admin/`. - Test generated links after any approved change. - 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. 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. Related guides Run the Delivery Note post-install functional test (https://pixiecrm.com/help-centre/run-the-delivery-note-post-install-functional-test)Understand the Delivery Note database tables (https://pixiecrm.com/help-centre/understand-the-delivery-note-database-tables)Troubleshoot a missing Delivery Note menu or invoice buttons (https://pixiecrm.com/help-centre/troubleshoot-a-missing-delivery-note-menu-or-invoice-buttons)Browse all Delivery Note guides (https://pixiecrm.com/help-centre/category/delivery-note)