The final step in Matching, Linking, and Merging Configuration is to configure a matching event processor. For information on the other required setup steps, see the Matching, Linking, and Merging Configuration documentation here.
To deduplicate records in STEP, an event processor must be configured to trigger the matching algorithm. When invoked, this event processor creates events for matching, allowing the matching algorithm to match records. Any potential duplicates identified during matching that score between the clerical review threshold and auto threshold are placed into clerical workflow tasks. This allows users to deduplicate records manually.
For more information on the deduplication process, see the Handling Potential Duplicates documentation here.
Steps for creating an event processor include:
This section guides you to select the type of processing required (match code generate and update and/or run matching algorithm), the matching algorithm(s) if necessary, establish the schedule, set the queue status, and set the event triggering definitions.
Important: While it is possible to use the same Matching Algorithm across Event Processors, this scenario will usually result in an optimistic locking and/or unique constraint violation when the two processors conflict with one another. Optimistic locking is the implementation where objects are modified concurrently. The result of this is that the system cannot know which value should be represented. To avoid these issues, ensure that each algorithm on the system is run by a single Event Processor.
2019, Stibo Systems – Confidential