Using Document Composer from Workflow

The Workflow Engine can trigger document generation at any point in an automation. You add a Document Composer task node to your workflow, configure which template to use, and the Engine handles the rest when the workflow runs.

Prerequisites

• A Document Composer template must already be created in Studio before you can reference it from a workflow.
• The workflow must be able to provide the data that the template's bindings expect. Review the template's data source bindings and ensure the workflow has the required data available at the point the node runs.

Adding the Document Composer Node

In the Workflow editor, add a new task node and select Document Composer from the node type list.

Configuring the Node

Setting	Description
Template	Select the Document Composer template to use for this generation run.
Output File Name	The name of the generated output file. Supports variable substitution.
Output Destination	Where the generated document is saved or passed (e.g. stored to a path, added to workflow output data).

[Expand with full node configuration options once the Workflow task node is implemented and confirmed]

What Happens at Runtime

When the workflow reaches the Document Composer node:

1. The Engine loads the selected template.
2. The current workflow data context is passed to the Engine.
3. The Engine resolves all field bindings against the workflow data.
4. The output document is produced and stored at the configured destination.
5. The workflow continues to the next node.

Next Steps

• Using from DocControl Transmittal
• Using from Configurator