containsInFile Step
Description:
This step verifies that the search item is present in the file contents.
Inputs
- inputFilePath - Path for the file on the App server
- searchTerms - List of search terms
- variableToStoreValue - Variable/Global to store the list of matched search terms
Returns
- True – step executed successfully
- False – step failed to execute
Usage:
Example:
Let’s build and execute the “containsInFileDef” example.
- Create a new definition named “containsInFileDef” and open it in designer mode.
- Drag a "containsInFile" step to the canvas.
- Connect the dots between the “Start” and "containsInFile" steps, as shown above.
- Define a variable or a global to store the result.
- Click the "containsInFile" step to configure its “Required” properties. Provide a name for the step. Provide the file path. Provide a list of search items, each on a new line. Provide a variable or a global to store the result. 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” 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 instance, and execute it. The process step should search the file contents for "terms" and store the match in a “variable.result” as configured.
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.