Description:
This step converts a PDF to an HTML document and stores it on the application server.
Inputs
- pdfFilepath - provide the file path on the app server
- varGlobalHTMLFilepath - the output file path on the app server
Returns
- True – step executed successfully
- False – step failed to execute
Usage:
Example:
Let’s build and execute the “PdfToHtmlDef” example.
- Create a new process definition called “PdfToHtmlDef” and open the definition in designer mode.
- Drag a “PdfToHtml” step to the canvas.
- Connect the dots between the “Start” step and “PdfToHtml” steps, as shown above.
- Define a variable or a global to hold the HTML file path.
- Click the "PdfToHtml" step to configure its "Required" properties. Provide a name for the step. Provide the path to the PDF input file on the app server. Provide the variable or global reference to store the path to the HTML output file. Click the Save button. Note: Click the "AI Predict" button for the Copilot to add new process steps that match your process description.
- Click the "Email" step to configure its "Required" properties. Provide a name for the step. Click the Save button. Note: Click the "AI Predict" button for the Copilot to add new process steps that match your process description.
- Click the "Email" step to configure its "Optional" properties. Configure the email recipients. Provide the email subject and message content. Click the File Attachment button. Provide the variable or global reference that holds the HTML file path as below. Click the Save button.
- The “Logging” setting configuration is necessary for documentation and also measures the workflow progress and the percent complete. This is achieved by configuring the step state and percent fields individually, as shown in the images below. Configure the “Logging” using the following properties.
- Save the process definition, create a new instance, and then execute it. Render the process instance. Click the process step to view its properties. The “PdfToHtml” step should make an HTML file and email the attachment to the recipient as configured.
- The email containing the HTML file attachment is shown 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 import. Then, save the definition to confirm the changes.