Multi-template bundles
A bundle combines several templates into one PDF or Word document for a single record. For example, a Sales Bundle might hold a cover letter, the quote, the terms and conditions, and an optional NDA.
To build a bundle you need the Sliick_Docs_Admin or Sliick_Docs_Template_Author permission set.
Create a bundle
Section titled “Create a bundle”
- Open the Doc Bundles tab.
- Click New Bundle.
- Enter a Bundle Name, the Base Object API Name (for example
Account) and an optional Description. Every template in the bundle must use this same object. - Click Create Bundle.
Add templates
Section titled “Add templates”
- On the bundle card, click + Add template.
- Pick a template. Only published templates on the bundle’s object are offered, and templates already in the bundle are left out.
- Tick Optional if the bundle should carry on without this template when it cannot be generated. Leave it unticked and the whole bundle fails if this template fails.
- Click Add. The template goes to the end of the list.
Use the up and down arrows on a row to change the order, which is the page order in the finished document. Use the trash icon to remove a template.
Include a template only sometimes
Section titled “Include a template only sometimes”A template in a bundle can have a rule that decides whether it is included, using the same style as a Show if block. For example, Account.Industry = 'Technology'. When the record does not match, that template is left out of the document. The rule is fixed when you publish the bundle.
A template with a rule shows a conditional pill on the bundle card.
Publish
Section titled “Publish”
Click Publish on the bundle card. The bundle locks in the current published version of each template, so it produces the same result every time, even if a template is changed later.
A combined PDF needs every template to make PDFs. If a template’s live version does not make PDFs:
- You cannot publish the bundle until you publish a new version of that template with PDF ticked, or remove it. See Proof, publish and versions.
- When generating, a required template stops the bundle with a message naming it. An optional one is left out, with a note on the run.
What the finished document looks like
Section titled “What the finished document looks like”Each template keeps its own look on its own pages: header and footer, watermark, Different first page setting, page size, margins and theme. In Word, each template becomes its own Word section.
Page numbers restart for each template, like a stapled packet: Page 1 of 3 for the cover letter, then Page 1 of 8 for the quote. A {{Pages}} in a template’s footer counts only that template’s pages.
Very large bundles can fail. On the record page, a combined file over 3 MB can’t be saved: you see “This bundle is too large to combine into one PDF. Generate its items separately, or remove the largest one.” and no document is made. From a Flow or a batch, a very large bundle can fail.
On the record page, keep the browser tab open until the bundle PDF is saved. If the tab is closed first, the run is marked Failed after 24 hours, with the reason on the Generation record. Generate the bundle again.
With premium high-volume rendering
Section titled “With premium high-volume rendering”If your organisation uses premium high-volume rendering, a combined PDF bundle from the record page or the Generate Sliick Bundle Flow action is made on the premium service instead (new in 3.4). Each template still keeps its own look and page numbers, and optional and required templates work the same way.
- It is made in the background. The record page shows the bundle as in progress until the file is ready, so you do not need to keep the tab open, and the size limit above does not apply.
- From a Flow, the file arrives a little later. There is no limit on premium bundles in one Flow run. See Flow actions.
- If the service cannot take the bundle, the generation fails with a message saying what to do, for example Try again later., and no PDF is made.
- Word bundles are still made inside Salesforce.
When a template in the bundle changes
Section titled “When a template in the bundle changes”
A published bundle does not update itself when one of its templates is republished. Instead:
- The bundle card shows a yellow badge such as 2 members updated. Hover over it to see which templates changed.
- A published bundle keeps the template versions it was published with. To use the new versions, create a new bundle with the same templates and publish it.
- The confirmation when you retry failed records on the Doc Batches page reminds you of this too.
Generating from a bundle
Section titled “Generating from a bundle”| You want | Use |
|---|---|
| One record, from the record page | The Bundle tab on the Sliick Docs Generator |
| One record, from automation | The Generate Sliick Bundle Flow action |
| Many records | Generate Sliick Docs (Bulk) with the bundle instead of a template, or the Doc Batches page |
Anyone who can generate documents can make a combined Word bundle, including users with only Sliick_Docs_User or Sliick_Docs_Automation. See Word output.