How to use secondary identifiers

I am trying to use the secondaryFields parameter of the "new case" functionality.
My expectation was that if I supply a secondaryField, e.g. the Nationality for an Individual, then all profiles returned by a screening must match this field. However this seems to be not the case.
Do I have to do anything in addition to creating the case with the secondary identifiers and starting the screening?
Thanks!
Best Answer
-
Hi @andreas.kappler,
If you can execute the SEQ-1c: Get the case template for a group then able to retrieve nationality like {
"typeId": "SFCT_5",
"fieldValueType": "COUNTRY",
"regExp": null,
"fieldRequired": false,
"label": "NATIONALITY"
}So in this case example you can get typeId for nationality is SFCT_5.When you create the case add this typeid in the case body secondary fields {"typeId":"SFCT_5","value":"CHN"}.For China you can find the ISO values using SEQ-1d: Get the ISO country list.So that's how we can create the case for China.But in API you are not able to see any filter.For filtration the matching profiles value you can go to the WC1 application and in application you can able to filter for that case using screening.
Attached the screenshot for your reference.
Hope this will help.
Thanks,
Shilpi
0
Answers
-
Hi @andreas.kappler,
For finding any secondary fields for a particular Group you can Execute the SEQ-1c: Get the case template for a group.Using this seq you can able to identify the available secondary fields for that group.Once you can create any new case under this group easily you can find what are all secondary fields are available for each entity.Based on this you can add secondary fields for each entity creation of a new case.
Attached the screenshot for your reference.
Hope this will help.Let me know if you have any further queries.
Thanks,
Shilpi
0 -
Hi Shilip,
Thanks so much for your answer.
I already did what you described, but all results are still returned as matches, regardless of the secondary identifiers.
Here is how the case created over the API looks in WC One (Case Name is Siemens):
It still says 21 Matches, but only 1 unresolved? What does this mean and how can I obtain only the 1 unresolved match over the API?
0 -
Hi @andreas.kappler,
In api if you can execute the SEQ-5b: Get screening results,you are able to see the how many resultid is weak,strong and exact match.Based on this we count the no of unresolved results.If you want to resolve the case you can do via WC1 application.
Attached the screenshot where i selected one particular unresolved case and select the status and then click the button resolve.
Let me know if any further question regarding this.
Thanks,
Shilpi
0 -
Hi Shilpi,
my problem is that all profiles matching the name, regardless of secondary identifiers, are still returned by the call to cases/xxx/results
How can I filter out the profiles which do not match the secondary identifier I provided when creating the case, using the API?
Thanks!
0 -
Hi @andreas.kappler,
Can you please provide me the exact scenario what you want from API.May be based on this I will help you further.
Thanks,
Shilpi
0 -
I want to decrease the number of results of a screening by adding secondary identifiers.
So for example if there are 100 matching profiles for a given name, but only 10 of the profiles are Chinese citizens, then I want to get those 10 matching profiles by adding "China" as a secondary identifier for the field "nationality".
0 -
I am also interested in this as well. We have a similar request from a client that they only want cases matching the secondary identifiers passed to the API back from the results. This is possible to do in the web interface but the API does not seem to be respecting the interface setting to exclude false matches from being returned from the API.
0
Categories
- All Categories
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 684 Datastream
- 1.4K DSS
- 613 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 248 ETA
- 552 WebSocket API
- 37 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 629 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 191 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 86 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛