Comments (6)
OK I'll be first to reply to my own question then....
Intent: ViewParent
Use Case: A trade has been queried in an Execution Management System. In order to see more details about the parent order, the user selects ViewParent(Trade) and selects the Order Management system to view the parent order
from fdc3.
Another for consideration:
Intent: ViewChildren
Use Case 1: A user wants to check if a transaction is part of their position. They select ViewChildren(Position) and select the Position Transactions application to view the underlying trades
Use Case 2: A user is considering selling part of a position and wishes to view the tax lots within that position. The user selects ViewChildren(Position) and selects the Tax Lot application to view their breakdown
from fdc3.
I think this is quite buy-sidey but still...
Intent: ModelTrade
Use Case: A portfolio manager wishes to sell out of a position in a security whose rating has dropped and buy into a different one. They select ModelTrade(Position) and select their Switch Calculator application to start modelling the trade.
from fdc3.
Intent: ViewAnalysis, ViewChart, ViewQuote
Use Case: A trader selects an order in their order management system, and wants to see analytics in an application from a broker or other external vendor to help them decide the best way to trade the order. This could be liquidity information, relevant charts, current pricing data, or other information depending on the application. There are cases where additional fields are required besides the Instrument, like side, quantity, and settle date.
Note that any actual order execution instructions would still be done via FIX, so we don't need to include every order detail in the FDC3 context.
from fdc3.
@dominicgifford I think ViewOrder(s)[Order/Trade/Position/Instrument/Portfolio] / ViewTrade(s)[Order/Trade/Position/Instrument/Portfolio] might be more straightforward? The use cases (particularly Use Case 1) look sound to me though. Potentially StartTradeModel for naming?
@timjenkel ViewAnalysis is one we're keen for - specifically for Trade/Order (pre-trade / in-flight analytics). You could potentially include Position here as well as you may want to view risk associated with a particular position?
Intent: StartOrder
Use Case: A portfolio manager has modelled a trade they want made in their Switch Calculator application, they select StartOrder and their Order Management System application which presents a partially pre-filled Order ticket.
Intent: StartTrade
Use Case: A trader has shared details of an order they are working with a Pre-trade Analytics application (through ViewAnalaysis) and the application has provided recommendations on how to trade the Order which the trader wants to action. They select StartTrade and their Execution Management System application which presents a partially pre-filled Trade ticket (I'm thinking things like strategy / schedule here).
from fdc3.
@nemery-flextrade - agree, those Intents make more sense and are less generic.
from fdc3.
Related Issues (20)
- Adding Event Listeners on Private Channel HOT 1
- Inconsistent Use of Promises HOT 6
- Bug or Inconsistency? HOT 1
- Question: AddContextListenerResponsePayload does not contain channelId HOT 2
- FDC3 monorepo HOT 2
- Use Cases and Workflows Discussion Group - 1st August 2024 HOT 5
- Make Listener.unsubscribe() async for consistency HOT 7
- Simplify Web Connection Protocol HOT 7
- IFramePositioning HOT 12
- RaiseIntentResultResponse HOT 5
- Question: resolvers / channel selectors UI HOT 5
- Spelling Error: FindIntentsByContextsResponse HOT 1
- broadcastEvent on no channel HOT 7
- Adding Channel State For JoinUserChannel / AddContextListener HOT 1
- Question: IntentEvent has no targetApp property HOT 3
- Question: How does DesktopAgentProxy remove event listener? HOT 3
- window.origin Requirement HOT 2
- Standard WG Meeting - August 22nd, 2024 HOT 8
- Add .NET docs for Events to API reference HOT 1
- GetAgentParams Not Optional HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from fdc3.