generateOutputDoc Step
Description:
This step generates a PDF document from the rich text content.
Inputs
- docContent– Document Content
- fileVariable– Variable to hold the file name of the output document
- templatefilePath- Path to the template file
Returns
- True – step executed successfully
- False – step failed to execute
Usage:

Example:
Let’s build and execute the “generateOutputDocDef” example.
- Create a new definition called “generateOutputDocDef” and open the definition in designer mode.
- Drag a “generateOutputDoc” step to the canvas.
- Connect the dots between the “Start” and “generateOutputDoc” steps, as shown above.
- Define a variable or a global to store the output file path.
- Click the “generateOutputDoc” step to configure its “Required” properties. Provide a name for the step. Click the button to enter the document content in rich text format. Provide the variable or global reference to store the output file path. Click the Save button. Note: Click the "AI Predict" button to have the Copilot add new process steps that match your process description.

- Click the button to include the rich text document content. A pop-up window appears for configuration. Using the rich text user interface, enter the required text. Click the Save button.

- Click the “generateOutputDoc” step to configure its “Optional” properties. Provide the template path to use for generating the PDF document. Click the Save button.

- The “Logging” configuration is necessary for documentation and also measures workflow progress and percent complete. This is achieved by configuring the step state and percent fields individually, as shown below. Configure the “Logging” using the following properties.

- Save the process definition, create a process instance, and execute it. Render the process instance and select the step variables or properties to view.

- The PDF document, which contains rich text, is rendered here for reference.

Definition Sample:
You may download the sample definition(s) from the link here and later import them (drag-and-drop) to your FlowWright Process Definition (XML file) or Form Definition (HTML file) page.
Note: Please verify and complete the process steps for any missing configurations, such as file path references and database connections, after the import. Then, save the definition to confirm the changes.