Customer work, connected.

Help & supportMyAccount
Module setup, access and architecture

Verify the Delivery Note database installation

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

Confirm the two module tables, indexes and installed options required by the code.

Audience: System administratorsPermission: Database access outside the CRMModule v1.0.0
Jump to steps
Where to goServer database administration → Pixie CRM database → Inspect module-owned tables

What this guide helps you do

Confirm the two module tables, indexes and installed options required by the 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. Verify the prefixed `delivery_notes` table exists.
  2. Verify the prefixed `delivery_note_events` table exists.
  3. Check unique indexes on `reference` and `secure_token`.
  4. Check invoice, client and status indexes.
  5. Check the installed Delivery Note options before functional testing.

Fields and options

  • Delivery notes table stores invoice/client IDs, reference, token, statuses, snapshots, delivery details and signing evidence.
  • Events table stores event type/message, IP, user agent, JSON metadata, actor and time.
  • Options include enabled, reference prefix, routes, route mode, schema version, invoice UI flag and PDF footer text.

Rules and limits

  • Table names use the CRM database prefix.
  • The installer is idempotent for existing tables/options.
  • `signed_by_name`, `signed_by_email` and `locked_at` exist in the schema but are not populated by the supplied signing flow.

Check it worked

  • Activation has produced the complete portable schema expected by the controllers and model.

Safety checks and troubleshooting

  • Do not document or use migration scaffolding as a user workflow; this module installs through `install.php`.
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.

Search the platform, integrations and practical Help Centre guides.

Press Esc to close.Browse every page