Description:

This step decrypts encrypted files and stores the decrypted output.

The Decrypt and Store Files workflow step reads one or more encrypted files, decrypts their contents using the configured encryption mechanism, and writes the decrypted files to the specified output locations.

The step supports decrypting a single file by specifying input and output file paths, or processing multiple files in a single operation using a configurable file-mapping list.

This step provides an efficient way to automate secure document processing, encrypted file exchange, regulatory workflows, data migration, archival recovery, and enterprise document automation.

The step supports:

• Single file decryption
• Multiple file decryption
• Batch file processing
• Configurable input and output locations
• File mapping support
• Integration with FlowWright workflow automation

This step can be used for:

• Secure document processing
• Encrypted document exchange
• Compliance workflows
• Data migration
• Archive restoration
• File processing automation
• Business process automation

Usage:

The Decrypt and Store Files step is typically placed before document processing, OCR, PDF manipulation, archival, or content extraction activities where encrypted files must first be converted into readable documents.

The workflow reads the encrypted file (s), decrypts the contents, writes the decrypted file (s) to the configured locations, and makes them available to subsequent workflow steps.

A typical workflow might look like this:

Once the files have been decrypted, later workflow steps can:

• Read document contents
• Convert documents
• Perform OCR
• Validate digital signatures
• Archive documents
• Upload files to the DMS
• Continue workflow execution

The encrypted files must already exist and be accessible before this step is executed.

Example:

Let’s build and execute the “decryptFilesDef” example.          

• Create a new process definition named “decryptFilesDef” and open it in Designer mode. 
• Drag a “decryptFiles” step to the canvas. 
• Connect the dots between the “Start” and “decryptFiles” steps, as shown above. 
• Click the "decryptFiles" step to configure its "Required" properties. Provide a name for the step. Provide a variable or global reference to store the process definition GUID. 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 "decryptFiles" step to configure its "Optional" properties. Click the button to configure multiple file mappings. A pop-up window will appear for configuration. Click the Add Row (+) button to insert an empty row. Provide the input and output file paths. Click the Save button. You may add multiple file paths for decryption using the Add Row button. 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 new Process Instance and execute it. When the workflow reaches the Decrypt and Store Files step, FlowWright reads the configured encrypted file or file mappings, decrypts each file, and writes the decrypted output to the specified destination. If the operation completes successfully, the workflow follows the True return path. If an encrypted file cannot be located, the decryption process fails, the output file cannot be created, or file permissions prevent access, the workflow follows the False return path. Click the process step to view its properties. The step should successfully decrypt the configured files, generate the decrypted output files, and return True upon completion.

Tips:

• Verify that the encrypted source files exist before executing the workflow.
• Ensure the FlowWright server has permission to read the encrypted files and write the decrypted output files.
• Use File Mappings when decrypting multiple files within a single workflow execution.
• Store decrypted files in a secure location with appropriate access controls.
• Remove decrypted files after processing if organizational security policies require temporary storage only.
• Test decryption workflows in a non-production environment before processing sensitive production documents.
• Use the True and False return paths to implement appropriate success and exception handling.
• Combine this step with PDF Validate Signature, Convert Word to Text, PDF to HTML, Azure OpenAI Chat Completion, Archive Document, or Upload Document workflow steps to automate secure document processing workflows.

Notes:

• The encrypted source files must be accessible to the FlowWright server.
• Either a single input/output file pair or multiple file mappings may be configured.
• The decrypted output files are written to the specified destination paths.
• Invalid source file paths, unsupported encryption formats, incorrect encryption keys, insufficient file permissions, or write failures may cause the step to return False.
• This step creates decrypted copies of the source files and does not modify the original encrypted files.
• Decrypted files should be protected according to your organization's security and data retention policies.
• The workflow should include appropriate handling for both True and False return paths.
• Consider securely deleting temporary decrypted files after downstream processing has completed if the original encrypted files must remain the system of record.

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:

• Encrypted file paths
• Decrypted output paths
• File mappings
• File system permissions
• Workflow variable definitions
• Environment-specific settings

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

Click here to download the sample file.