For the complete documentation index, see llms.txt. This page is also available as Markdown.

Automate E-Signature in Batch

This page will walk the user through setting up a Automated Batch Process for E-Signature solutions. We will accomplish this by setting up 2 Flows, one screen flow and one record-triggered Flow.

Understanding the Overall Schema

Outlined above is the generalized process from start to finish users will take to generate an S-Sign Request using a Record Triggered Flow.

The process goes as follows:

  1. Collect Data that will be used for document generation (S-Sign Enabled Template + Object Record)

  2. Generate the document from the collected data

  3. Prepare the Envelope the Generated Document will be stored in

  4. Seal the Envelope in preparation to deliver the request

  5. Send out the request for Electronic Signature

This use case is more unique, considering we couple the use of a Screen Flow to do the data collection and document generation in batch, then leverage a record-triggered after save flow to create, seal, and deliver the envelope.


Phase 1: Configure the Batch Generation

In large the screen flow is our standard document generation steps through flows. With batch generation, the key characteristic that needs to be focused on is the input variables. The Base Record IDs and Template IDs inputs only accept Collection variables. After we use the Get Records Invocable Actions to find the data we want to generate, we will use the assignment variable to assign both the templates and object records to collections. Then we feed the collections into the Generate in Batch Invocable Action.


Phase 2: Construct the Record-Triggered Flow

  1. Construct the Flow using the same process outlined in Automate E-Signature with Record-Triggered Flows

  2. Ensure all Invokable Actions are added to the Asynchronous Path

  3. Do not include any invokable actions that are included in Phase 1

  4. Add the Triggering S-Doc ID to the collection, this will be provided to the Attachments option in the Send Email invocable action

Record-Triggered Flows will batch all qualifying records into a single transaction. Restrict the number of S-Docs generated in Phase 1 to avoid encountering Salesforce Governor Limits.

Last updated

Was this helpful?