Doc Batches

The Doc Batches tab is where admins submit and monitor bulk runs: one template or bundle, run against many records. You need Sliick_Docs_Admin or Sliick_Docs_Template_Author to reach it.

Submit a new batch

1. Click New batch.

2. Pick a template (only templates with a published release appear) or a bundle.

3. Pick a source:

   • By filter: build conditions field by field in the Builder, which is the default. Pick a Field, an Operator and a value; date and datetime fields also offer a Value kind for relative literals such as TODAY or LAST_N_DAYS:30, alongside a real date picker for an exact one. Stack more conditions with Add condition; all conditions must match. Anything the Builder cannot express, such as OR logic or nested grouping, drops to Advanced (SOQL), a raw WHERE-clause box. Leave the filter blank to target every record of the base object.
   • By report: pick a tabular Salesforce report of up to 2,000 rows, or click Copy these filters into the builder to bring the report’s own filters across as editable conditions and refine them from there. Anything that cannot be translated is listed by name rather than silently dropped.
   • By record IDs: paste a list of up to 2,000 record IDs. This source is also available from the Flow action.

   

4. Pick a batch size, 1 to 200, default 1.

5. Pick an output mode:

   • Individual (default): one file per record, attached to that record.
   • Combined PDF only: one merged PDF attached to the batch row, with no per-record files.
   • Both: one file per record plus a combined PDF.

6. Optionally pick an Output Format: PDF (default) or Word. Word batches require Individual mode.

7. Click Analyze.

The pre-flight verdict shows release readiness, the record count against the 50,000 cap, and, for Combined or Both, a size estimate. Combined-output batches with more than 50 records are flagged upfront with an actionable “Switch to Individual mode” message instead of failing partway through a large run.

Spot-check a sample

From the verdict, click Preview sample to step through up to 5 sample records and see exactly how each will render. This catches merge-field problems before generating 500 documents.

Monitor

The batch monitor refreshes every 5 seconds. The header shows a status badge and progress bar, and the per-record table updates as each record completes. While the run is in flight, Cancel is available and Sliick Docs stops the underlying work as soon as it can.

When the run terminates, the recent-batches sidebar updates and a Sliick Docs Batch notification is sent to whoever submitted it.

Download

• Individual or Both: Download all as ZIP is available on the monitor. It runs immediately for up to 50 records and asynchronously above that, with a notification when the ZIP is ready. Each batch also lists per-record files inline.
• Combined or Both: the combined PDF sits on the batch row itself, as a single download.

Retry failed records

After a batch ends as Partial Success or Failed, expand the row and click Retry failed. If the template has been republished since the original run, Sliick Docs surfaces that in the confirmation dialog so you can decide whether to re-run against the original release or the new one. The new batch links back to the original so you can trace retry chains. It is capped at 2,000 failed records per retry.

Limits worth knowing

Limit	Default	Configurable?
Records per batch	50,000	No, a Salesforce platform limit
Record IDs per Flow call	2,000	No
Records per list-view mass action click	200	No, the Salesforce list-view selection cap
Concurrent batches per template or bundle	3	No
Immediate ZIP record cap	50	Yes, through custom metadata
Batch size (records per chunk)	1	Yes, per submission, 1 to 200
Combined-mode record cap	50	No, rejected upfront by the analyzer above 50
Combined-mode size cap	about 10 MB	No, a Salesforce platform limit