Description:
This step validates the PDF document against a PDF standard.
Inputs
- inputFilePath - Input File Path
- validationType - PDF Validation type
- outputFilePath – Output file path
- pdfVirtualPath – PDF Virtual file path
Returns
- True – step executed successfully
- False – step failed to execute
- Error - step execution error
Usage:
Example:
Let’s build and execute the pdfValidate example.
- Create a new definition called “pdfValidateDef”
- Select the definition and click the “design” button
- Drag the “pdfValidate” step to the canvas
- Connect the dots between the start and the step, as shown in the above image
- Define a few variables/globals to store the file path result after execution
- Click the "pdfValidate" step to configure its "Settings" properties. Give the step a name. Provide the source file path on the application server. Provide the PDF validation type. Provide the variable references to hold the Output and Virtual PDF file paths. Click the Save button to confirm.
- 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 “pdfValidate” process step to view the properties. This step validates the PDF document against one of the following PDF standards and returns the True value.