Multi-template bundles

A bundle is a named, versioned collection of templates rendered together against one source record to produce a single combined PDF or Word document. A Sales Bundle might combine a cover letter, the quote itself, the terms and conditions, and an optional NDA addendum. You need Sliick_Docs_Admin or Sliick_Docs_Template_Author to build one.

Create a bundle

1. Open the Doc Bundles tab.
2. Click New bundle.
3. Fill in the display name, the base object (every member template must share it), and an optional description.
4. Click Create.

Add templates

1. On the bundle card, click + Add template.
2. Pick a template that shares the bundle’s base object. Templates already in the bundle are filtered out.
3. Set it Required or Optional. Required means the bundle fails if the template is inaccessible; Optional means it is skipped and the run continues.
4. Click Add. The item appends to the end.

Reorder items with the up and down arrows on each row, and remove items with the trash icon.

Include an item only sometimes

Each bundle item can carry an optional inclusion expression, using the same grammar as the Show if block, for example Account.Industry = 'Technology'. The expression is frozen into the bundle release at publish and evaluated at runtime against the source record. Items that evaluate to false are skipped from the combined document.

Publish

Click Publish on the bundle card. Sliick Docs snapshots each member template’s current active release into the new bundle release. Once published, the bundle renders the same way every time, even if a member template is later republished.

A combined PDF needs every member to be able to produce a PDF. A member whose Allow PDF output is off, or whose release has no proofed PDF, is refused: a required member fails the bundle, naming the template, and an optional one is left out with a note on the run. Publishing a bundle that contains such a member is refused until you turn its PDF on (then proof and publish it) or remove it. See Proof, publish and versions.

What the combined document looks like

Each member is rendered on its own and the results are joined, so every member keeps its own header and footer, watermark, Different first page setting, page size, margins and theme, on its own pages and nowhere else. This is true in PDF and in Word, where each member becomes its own Word section.

Page numbers restart with each member: Page 1 of 3 for the cover letter, then Page 1 of 8 for the quote, like a stapled packet. A {{Pages}} in a member’s footer counts that member’s pages.

A very large bundle can be refused. The joined file is assembled in one go, so there is a size ceiling. The record page has the most room, because the browser does the joining; Flow and batches have less. Over the ceiling you get “This bundle is too large to combine into one PDF. Generate its items separately, or remove the largest one.” and no document is produced.

On the record page, if the browser tab is closed before the finished bundle PDF is saved, the run is marked Failed after 24 hours, with the reason on the Generation record. Generate the bundle again.

When a member template changes

Bundle releases are immutable by design, so a bundle does not auto-update when a member template is republished. Instead:

• The bundle library card shows a yellow Members updated badge, with a tooltip listing the affected templates.
• A one-click Republish with current members action produces a fresh release that re-snapshots every current member release.
• The retry-failed confirmation dialog on the Doc Batches console calls out the same thing.

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 console

Combined Word bundles work for everyone who can generate, including users who hold only Sliick_Docs_User or Sliick_Docs_Automation. See Word output.