unMarkPartiesAsSuspect
- Description
- This transaction changes the
suspect status to
not duplicatefor two given suspect parties. The purpose of this transaction is to allow suspects to be unmarked (that is, status changed tonot duplicate) that have been manually marked as suspects in error. - Web Services
- Operation name: unMarkPartiesAsSuspect
- Example
- Update the suspect status between parties John Smith and John Black to 'not duplicate'.
- Usage information
- Suspected duplicates can only be 'unmarked' when the source code
on the suspect entry is 'user marked' (the value is defined in the
system properties).
The updateSuspectStatus transaction can also be executed to change the suspect to 'not duplicate'.
- Preconditions
- Suspect object must exist.
- Mandatory input
- Not applicable
- Inquiry levels
- Not applicable
- Filter values
- Not applicable
- Transaction behavior
- The source code is automatically set to 'user marked' through the markPartiesAsSuspect transaction and can be set explicitly to 'user marked' through the updateSuspectStatus transaction.
- Request message
- <TCRMTxType> unMarkPartiesAsSuspect
<TCRMTxObject> TCRMPartyListBObj
<TCRMObject> TCRMPartyListBObj containing the two parties that are no longer considered suspected duplicates
- Response objects
- TCRMPartyListBObj contains two parties, each with updated TCRMSuspectBObj business objects
- Special note
- Not applicable