Description:
This step encrypts and stores the files on the application server.
Inputs
- inputFilePath - provide the input file path on the application server
- outputFilePath - provide the output path to store the encrypted file
- fileMapping - file mappings list for multiple encryption
Returns
- True – step executed successfully
- False – step failed to execute
Usage:
Example:
Let’s build and execute the “encryptFilesDef” example.
- Create a new process definition named “encryptFilesDef” and open it in Designer mode.
- Drag a “encryptFiles” step to the canvas.
- Connect the dots between the “Start” and “encryptFiles” steps, as shown above.
- Click the "encryptFiles" 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 "encryptFiles" 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. Enter the input and output file paths. Click the Save button. You may add multiple file paths for encryption using the Add Row 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 in the images below. Configure the “Logging” using the following properties.
- Save the process definition, create a new instance, and execute it. Render the process instance. Click the process step to view its properties. The “encryptFiles” step should store the file at the output path.
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 (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 the import. Then, save the definition to confirm the changes.