Template editor and validation

Complete e-Invoice template fields

Enter the three values used by validate_and_save.

Audience: CRM staffPermission: AdministratorModule v1.0.0
Exact navigationAdmin Area → Setup → Settings → Finance → e-Invoice → New/Edit Template
Before you begin
  • 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 this guide covers

Enter the three values used by validate_and_save. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.

Exact step-by-step process

  1. Enter Name.
  2. Choose Content Type XML or JSON.
  3. Enter Content.
  4. Validate and save.

Fields, choices and supported possibilities

NameStored as the template name.
Content TypeXML or JSON; JSON is special-cased, all other values follow XML validation/output defaults.
ContentRequired Mustache template; blank content is rejected.

Code-backed validations and workflow rules

  • Only values and transitions exposed by the supplied module code are supported.
  • Server-side validation remains authoritative even when browser controls appear to accept a value.

Expected result and verification

  • 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.