Description:

This step validates the digital signature embedded within a PDF document.

The PDF Validate Signature workflow step reads a PDF document from the specified input file path and verifies the integrity and validity of its digital signature. During execution, the step checks whether the document contains a valid digital signature and whether the signed content has remained unchanged since the signature was applied.

This step provides an efficient way to automate document verification before approval, archival, distribution, compliance processing, or integration with downstream business systems.

The step supports:

• Validation of digitally signed PDF documents
• PDF input file processing
• Signature integrity verification
• Automated document authenticity validation
• Integration with PDF processing workflows
• Conditional workflow routing based on validation results

This step can be used for:

• Electronic document verification
• Compliance workflows
• Contract processing
• Invoice validation
• Regulatory document management
• Digital records management
• Business process automation

Usage:

The PDF Validate Signature step is typically placed before document approval, archival, import into a document repository, or downstream business processing.

The workflow opens the specified PDF document, validates its digital signature, and routes execution based on the validation result.

A typical workflow might look like this:

Once the signature has been successfully validated, later workflow steps can:

• Archive the document
• Upload the document into the DMS
• Route the document for approval
• Generate audit records
• Notify stakeholders
• Continue document processing workflows

The input PDF document must already exist and be accessible before this step is executed.

Prerequisite:

The PDF document must contain a digital signature that can be validated by the FlowWright PDF processing engine.

Example:

Let’s build and execute the “pdfValidateSignatureDef” example:

• Create a new process definition called “pdfValidateSignatureDef” and open it in Designer mode. 
• Drag a “pdfValidateSignature” step to the canvas.
• Connect the dots between the “Start” and “pdfValidateSignature” steps, as shown above. 
• Click the "pdfValidateSignature" step to configure its "Required" properties. Provide a name for the step and the path to the PDF file. Then click the Save button. Note: Click the "AI Predict" button to have Copilot add new process steps that match your process description. 

• 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 in the images below. Configure the “Logging” using the following properties.

• Save the Process Definition. Create a new Process Instance and execute it. When the workflow reaches the PDF Validate Signature step, FlowWright opens the specified PDF document and validates its digital signature. If the signature is successfully validated and the signed content has not been modified, the workflow follows the True return path. If the document cannot be found, is not a valid PDF, contains no valid signature, has been altered after signing, or the signature validation fails, the workflow follows the False return path. Click the process step to view its properties. The step should successfully validate the document's digital signature and return the appropriate workflow path based on the validation result.

Tips:

• Verify that the input PDF file exists before executing the workflow.
• Ensure that the document has been digitally signed before attempting signature validation.
• Use workflow variables to dynamically specify the input file path.
• Perform signature validation before archiving or approving important documents.
• Use the True and False return paths to implement appropriate business rules and exception handling.
• Combine this step with PDF Sign, Remove Blank Pages, Create Document, Archive Document, Approve Document, or Email workflow steps to automate secure document processing workflows.

Notes:

• The input file must be a valid PDF document.
• The executing process must have permission to read the specified file.
• Signature validation verifies the integrity of the digitally signed document.
• Documents without valid digital signatures follow the False return path.
• Corrupted PDF files, inaccessible files, unsupported signatures, or modified documents may also result in the False return path.
• This step validates the digital signature but does not modify the PDF document.
• The workflow should include appropriate error handling for failed validation scenarios.
• Digital signature validation should be incorporated into workflows that require document authenticity, integrity, or regulatory compliance.

Definition Sample:

You may download the sample definition(s) from the link provided and later import them (drag-and-drop) into your FlowWright Process Definition page.

Note: Verify and complete any missing configuration after importing the sample, including:

• Input file path
• Workflow variable mappings
• File system permissions
• PDF document availability
• Environment-specific settings

After verifying the configuration, save the Process Definition before execution.

Click here to download the sample file.