"cases/{<!-- -->{case-system-id}}/screeningRequest" is not updating case results when called agai...

...n after case update request
Hi Team,
When we are updating a case and performing caseScreening again it is not updating the results in World-Check One application. There are only old matched profiles in World-Check One application.
Does the caseScreeing adds the new results to old one? If it is true then may be there are no new profiles for recent update. Thats why showing old results only. Is it possible to check what was the result for recent screening in World-Check One application?
In our application after updating case, we are performing caseScreeing and then sending email if match found. The issue is, all emails contain old result values even after case has been updated.
Please help.
NOTE - We are working on Pilot environment right now
Best Answer
-
Thank you for the requested details.
Kindly note that you are unable to view any of the matches for the name "PACQUIAO MARQUEZ" in your updated case, is because that the name "PACQUIAO MARQUEZ" does not generate any screening results. This is why you are able to see only the old results related to the name "SALMAN KHAN".
The key here is to understand that when the case is updated with a new name, the old results are retained in the new result set along with the new results. In this case, there were no new results, so the screening result API is showing only the old result set.
I just screened the name "PACQUIAO MARQUEZ" as a new case and do not find any results for it.
Request you to replicate this using a different name, which is common and which is bound to generate results when it is screened and you will see them in the result set.
Thanks.
0
Answers
-
Can you please post the original request (including the payloads), the updated request and their respective results here ??
Regards,
Mehran Khan
0 -
@Mehran.Ahmed Khan thank you for the response.
Please find below our original request
<caseId>OM000081280</caseId><entityType>INDIVIDUAL</entityType><groupId /><name>SALMAN KHAN</name><secondaryFields><typeId>SFCT_2</typeId><value></value><dateTimeValue>1965-12-27</dateTimeValue></secondaryFields><secondaryFields><typeId>SFCT_5</typeId><value>IND</value><dateTimeValue></dateTimeValue></secondaryFields><providerTypes>WATCHLIST</providerTypes>
then we updated the case with name PACQUIAO MARQUEZ and screened case again but results are not updated in world check application.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 690 Datastream
- 1.4K DSS
- 629 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 559 WebSocket API
- 39 FX Venues
- 15 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 25 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 280 Open PermID
- 45 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 717 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
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 106 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 95 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛