Handling status with UPA
If I post a request for an item using UPA and I get a RSSL_MC_REFRESH message with an associated RSSL_DATA_SUSPECT dataState, if the item later recovers I assume that I will get a RSSL_MC_STATUS message with an RSSL_DATA_OK dataState.
Will the code of that message be RSSL_SC_NONE ?
I've checked in the Dev guide but I can't find this case referred to explicitly.
Best Answer
-
It's okay to look at the state code but the stream state and data state are what tell you the status of your request. Stream state of RSSL_STREAM_CLOSED/CLOSED_RECOVER and data state of RSSL_DATA_SUSPECT tell you that your request is rejected. The state code is just extra information.
0
Answers
-
This will generally be the case, however the status code may vary based on the content provider so it is not advised you code specific behaviors around that. Behavior should be driven mainly by stream and data states. Appendix A in the UPA/ETA Developers Guide walks through typical application behaviors driven by each stream & data state combination, both for item status and group status.
Hope this helps!
0 -
Thank's for that. Re the code, my app needs to know if the symbol we're requesting exists and if we're entitled to it. We have to drive behaviour based on that. We currently use the code field to check this i.e. we check for RSSL_SC_NOT_ENTITLED, RSSL_SC_NOT_FOUND values. It sounds like that isn't recommended. But from when I read in the Dev guide I can't see any other way of checking those conditions.
0 -
I understand the point about the state being the vital information. It's just that on our platform it's important to distinguish between a symbol not existing and not being permissioned and we have to use the code for that information. So even though it's recommended in the Dev guide to not use the code to drive behaviour, in this case we have to.
0
Categories
- All Categories
- 6 AHS
- 39 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
- 60 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛