3.2.0

Released 12 October 2026.

Before you upgrade

Output formats

• Output formats now belong to each version, not the template. Allow PDF output, Allow Word output and Lock output format can no longer be changed. Nothing changes on upgrade: a version published before 3.2 keeps making what those switches said. To change formats, publish a new draft.
• Word batches: a Word batch for a template published before 3.2 with Word turned off is now refused when you submit it, instead of failing record by record.

Word files

• Every value from Salesforce is now locked in Word files, including from existing templates. Readers can still edit the wording around a value, but not the value itself. To turn this off, set the template to Editable.

Conditions in a repeat

• Repeat conditions without the list name now work. If a designed template’s repeat has a Show if such as Title = 'CEO', and that field is not printed anywhere else, publish a new version to get the right content.
• In a Word template, the same kind of condition ({{#if Title = 'CEO'}} inside {{#Contacts}}) now reads each row straight away, with no republish, so existing documents may print differently.

Custom or cloned permission sets

• The packaged permission sets are updated for you. If you made your own, add:
  • every set that generates documents: Read on the Output Formats field of Template Release. Without it, generation fails for that user.
  • every set that builds templates: Read and Edit on the Output Formats field of Template Version.
  • every set or profile that sends for e-signature: Read on the Seal Failure Code field of Signature Request. Without it, the Sliick Signatures card does not load.

Custom integrations

• If an integration sets the old output-format switches, it must stop. Change formats by publishing a draft instead.
• Some messages are new or reworded. Update anything that checks for the old wording.

Formats are picked on each version

• Pick PDF, Word or both on a draft, in the new Formats this version makes card. At least one must stay ticked.
• Users get those formats when you publish. Until then they keep what is live, and the card says what that is.
• Asking for a format the template does not make is refused, with the format to use instead.
• A Flow, list view or batch that does not name a format gets the template’s own: PDF if it makes PDFs, otherwise Word.
• Lock output format is retired. To offer one format only, tick just that format and publish.
• See Word output.

Salesforce values are locked in Word

• In a Word file, values from Salesforce can no longer be edited or deleted. The wording around them stays editable.
• Change this with Salesforce values in Word (Locked or Editable) in the template’s Output settings. It applies straight away, with no republish.
• PDFs are not affected.
• See Word output.

Conditions inside a list

• In a designed template, a Show if inside a repeat can name a field without the list name. Inside a repeat over Contacts, Title = 'CEO' means Contacts.Title = 'CEO'. Before, it saved but was always false.
• A field the row does not have is now refused when you save.
• Word templates work the same way: {{#if Title = 'CEO'}} inside {{#Contacts}} reads each contact’s Title.
• See Repeats and conditional content.

E-signature

• When a seal cannot be made and trying again will not help, the Sliick Signatures card says what happened and what to do next.
• The emails to the sender now point to the Sliick Signatures card.