Skip to content

Generation at scale and your own storage

Sliick Docs is native by default: everyday documents are made inside Salesforce, with no setup. Two premium options help at the demanding end:

  • Premium high-volume rendering, for large, photo-heavy PDFs.
  • Your own cloud storage, to keep generated documents out of Salesforce file storage.

Both connect outside your Salesforce org, as explained below.

Large, photo-heavy documents, such as evidence packs with hundreds of photos or long reports full of images, are the hardest to make inside Salesforce. Standard generation can run out of room on them. Premium high-volume rendering makes these PDFs on a Sliick-managed rendering service that does not have those limits, so they generate reliably.

This option connects outside your org. When it is on, the document’s content and images are sent to the Sliick-managed service, the PDF is made there, and the finished file is saved back to Salesforce.

What to know:

  • It covers every template PDF, not only the big ones. Once it is on, PDFs made from a single template, from the record page or a Flow, go through the service. They are made in the background, and you are notified when the file is ready. In a Flow, this means the Generate Sliick Doc action does not hand back the file straight away (see Flow actions).
  • PDF only. Word files are always made inside Salesforce.
  • Batches and bundles too (new in 3.4). PDF batches, of templates or bundles, from the Doc Batches tab, a list view or the bulk Flow action, and combined PDF bundles from the record page or the bundle Flow action, are also made on the service. See Premium batches and bundles below.
  • Documents are always saved. A template set to download only still saves its file, because the PDF arrives once the service has finished rather than straight to your browser. This is also why these templates work in a Flow.
  • Authors change nothing. Templates work the same way.

With premium rendering on, every PDF batch and every combined PDF bundle is made on the Sliick-managed service. There is no separate setting. Word batches and Word bundles are still made inside Salesforce.

  • Bigger batches. A premium batch takes up to 100,000 documents, and each document in a bundle counts (a three-document bundle reaches the limit at about 33,000 records). The pre-flight check shows the count and refuses a bigger batch before anything is sent.
  • A warning about your daily file allowance. Salesforce limits how many files an org can add in a day. If a batch would use a lot of that allowance, the pre-flight check warns you. You can still submit it: delivery pauses at the limit and carries on when files can be added again, so a very large run can take more than a day.
  • Files arrive as they are ready. Each record’s file is saved on the record while the batch is still running. A combined PDF arrives in parts of up to about 25 MB, each holding whole records in your sort order.
  • The batch is decided when you submit it. A batch submitted while premium is on finishes on premium, even if premium is turned off while it runs.
  • If the service cannot take the run when it starts, the batch or bundle fails and no documents are made. Its message says what to do, for example try again later, check the template, or contact Sliick support to have premium rendering enabled. Once a run has started on the service, it stays there. Word output is not affected.
  • Bundles arrive in the background. The record page shows the bundle as in progress until the file is ready, and the bundle Flow action works like the single-document action (see Flow actions).

What happens to the documents. For a premium batch or bundle, each document’s content, its images and the finished PDFs are held on the Sliick-managed service while the run is made. When the run finishes, fails or is cancelled, everything held for it is deleted, and the batch console shows when that happened. If the deletion cannot be confirmed, what is left is removed automatically, at the latest about 6.5 days after the run started.

How to watch, cancel and resume a premium batch is covered in Doc Batches.

Premium rendering needs to be enabled for your organisation by Sliick first, so talk to the team. Then an admin with Sliick_Docs_Admin:

  1. Opens Sliick Docs Settings and goes to the Premium Rendering tab.
  2. Under Sliick Docs Service, follows the one-time setup shown on screen, enters the integration user, and clicks Connect to Sliick Docs Service.
  3. Under Rendering, turns on Premium off-platform rendering, and clicks Save premium rendering.

With Sliick Files installed, generated documents can be saved to your own cloud storage instead of Salesforce Files. This keeps high-volume output off your Salesforce file storage, which can matter for cost or for your data rules. Each document is still linked to its record, just as before.

To turn it on, an admin opens Sliick Docs Settings, goes to the Defaults tab, and turns on Use Sliick Files storage.

This option also connects outside your org: the finished files are stored in the cloud storage your organisation connected through Sliick Files.

It pairs well with evidence packs: photos are read from your connected storage, and the finished document is saved back to it.