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 definition called “PdfToHtmlDef.”
- Select the definition and click the “design” button
- Drag a “PdfToHtml” step from the toolbox
- Connect the dots between the Start and “PdfToHtml” step
- Click the "PdfToHtml" step to configure its "Required" properties. Provide the step name. Provide the PDF input file path on the app server. Provide the variable/global reference to store the HTML output file path. Click the Save button to confirm.
- Click the "Email" step to configure its "Required" properties. Provide the step name.
- 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/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 execute. Render the process instance. Click on 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 it (drag-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.