Proof, publish and versions
Your users only get a template once you publish it. Before that, Sliick Docs checks the template for problems, and you can make a proof to see the real output. This page covers checking, proofing, publishing, and going back to an earlier version.
Checks while you work
Section titled “Checks while you work”Sliick Docs checks your template every time you save, and again when you proof or publish. It makes sure every merge field and theme colour still exists, and that style settings are within range, so you find problems while building rather than when someone generates a document.
The validation area on the right shows one of three states, Valid, Warnings or Errors, with a plain-English explanation of what to fix. A merge field that does not exist counts as an error, so it can never quietly print as a blank.
Preview, Generate proof and Publish are blocked while there are errors. A broken template cannot reach your users.
If the problem is a merge field in the header or footer, the message says where: “Fix the header of this template.” or “Fix the footer of this template.”, followed by the usual explanation.
Two kinds of condition that could never work are refused when you save: a Show if condition that reads a related list outside a repeat over that list, and a repeat filter the document cannot read. See Repeats and conditional content.
Merge fields inside a callout or a list item are checked like any other: the field must exist and you must be able to read it. Built-in fields such as {{Today}}, {{Now}} and {{RunningUser.*}} work inside callouts, list items and repeats.
Symbols the PDF cannot print
Section titled “Symbols the PDF cannot print”Pasted symbols such as ✓, ☑, ☐ and ● are checked too. If a character cannot be printed in a PDF (emoji are the usual example), you get a warning that names the character, rather than a gap on the printed page. Headers and footers are checked the same way.
This is a warning, not an error, because Word documents are not affected. It does not block Preview, Generate proof or Publish. To fix it, replace the character with ordinary text, or make a Word document instead.
Chinese, Japanese and Korean text is fine: it prints in PDFs and wraps onto new lines correctly, with nothing for you to do.

Generate a proof
Section titled “Generate a proof”A proof is a real document made from your draft and your test record, so you can check it before anyone else sees it.
- Save your changes.
- Click Generate proof in the top bar. If the template makes both PDF and Word, you get a proof in each format.
- Open the proof and check it. Proofs are saved to Salesforce Files with the name
<Template Name> - v<Version Number> - Proof - <Record Id>.<ext>. You can also find them in the Generated proofs list in the top bar.

A draft is Ready to publish once it is Valid. You do not have to make a proof before you publish: you can make one at any time, and Sliick Docs makes one for you after every publish.
The proof that follows a publish
Section titled “The proof that follows a publish”Publishing takes effect as soon as you click. Sliick Docs then makes a proof from the newly live version in the background, so you can keep working. It uses:

- the template’s test record, or
- if none is set, the most recently changed record you can read, or
- if there is no record you can read, a layout proof that shows each field’s name instead of its value.
The proof appears on a card in the editor and as a label in the Template Library.
If the proof cannot be made, the template stays live and the card explains why. A Word-file template can still be refused at publish if the document itself needs fixing, for example if its tags do not match any field or, when PDF is ticked, the document cannot become a PDF or its pictures were not stored.
Publish
Section titled “Publish”Publishing locks your draft as a new version and makes it the live version, in one step. A published version never changes, so a document made from it today will look the same if it is made again next year.
- In the top bar, click Publish. For a designed template, the button is available once the draft is Ready. A Word-file template is checked when you click, and if the document needs a fix, Sliick Docs tells you what it is.
- Confirm. Sliick Docs saves the version together with the current theme, and switches your users to it straight away.
- The editor becomes read-only. To make more changes to a designed template, click Create draft, which replaces Publish. A Word-file template works differently: give it a new file with Upload a new version or a save from the Word add-in, or use Re-publish… to change its formats without a new file. See Word-file templates.
While publishing runs, the settings on the right are read-only, so nothing you type there is lost.
Go back to a previous version
Section titled “Go back to a previous version”In the Template Library, click Restore previous version to make the version that was live before this one live again. Sliick Docs asks you to confirm, and names that version.

- Nothing is generated again.
- Restoring again undoes the first restore.
- A version that was replaced and then changed cannot be restored.
Published versions are always read-only. To change a designed template, click New Draft in the Template Library. To change a Word-file template, use Upload a new version or Re-publish… instead. Every past version is kept for audit.