Automation
Automator Config
1. Open App Launcher and select Gutenburg app
2. Click Automators in the Salesforce navigation bar
Gutenburg automation begins with Automators. These reusable modules are invoked by a Flow or Apex, eliminating the need for manual user interaction.
Simply create the Automator, embed it in a Flow, and PDF generation is automatic.
3. Create a new Automator
4. Populate the Automator parameters.
Automator Name: Use a descriptive name that makes the purpose clear.
Templates: Add the name of one or many Templates to invoke.
*If using multiple Templates, separate the names with a comma.
5. Click Save
Flow Config
Navigate to Setup create a new Flow. Gutenburg is compatible with all Flow types.
Once the Flow criteria is specified, click the plus icon to add an element to the Flow.
Select to add an Action to the Flow.
Scroll to the folder containing Gutenburg actions.
There are 3 Gutenburg actions that achieve different things. They achieve distinct tasks, let's review what each one if for.
Create PDFs for 1 Record:
Create one or many PDF templates for a single record per Flow execution.
Create PDFs for Multiple Records:
Create one or many PDF templates for many records per Flow execution.
Map PDFs for Multiple Records:
(Advanced) Create a different PDF template for each record in a list.
Each Flow action has slightly different configuration options. The following section covers each one individually.
Create PDFs for 1 Record:
Use this action when one or many PDFs are needed for just a single record.
Inputs:
Automator Names: Specify one or many Automators to invoke when the Flow fires.
*If using multiple, separate Automators with a comma.
Record ID: The base record to use within the PDF.
For record triggered Flows, Triggering Record > Record ID is typically used.
Create PDFs for Multiple Records:
Use this action when one or many PDFs are needed for many records at once.
Inputs:
Automator Names: Specify one or many Automators to invoke when the Flow fires.
*If using multiple, separate Automators with a comma.
Records: Accepts a list of records and will generate PDFs for each.
This can be populated in many ways: an example using Get Records is below.
Map PDFs for Multiple Records:
Use this action when different PDFs are needed for each record. This action is advanced and primarily for batch and bundled use cases.
Inputs:
Object: Choose the Object of which records will be passed into the Flow.
Automator Names: Specify one or many Automators to invoke when the Flow fires.
*If using multiple, separate Automators with a comma.
Records: Accepts a list of records and will generate PDFs for each.
This can be populated in many ways: an example using Get Records is below.
Most implementations of this feature require surrounding Flow architecture. Although flexible, each implementation requires common elements.
Required Elements:
List of Automators: Flow Variable.
Data Type = Text
Accepts Multiple Values = Checked
List of Records: Flow Variable.
Data Type = Records
Accepts Multiple Values = Checked
This can be populated in many ways: an example using Get Records is below.