The EDQ Siebel Integration describes the GUI usage of the EDQ Siebel Connector. Thanks to the answers in this forum I've been able to nearly complete the setup of my duplicate check demo system for the GUI.
Now, I'm getting to the interface part. Are there any recommended approaches regarding the integration of interfaces?
An external system sends a contact update into Siebel. We want to prevent duplicates from entering the database.
An external system sends a new account into Siebel. We want to prevent duplicates from entering the database.
I can imagine ways like
The counterpart of the interface performs a duplicate check request against EDQ before inserting a record into Siebel, considering the match value
Siebel itself could be configured to initiate a request against EDQ for each new / updated record approaching the Siebel system via an interface
Would there be any way to make use of the EDQ Siebel Connector functionalities for the second proposal?
The DQ interfaces in Siebel can easily be enabled at all points of record entry, and share the same attribute mappings etc. Once set up, you simply enable DeDuplication and Cleansing on the right business objects, e.g. the EAI layer.