Map WC1 API and case manager using WC1 UI
Hello.
I need to get same value from the World-Check-API as is displayed in the World-Check-One UI.
My mappng primarily focuses on the World-Check-One UI.
Could you please review my mapping and indicate where I may be mistaken?
- In case manager list
Mandatory Actions: `World-Check-Summary Unresolved` + `World-Check-Summary Review Required`
World-Check-Summary Unresolved: call `GET cases/{
{case-system-id}}?aggregatedSummary=true` and count `.aggregatedResultSummaries.watchlist.categorisedMatches.watchlistUnresolved` in the Response.
World-Check-Summary Review Required: call `GET cases/{
{case-system-id}}?aggregatedSummary=true` and count `.aggregatedResultSummaries.watchlist.watchlistReviewRequired` in the Response.
Ongoing Screening: call `GET cases/{
{case-system-id}}` and if `.caseScreeningState.WATCHLIST`in the Response is `ONGOING`, it's displayed TRUE.
Archived: call `GET cases/{
{case-system-id}}` and if '.lifecycleState` is `ARCHIVED` then TRUE, if `UNARCHIVED` then FALSE.
Create Date: call `GET cases/{
{case-system-id}}` and get `.creationDate` in the Response.
Last Screened Date: call `GET cases/{
{case-system-id}}` and get `.lastScreenedDatesByProviderType.["WATCHLIST"]` in the Response.
- In WORLD-CHECK ( right list)
UNRESOLVED: call `GET cases/{
{case-system-id}}?aggregatedSummary=true` and count data of `.aggregatedResultSummaries.watchlist.categorisedMatches.watchlistUnresolved` in the Response.
Positive: call `GET cases/{
{case-system-id}}/results`, get `[].resolution.statusId` in the Response and Multiple screening results can be obtained through 'results'. Count the number of cases that match the 'statusId' (indicate `Positive`).
Possible: call `GET cases/{
{case-system-id}}/results`, get `[].resolution.statusId` in the Response and Multiple screening results can be obtained through 'results'. Count the number of cases that match the 'statusId' (indicate `Possible`).
False: call `GET cases/{
{case-system-id}}/results`, get `[].resolution.statusId` in the Response and Multiple screening results can be obtained through 'results'. Count the number of cases that match the 'statusId' (indicate `False`).
Unspecified: call `GET cases/{
{case-system-id}}/results`, get `[].resolution.statusId` in the Response and Multiple screening results can be obtained through 'results'. Count the number of cases that match the 'statusId' (indicate `Unspecified`).
- In CURRENT STATUS ( in WORLD-CHECK)
This area includes fields such as Resolution Status
, Risk Level
, Resolution Remark
, Review Comment
, and Last Updated
. However, I only need the Risk Level
.
Risk Level: call `GET cases/{
{case-system-id}}/results`and get `[].resolution.riskId` int the Response.
Thanks.
Best Answer
-
Hi @satom ,
The above understanding/mapping of the API response values are correct to achieve the same as displayed in UI.
However, please find below comments on your understanding for two of the filed values.
- Ongoing Screening: call `GET cases/{ {case-system-id}}`if you have set the case to OGS for WATCHLIST the caseScreeningState of WATCHLIST will show as ONGOING as below.
- Archived: call `GET cases/{ {case-system-id}}` and if the case is archived the value of lifeCycleState will be set to ARCHIVED, if the case is not archived the value will be set to UNARCHIVED.
Thanks
1
Answers
-
Hi @satom ,
Thanks for reaching out to us!
Please allow us to verify the above details, will get back to you asap.
Thanks
1 -
Hi @anisetti.saikiranreddy01 ,
Thanks for your prompt replay! I appreciate your assistance and look forward to your update.
Thanks0 -
Hello @anisetti.saikiranreddy01,
Upon further reflection, the previous message might have been incorrect.
> World-Check-Summary Unresolved: call `GET cases/{ {case-system-id}}?aggregatedSummary=true` and count `.aggregatedResultSummaries.watchlist.categorisedMatches.watchlistReviewRequiredBySubCategory` in the Response.
However, it should likely be as follows, right?
World-Check-Summary Unresolved: call `GET cases/{ {case-system-id}}?aggregatedSummary=true` and count `.aggregatedResultSummaries.watchlist.categorisedMatches.watchlistUnresolved` in the Response.
And, this message might have been incorrect either.
> UNRESOLVED: call `GET cases/{ {case-system-id}}?aggregatedSummary=true` and count data of `.aggregatedResultSummaries.watchlist.categorisedMatches.watchlistReviewRequiredBySubCategory` in the Response.
Thanks.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 中文论坛