fileExist Step
Description:
This step is used to verify the file's existence on the application server.
Inputs
- filePath – file name including the file path
Returns
- True – file exists
- False – file does not exist
Usage:
Example:
Let’s build and execute the “fileExistDef” example.
- Create a new process definition called “fileExistDef” and open the definition in designer mode.
- Drag a “fileExist and placeHolders” step to the canvas.
- Connect the dots between the “Start” and other steps, as shown above. Click the connection link to configure the “TRUE and FALSE” workflow paths.
- Click the "fileExist" step to configure its "Required" properties. Provide a name for the step. Provide the file path on the application server. Click the Save button. Note: Click the "AI Predict" button for the Copilot to add new process steps that match your process description.
- 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 below. Configure the “Logging” using the following properties.
- Save the process definition, create a new instance, and then execute it. Render the process instance. The step verifies the file's existence and takes the “TRUE or FALSE” path as configured. Here, the workflow takes the “TRUE” path as the file exists.
Definition Sample:
You may download the sample definition(s) from the link here and later import them (drag-and-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.