The CloudFiles: Generate Document (Batch) action allows you to automate the generation of multiple documents in a single action within Salesforce Flow Builder. It simplifies the process of handling multiple document generation requests, reducing complexity and increasing efficiency for bulk operations.

Unlike the Generate Document action, which processes a single document at a time, the batch action takes a collection of input configurations and generates multiple documents asynchronously, each based on its respective template and parameters.

Below is how the action looks like. Detailed descriptions of the input and output parameters are provided in the following section.

The Generate Document (Batch) action processes a collection of document generation inputs in a single execution, where each input corresponds to a single document generation request. It automates bulk document creation with the same advanced features available in the standard Generate Document action.

Each variable in the collection input can specify a unique Generate Document action. Each Each processed input publishes a Document Generated event, which can be used to trigger additional automations or workflows.

Example Use Case:

A sales team needs to generate multiple Opportunity documents records in one go when the status is updated to 'Closed-Won'. Instead of using multiple Generate Document flow actions in the flow, a single Generate Document (Batch) action can be used to generate all the documents based on the input paramters.

The Generate Document (Batch) action has a single input parameter:

A collection of Apex-Defined Variables of the class cldfs__GenerateDocumentFlowInput.

Each cldfs__GenerateDocumentFlowInput represents the input configuration for generating one document and contains the same fields as the parameters for the Generate Document action:

The CloudFiles: Generate Document (Batch) action operates asynchronously, meaning it does not provide immediate outputs after execution, instead publishes events for each processed input.

Each document generation request (individual input) publishes a Document Generated event upon successful processing. Use these events to trigger downstream automations or flows, such as notifications or additional processing.