How can we transfer data from A app to B app using JET in Eikon?

Best Answer
-
Re: your comment "... how can we pass a chunk of data via this method and ... read it in app B".
There are a number of examples of using JET.navigate to open different objects in the JET Demo App (you can find it under Core Functionality).
If this is a web app, then the best way to pass data/state to it would be over the URL you are calling to open it.
The most flexible way to pass additional data to the App, after it’s created, would probably be to use Pub/sub messaging on JET. The amount you can send over this is pretty unlimited, providing you use common sense chunking. You would just want to establish a private handshake between the 2 Apps once the second one was loaded. We are introducing the concept of targeting into the pub/sub APIs for JET – though this is still under development.
0
Answers
-
You can use JET.navigate to open another app programmatically, with context.
Here is an example of the mechanism you will use, to open a chart in a popup window:
var data = { target: "popup",
location: { x: 100, y: 100, width: 300, height: 300 },
name: "Graph",
entities: [{ "RIC": "GOOG.O" }]};
JET.navigate(data);And another one for a Web App/Views Explorer:
var data = { target: "popup", // open a popup window
location: { x: 100, y: 100, width: 300, height: 300 },
url: "cpurl://views.cp./Explorer/GxHOME.aspx"};
JET.navigate(data);0 -
Thanks Christiaan
Can you also let us know how can we pass a chunk of data via this method
and also would like to know how to read it in app B.0 -
Looks like we need to modify our current app to use Pub/sub messaging on JET. Before that, can we use Active Context like the below example?
JET.navigate({
name: "Eikon Explorer App",
entities: [
{ RIC: "MSFT.O" },
{ RIC: "C.N" },
{ RIC: "XON.N" },
{ RIC: "HPQ.N" }
],
url: url
});0 -
Yes, you can sent it like this:
var data = {
target: "popup",
url: "http://localhost:8888/receiver.html",
entities : [{
RIC: "MSFT.O"
}, {
RIC: "C.N"
}, {
RIC: "XON.N"
}, {
RIC: "HPQ.N"
}]
};
JET.navigate(data);And receive it like this:
JET.onContextChange(function(contextData) {
console.log(contextData);
})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
- 684 Datastream
- 1.4K DSS
- 615 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 249 ETA
- 554 WebSocket API
- 37 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 643 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
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 192 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛