Understand Delivery Note PDF footer behaviour
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Distinguish the installed footer-text option from the footer actually rendered by the supplied PDF code.
Where to goNo staff-menu setting exists → Review generated Delivery Note PDF footer
What this guide helps you do
Distinguish the installed footer-text option from the footer actually rendered by the supplied PDF code. This guide follows the supplied Delivery Note module’s live hooks, controller actions, model rules, views and stored side effects.
Follow these steps
- Generate a test PDF.
- Read the footer at the bottom of the page.
- Verify it states Powered by Pixie CRM Software Solutions UK Ltd..
- Check the installed `delivery_note_pdf_footer_text` option only as metadata.
- Do not tell users that changing the option will alter the PDF unless the deployed code is later changed and verified.
Fields and options
- Installed option default: one-time e-signature/compliance-log sentence
- Rendered hard-coded footer: Powered by Pixie CRM Software Solutions UK Ltd.
Rules and limits
- The current Delivery_note_pdf library does not read the installed footer-text option.
- The rendered footer is repeated on pages/continuations.
- This is a code-backed limitation, not a configurable UI feature.
Check it worked
- Documentation accurately describes the footer users will actually see.
Safety checks and troubleshooting
- Future code changes should align the option and rendered output before a configuration guide is added.
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
Was this guide useful?Your response is stored only in this browser.