Ongoing Screening Alerts Workflow ?

Hello,
Could you please confirm the following : The OGS can be enabled via API via a request and the API administrator will receive an email if any update happened telling him to check the cases for an update.
If true, I have three questions:
- What is the request I should do, via the API, to get the case that was updated ?
- is there any way to be updated via the API in addition to the sent mail ? If yes what is the request and workflow ?
Best Regards
Best Answer
-
You will have to use the API call "SEQ-6a: Enable ongoing screening for a case." in order to enable OGS for a screened case.
In order to check the case which has been updated, you need to call the API call - "SEQ-9: Monitor ongoing screening updates on cases", where you have to manually update the content of the Body before calling the API call, with the date when you have received the alert.
For example, if you have received an email update for an OGS on 28th May 2018, then you will have to edit the body of the "SEQ-9" from { "query": "updateDate>='{{weekAgo}}'" } to { "query": "updateDate>='2018-05-28'" } and then call the API to view the result. The result should display the details of the updated OGS case as on that date.
Just for calrification - Below is a sample workflow which you may follow:
Step 1: SEQ-2b: Save a very simple case
Step 2: SEQ-4a: Screen a case
Step 3: SEQ-6a: Enable ongoing screening for a case
Step 4: SEQ-8: Retrieve the audit log for a case
Step 5: SEQ-9: Monitor ongoing screening updates on cases
Hope this clarifies your concern.
0
Answers
-
You should receive email alerts for the OGS, as and when the case is updated. There is no specific API call to enable it.
- In order to check updates via email for any OGS, use the API call - "SEQ-9: Monitor ongoing screening updates on cases". You should receive email notification as and when the case has been updated.
- There is no way to be updated via API call in addition of email notification.
0 -
Hello
Thank you for your answer.
The OGS is not automatically enabled for every screened name. So you must enable it, how do you do that ?
The mail received does not contain the information on the updated case, so how do you find the right case and also all the updated cases via the Api ? What is the workflow?
Besr regards
0 -
Thanks a lot very precise answer.
0 -
Hi,
To finish the workflow:
The Json output of SEQ 9: can be
{
"caseSystemId":
"0a3687cf-5e81-1702-97a8-06050005be8c","numberOfNewResults": 6,
"numberOfUpdatedResults":
15,"updateDate": "2018-10-07T06:23:57.938Z"
},
{
"caseSystemId":
"0a3687d0-5e81-1e6e-97a8-3fb100004eba","numberOfNewResults": 0,
"numberOfUpdatedResults":
1,"updateDate": "2018-10-07T06:23:58.280Z"
},
What is the meaning of numberOfNewResults and numberOfUpdatedResults ?
By applying "SEQ-5b: Get
screening results" with the CaseSystemId we will get the ongoing screening results, right ?Best Regards
0 -
Hi,
I found the answer in the documentation:
Name
Description
Schema
caseSystemId
required
System generated ID
for the Case
string
numberOfNewResults
optional
Number of new
results added to the Case identified by caseSystemId during the ongoing
screening operation that this update belongs to.
integer(int32)
numberOfUpdatedResults
optional
Number of updates
in the existing results of the Case identified by caseSystemId found during
the ongoing screening operation that this update belongs to.
integer(int32)
updateDate
required
Creation date and
time of this ongoingScreeningUpdate in ISO 8601 format excluding Week and
Ordinal dates.
string(date-time)Best Regards
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.5K 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
- 560 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
- 281 Open PermID
- 46 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 724 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 中文论坛