Regarding Watchlist:

I am sorry to break this to you but you will have to seek update about this on the support case you raised with Refinitiv.

Regarding Resolution:

Please find my answers below;

• In both cases ("auto resolve as FALSE" & "remove from result") this setting ONLY applies on the matching of the secondary identifier values.----Yes
  So this has no impact on the "name" value matching?----Yes
• A "mismatching" is detected when:
  The provided value is not equal to the WC DB value and can be configured using the "Manage the outcome of auto resolution" matrix?----Yes
  When the secondary identifier is checked, for a particular source, and a value mismatching is detected it will auto-resolve that match (to False or Remove). Correct?----Yes
• "auto resolve as FALSE" : only usable in UI because this resolution-value is not exposed in API result.----No. We expose this information in the endpoint "SEQ-case-investigate-results: Get screening results". So with each match you will have resolution values for them too which would tell if a particular match is auto resolved. In version 2 of the API, this information will be available in the endpoint "SEQ-screen-sync-simple: Perform Synchronous Screening" too.
• But "remove from result" : that result is totally removed and so also removed from the API screening result?----Yes
• Can you provide me some additional info regarding the "Resolution Toolkit", how this plays a role in all this?----Yes. So any match that is auto resolved due to mismatch of the secondary identifier will have the resolution state marked as "False" while "Reason" state will be NULL/Blank and "Risk" state will also be NULL/Blank. This is how you can identify if the case was auto resolved. Please check the screenshot.

Thanks.

Exposing of resolution attribute is not available in the JSON of version 1 sync screening endpoint. But this will be available in version 2 of this endpoint.

Filtering of the results on the basis of strength can be controlled from the admin UI of the WC1 account. So if you set the match strength as "STRONG" in your UI settings, you will only be returned only STRONG and EXACT matches, other results with lesser strength will be discarded.

Yes, in the value of sources- only last part of the string corresponds to World Check Keyword Abbreviation list. But what we display in the value is the complete unique indentifer of that source that can be tracked in the API call "SEQ-pre-source-providers: Get the list of source providers".

If you call the API call "SEQ-pre-source-providers: Get the list of source providers", you would be able to track that source by searching the complete string "b_trwc_RUPGO".

If you check the JSON of the API call "SEQ-pre-source-providers: Get the list of source providers". You would the first few lines as:

{
        "identifier": "cnp_7",
        "code": "trwc",
        "name": "World Check",
        "master": true,
        "sources": [

So to answer your questions, in the string "b_trwc_RUPGO"- trwc means the code appended to the keyword list abbreviation to make it more unique.

Thank you for the helpful response.

When I want to modify the "Name match threshold" on the "WATCHLIST SETTINGS" following message is returned:

"You are disabling all sources. Users will not be able to see results from World-Check screening. Do you really want to proceed?"

Using the threshold on the World-Check setting is working fine.

Coming back to the "resolution" function.

Based on info I received through refinitiv customer support, this functionality auto resolves matches as FALSE. but this can also be configured as "Remove from results".

• How do we need to understand this "resolution" functionality ?
• And is this "resolution" setting affecting the actual results returned ?

Thanks in advance.

Thank you for the clarification.

Can you please provide me a screenshot of the "WATCHLIST SETTINGS" that gives you the mentioned notification?

This notification is shown when you are trying to deselect all the source providers from your settings.

Regarding resolution, I understand now that you are talking about the UI resolution settings.So the answer for that is below:

If you use the choose the "auto resolve" functionality, this will not reduce the number of matches/results. But this will simply auto resolve the matches/results that has a mismatch in terms of secondary identifiers (like gender, DOB, Place of Birth, etc- any one of the secondary identifier mismatching with the WC DB match will render the match as auto resolved) but will be included in the result set. Hence no reduction in the number of match count.

If you choose the option "remove from result", this will remove all the results that has been auto resolved due to mismatch of the secondary identifier and this will lead to lesser results/matches in your case.

Regarding WATCHLIST SETTINGS:

When changing the "Name match threshold" in these settings, following message is returned:

Only changed the threshold and all sources are still checked.

Regarding RESOLUTION:

• In both cases ("auto resolve as FALSE" & "remove from result") this setting ONLY applies on the matching of the secondary identifier values.
  So this has no impact on the "name" value matching?
• A "mismatching" is detected when:
  The provided value is not equal to the WC DB value and can be configured using the "Manage the outcome of auto resolution" matrix?
  When the secondary identifier is checked, for a particular source, and a value mismatching is detected it will auto-resolve that match (to False or Remove). Correct?
• "auto resolve as FALSE" : only usable in UI because this resolution-value is not exposed in API result.
• But "remove from result" : that result is totally removed and so also removed from the API screening result?
• Can you provide me some additional info regarding the "Resolution Toolkit", how this plays a role in all this?