Overview
After a document is generated by an upstream flow, save flows upload it to the configured destination. Each save flow reads the GeneratedDocumentId from the automation context and handles the upload.
Quick Steps
Save Generated Document To ProcessPro
Complete the document generation flow first.
The Save to ProcessPro flow reads the GeneratedDocumentId.
The document is uploaded to Azure Blob storage via DocumentStorage.
A new Process record is created under the configured Managed Document Type (Category).
The document appears in the Managed Documents area with the correct category.
Metadata includes workflow and submission references.
Save Generated Document To SharePoint
The Save to SharePoint flow reads the GeneratedDocumentId.
A SharePoint destination is resolved from tokens and config (folder path template, file name template).
The file is uploaded to the resolved SharePoint folder.
Metadata fields are populated if configured.
Check-in is performed automatically.
Save Generated Document To Azure Storage
The Save to Azure Storage flow reads the GeneratedDocumentId.
An Azure Blob path is resolved from config (blobPathTemplate + baseUrl + sasToken, or sasUrlTemplate).
The document is uploaded via HTTP PUT with SAS authentication.
Save Generated Document To External API
The Save to External API flow reads the GeneratedDocumentId.
An HTTP request is built from the configurable JSON spec (connectionKey, headers, body template).
The document and metadata are sent to the configured endpoint (e.g., Laserfiche, Dropbox).
If the endpoint returns an error, the flow surfaces the error and audit records the failure.
Chaining Example
A multi-step pipeline on a single activity:
Generate Document From Template — creates the document
Save to ProcessPro — uploads to Managed Documents
Save to SharePoint — uploads to SharePoint
Each flow receives the GeneratedDocumentId from the previous flow. Three separate audit entries are created, one per flow.
Important: Save flows require a valid GeneratedDocumentId from an upstream generation flow. Running a save flow without a generated document will fail with a clear error.