Word-file templates

A template’s Source Type decides where its content is authored: in the Sliick Docs editor, or in a Word file you upload. An uploaded Word template carries its own text tags, and Sliick Docs merges them and produces the PDF or Word file at generation time. Use this when the document already exists in Word and legal or brand ownership of it sits outside Salesforce.

What you can write in the file

• Merge fields and conditions. Write merge fields as tags in the document, and wrap optional content in {{#if}} blocks. Nested {{#if}} blocks are supported, so an optional clause can sit inside another optional clause. A file whose tags do not close properly is refused when you upload it, naming the tag, where it is, and how to fix it, rather than being accepted and merging into a broken document later.
• Whole numbers. {{Qty:integer}} renders 120 rather than 120.00, exactly as the Whole number format does in a designed template. See Merge field formats.
• Barcodes. Barcode tags render as real barcodes in the generated PDF and are sized to the document’s own page width. Add :nohri to a barcode tag to turn off the line of readable text that otherwise prints beneath the symbol. A barcode that cannot fit prints its value as readable text instead, with the reason recorded on the template’s info card when you proof it and in the generation history when you run it, so a document is never delivered with a raw tag or an unscannable symbol in it.
• Signature tags. Write {{@Signature:Role:Order:Type}} where a signature belongs and Sliick Docs places the field and builds the signer list from it when the document is sent for signature. See Signature tags.
• Chinese, Japanese and Korean text renders in the generated document, including text that Word producers write as character references rather than as the characters themselves.

New versions start from Word

The content of an uploaded template lives in the Word file, so a new version begins there: upload a new .docx, or attach one from the Word add-in. There is no Create draft action on these templates, because an empty draft with no Word file attached could never be published.

Source Type is fixed once a template is published. So is its base object. A save that would change either is refused with an explanation, because every release already published was compiled against them.