containsInFile Step
Description:
This step verifies the search item is contained 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 called “containsInFileDef”
- Select the definition and click the “design” button
- Drag a "containsInFile" step to the canvas
- Connect the dots between the start and "containsInFile" step
- Define a variable/global to store the result after execution
- Click on the "containsInFile" step to configure its “Settings” properties. Provide a name to the step. Provide the file path. Provide the search items list separated by a carriage return. Provide a variable/global to store the result.
- The “Logging” setting configuration is necessary for documentation and also measure the workflow progress and the percent complete. This is acheived 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. 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 here and later import it (drag-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.