No media check results after updating name
Hi, we are using WC1 API.
Here is our issue.
I have created an organization case with name 'GOOGLE' with provider as media_check
Screened the case
Now, retrieved the media results and marked all of them as reviewed
After that, I realised name should be modified to - 'AMAZON'
SO Used update API along with screening API to update the name for the same case
Now. Retrieved the media results - here no results were seen.
In the audi I could see noofnewresults is updayed but not noofresultstobereviewed value as it is still showing as zero. Shouldn't this be updated as well?
Can someone please let us know what is going on here?
Best Answer
-
Hello,
The product team has clarified that the logic around MC.
The update function is not designed to completely change the name of the case but to make a small modification to the name e.g. Adding Inc.
Once the reviewed command is run the case meta data is updated to show that all articles published up until x date are reviewed. Therefore, all articles published before the date the reviewed command was run will be marked as resolved.
When you update and re-screen that case, articles with the new name will still appear in the API and WebUI but will be marked as resolved.
For articles to show up as unresolved they need to be published the day after the reviewed command was run.
As mentioned, the update function is not designed to completely change the focus of a case but to only make minor changes.
We would be happy to assist with a way to utilise this feature more optimally in order to more effectively implement your use case. Please contact us directly if you would like to set up a consultation.
0
Answers
-
Hello @prathyu.gai thanks for reaching out! Could you please send your request body schema so that I am able to replicate the issue you are facing? Thank you!
Best,
Judith
0 -
Hello @judith.pillado01 Thank you for response. Please refer to the attached content for the APIs used along with the request body.
0 -
Hi @prathyu.gai ,
We have replicated the same flow on our side and observed same results. Furthermore, we have reported this to our product team for investigation. We will keep you posted once we receive an update on the matter.
We appreciate your cooperation while we work on this matter.
Thanks
Sai
0
Categories
- All Categories
- 6 AHS
- 37 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛