Description:

This step compares a collection of strings using fuzzy string matching.

The Compare Strings Using Fuzzy Compare workflow step analyzes a list of strings and determines how closely they match using fuzzy comparison algorithms. Instead of requiring exact character-by-character matches, fuzzy matching measures similarity, making it ideal for comparing strings that may contain spelling variations, abbreviations, formatting differences, or minor typographical errors.

During execution, the step compares the supplied string list against the configured match ratio threshold. If the calculated similarity satisfies the specified ratio, the workflow follows the True return path. Optionally, the calculated average similarity ratio can be stored in a FlowWright Variable or Global Variable for later workflow processing.

This step provides an efficient way to automate intelligent text matching within document processing, OCR validation, customer matching, data cleansing, search workflows, and business process automation.

The step supports:

• Fuzzy comparison of multiple strings
• Configurable similarity threshold
• Automatic similarity evaluation
• Storage of the calculated average match ratio
• Integration with FlowWright workflow variables
• Conditional workflow routing based on similarity

This step can be used for:

• OCR validation
• Customer name matching
• Duplicate record detection
• Address comparison
• Product matching
• Data quality validation
• Business process automation

Usage:

The Compare Strings Using Fuzzy Compare step is typically placed after OCR processing, text extraction, customer lookup, or data import activities that require approximate string matching.

The workflow compares the supplied string list, evaluates the similarity score against the configured threshold, optionally stores the calculated average ratio, and routes execution based on the comparison result.

A typical workflow might look like this:

Example:

Let’s build and execute the “fuzzyStringCompareDef” example:

• Create a new definition named “fuzzyStringCompareDef” and open it in designer mode. 
• Drag an “UpdateVariable, fuzzyStringCompare” step to the canvas.
• Connect the dots between the “Start” and other steps, as shown above. 
• Define a variable or a global to store the string and the average ratio. 
• Click the "UpdateVariable" step to configure its "Required" properties. Provide a name for the step, then click the Save button. Note: Click the "AI Predict" button to have Copilot add new process steps that match your process description. 

• Click the "UpdateVariable" step to configure its "Optional" properties. Click the button to update multiple variables, or provide a single variable reference and a value as shown below. Select “No” if the variable value is not a C# expression. Click the Save button. 

• Click the "fuzzyStringCompare" step to configure its "Required" properties. Provide a name for the step. Click the button to enter a list of strings. Set the match ratio. Click the Save button. Note: Click the "AI Predict" button to have the Copilot add new process steps that match your process description. 

• Click the button to provide a list of strings. Click the Add Row (+) button to insert an empty row. Enter a string value. Click the Save button. You may insert multiple strings by using the Add Row button. 

• Click the "fuzzyStringCompare" step to configure its "Optional" properties. Provide a variable or global reference to store the average ratio. Then 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 in the images 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 Compare Strings Using Fuzzy Compare step, FlowWright compares all supplied strings using fuzzy comparison techniques and calculates an average similarity ratio. If the calculated similarity satisfies the configured threshold, the workflow follows the True return path. If the calculated similarity falls below the configured threshold, the workflow follows the False return path. If configured, the calculated average similarity ratio is stored in the specified Variable or Global Variable for use by subsequent workflow steps. Click the process step to view its properties. The step should successfully evaluate the supplied strings and return the appropriate workflow path based on the configured match ratio.

Tips:

• Use realistic similarity thresholds based on your business requirements. For example, 95–100% for strict matching and 80–90% for more tolerant matching.
• Store the calculated average ratio when later workflow decisions require additional evaluation.
• Use workflow variables to dynamically build the string list during execution.
• Fuzzy comparison is particularly useful when processing OCR results, imported customer data, or manually entered information.
• Avoid setting the match ratio too low, as unrelated strings may be considered matches.
• Use the True and False return paths to implement appropriate workflow branching.
• Combine this step with OCR, Extract Text, Remove Blank Pages, Update Variables, Conditional Routing, or Notification workflow steps to automate intelligent document and data processing workflows.

Notes:

• The string list must contain at least one valid string value before execution.
• The configured match ratio determines the minimum similarity required for a successful comparison.
• If configured, the calculated average similarity ratio is stored in the specified Variable or Global Variable.
• Fuzzy comparison is designed to tolerate minor spelling differences, formatting variations, abbreviations, and typographical errors.
• Very low similarity thresholds may produce unexpected matches.
• Invalid string lists or improperly configured comparison values may cause the step to return False.
• The workflow should include appropriate handling for both True and False return paths.
• This step is intended for approximate text matching and should not replace exact comparisons where precise equality is required.

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:

• String list configuration
• Match ratio
• Average ratio variable mapping
• Workflow variable mappings
• Environment-specific settings

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

Click here to download the sample file.