Task 2a: Creating a matching policy

You create a matching policy under and apply it to a table registered with the add-on. When creating the matching policy you tell the add-on when to execute. Users can run matching manually from a table menu, or you can specify that matching executes inline during record creation or update. When matching executes inline, a matching policy automatically executes after creating the record. If the matching operation finds potentially duplicate (suspect) records, users are notified and can review and make changes to the record.

To create a matching policy (skip to step 2 if picking up from Task 1):

1. From the main menu bar, select the Administration panel and open Data Quality & Analytics > TIBCO EBX® Match and Merge Configuration and open the table settings you want to edit.

2. Select the Matching policies tab.

   

3. Select the '+' icon to create a new matching policy and fill in the required fields on the page that displays. The image below highlights required options:

   

   1) Matching policy code	The unique code used to identify this matching policy.
   2) Active	Sets whether this matching policy is active.
   3) Execute matching	The Execute matching group allows you to set whether matching executes automatically or manually when user create or update records.

   Attention

   Note that Merge policy tells the add-on which merge policy to link to this matching policy. After creating a merge policy, you must specify it here in order to activate the automatic merge feature. See Task 4: Configuring a merge policy for instructions on creating a merge policy.

4. After saving, the pages displays two additional tabs described below:

   1. Decision tree: These settings allow you to tell the add-on how to compare data values. These settings are covered in the quick start Task 2b.

   2. Matching fields: Contains configuration settings for each field used in a matching policy.

What's Next? Use the instructions in Task 2b: Creating a decision tree to create a matching decision tree to specify how this matching policy compares data values.