› User interface › Forms › Form events and actions › Form actions › Fuzzy search action

Fuzzy search action

Add a Fuzzy search action to a document validation form to perform a fuzzy search in a Validation activity. For example, if you enter 9600 as search text, all matching records (partial or complete) appear, irrespective of fields.

Fuzzy search is a technique of finding strings that closely (but not exactly) match a pattern in a fuzzy database, which is a single table or view exported from a relational database. A fuzzy database is relatively static and contains sensitive data in a table or view from a large relational database that is on a secured network and not readily available. A fuzzy index enables fast searching and matching of text values using non-exact string matching in record sets or specific columns.

You can configure Fuzzy search actions to apply filters to columns of the database.

  • The Fuzzy search action is available only for a document validation form.

  • It is mandatory to configure a remote fuzzy database in Kofax Search and Matching Server or the Transformation Designer to add and execute the Fuzzy search action in TotalAgility.

  • The Fuzzy search action allows the user to progress on the fuzzy search; however, any other actions that are configured to come after the Fuzzy search action continue to run and do not wait for the user to complete the fuzzy search.

  1. On the form modeling bar, click Actions and click New.

    The New action dialog box is displayed.

  2. On the Type list, select Fuzzy search.
  3. Change the default Name (FuzzySearch1) to something meaningful.
  4. Optional. Enter a Description for the action.
  5. On the Data source list, select a data source.

    A list of fields for the selected data source appears in the Mapping table.

    A Filter column appears next to the Value column in the Mappings table. You can configure filters for each column which the Fuzzy search action displays as rows.

    The Data source list only appears if the database is configured in Kofax Search and Matching Server and Transformation Designer.
  6. Specify the Number of records to return to return at runtime. (Default: 10)
  7. To use a default search text, select a Global variable, Form variable, or Form control, or click and enter a custom value in the Search default text field.
  8. In the Mapping table, configure the following columns:
    1. Select the columns you want to use in the search.
    2. To map a form field to the database field, select a field on the Value list.
    3. To specify filters for those columns that can be filtered, select a form field on the Filter list or click and provide a custom value.
      Multiple columns may have filter values if allowed by the configuration of the database.

    At runtime, the selected record appears in these form fields.

  9. Click the Display tab and configure the following properties:
    Width mode

    The width mode to be Fixed or Percentage. (Default: Percentage)

    Dialog width

    The width of the pop-up window (Default: 75% (667 px for fixed mode))

    Dialog height

    The height of the pop-up window (Default: 450 px)

    Results columns

    Displays the results in a table based on the configuration of fuzzy database.

    All the columns are selected for display (at runtime) by default.

    To configure the display name and width of the column:

    1. Select the column and click .

    2. Clear Display if you want to hide the column at runtime.

    3. Change the Display name to a user-friendly name.

    4. On the Width list, select the width for the column. (Default: 20% (100 px for fixed mode))

    5. Click OK.

    6. Click to reorder the columns to use a logical order for your search query.

  10. Click Add.

    The newly created action is added to the table.

  11. Associate the action with the control to trigger this action. See Configure actions for form control events. Alternatively, to call this action for a form event, associate the action with the form. See Associate an action with a form.

    At runtime, when this action is triggered, the fuzzy search is performed in a validation activity.

See also: