Record creation, snapshots and PDF output

Render the verified locked PDF stamp

Regenerate a signed document PDF to include the green evidence stamp. 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: CRM staffPermission: Staff loginModule v2.1.1
Jump to steps
Where to goAdmin Area → Sales → Open signed source document → View or download PDF
Before you start
  • Use an authorised account and confirm the source CRM record or setting is correct.
  • Follow the exact route shown above; do not force database values to imitate a completed action.

What you’ll accomplish

Regenerate a signed document PDF to include the green evidence stamp. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.

Follow these steps

  1. Make sure Verified stamp enabled is Yes.
  2. Complete the public signature.
  3. Regenerate the source PDF.
  4. Verify the green verified locked stamp appears and matches the record.

Fields and options to review

Stamp contentsDocument reference, signer/role, signed date/time, public or masked IP, verification code and valid signature image where available.

Rules the system enforces

  • The stamp is rendered only when the record status is signed and integrity verification passes.
  • Integrity or signature-image errors are logged and prevent misleading evidence output.

How to confirm it worked

  • The requested record, output or setting is created or updated through the supported module flow.
  • Any related status, count, email, audit/event, PDF/file or queue evidence agrees with the source action.
  • An error message is investigated rather than bypassed.

Security, privacy and operational checks

  • Apply least privilege and verify the correct customer, lead, sales document or recipient before processing.
  • Protect public tokens, recipient data, IP/browser evidence, templates and exported files according to organisational policy.
  • Test configuration changes with controlled records before production-wide use.
  • Retain or delete evidence only under an authorised retention process.