Skip to content

Word output

Sliick Docs generates either a PDF or a Microsoft Word .docx from the same template: one source of truth, two output paths. Word files are generated natively on the platform, so no external service is involved. The data inside the document is identical between formats; only the output file type differs.

Two flags on the Template record control which formats end users see.

FieldDefaultEffect
Allow PDF OutputtrueThe record-page button renders Generate PDF. PDF batches and Flow runs are accepted.
Allow Word OutputfalseThe record-page button renders Generate Word. Word batches and Flow runs are accepted.

At least one format must be enabled: a validation rule rejects the both-off state. Enable both to give end users a split button at runtime.

Use casePick
Final-form document going out as-is (statements, invoices, receipts)PDF
Editable draft the recipient will redline (contracts, offer letters)Word
Document that needs further customisation per recipientWord
Compliance-locked output that must not be modifiablePDF
  • The record-page Sliick Docs Generator, as a split button when both formats are enabled.
  • All three Flow actions, through the optional output format input.
  • The Doc Batches console and the bulk Flow action, in Individual output mode only.
  • Single-record bundle generation. The combined .docx has one Word section per member, each with its own header, footer, image watermark, page setup and theme, and page numbers restart for each member.
  • The list-view mass action.
  • Dual-format proof during authoring.
  • Combined and Both batch modes are PDF-only. Use Individual mode for Word batches.
  • Text watermarks are PDF-only. Word output leaves a text watermark out, and the template saves normally with both. Image watermarks are carried into Word.
  • Barcodes are PDF-only. A template with a barcode block cannot turn on Word output. Authors typically split into separate templates, one for the editable-Word workflow and one for the barcoded PDF.
  • A template first published on an early version may need a one-time re-publish to enable Word output.

A Word file reads the theme frozen when the template was published, the same one its PDF was compiled from. That holds for a single template and for each member of a bundle. So if your organisation rebrands after publishing, Word files keep the publish-time branding, matching their PDFs, until the template is republished.

Upgrading from 2.12 or earlier: Word output used to read the live org theme, and a bundle’s Word file used the org default for every member. After the upgrade, Word files from a template published before a rebrand go back to its publish-time branding. Republish the template to pick up the current theme.

The per-template File name pattern does not need an extension token: the extension swaps automatically based on which format was generated.

  • Pattern {{Account.Name}} - Quote.pdf, generated as Word, becomes Acme Corp - Quote.docx.
  • Pattern {{Account.Name}} - Quote.docx, generated as PDF, becomes Acme Corp - Quote.pdf.

See File names. Salesforce previews Word files natively, so generated .docx files render inline in the Files viewer alongside PDFs.

Note: a template can also be authored as a Word file you upload, which is a different thing from generating Word output. See Word-file templates.