2. ACCEPTED Use Cases

Once fully accepted by the working group (based on our criteria and process), use cases are moved to GitHub. To access the discussion history of a given use case prior to acceptance, please find archived accepted use cases under the Archived / Released folder.

The table below maps the implementation status of the use cases against FDC3 standards (New, Proposed, Accepted onto Roadmap of Standards, Implemented, Rejected, N/R)

Summary

Status	Count	%
New	21	75%
Proposed	5	18%
Accepted onto Roadmap of Standard	0	0%
Implemented	2	7%
Rejected	0	0%
N/R	3
Total (excl. N/R)	28	100%

Detail

Accepted Use Case	Workflows (incl. link)	Status Against 1.0 Standard	App Directory	Intent	Context data	API
Use Case 1: Equity Sell Side Trader Former user (Deleted)	W1	New
	W2	Implemented		raise intent: viewAnalysis app raises intent to listen to viewAnalysis	Passing instrument identifier
	W3	Implemented		app raises intent	passes instrument identifier
	W4	Proposed (link to Github issue)				would require further API support - within API working group e.g channel
	W5	Proposed (link to Github issue)			context is the watchlist: connected apps should listen for update to the context object	As above
Use Case 2: Buy Side Portfolio Manager Johan Sandersson	W1	N/R	Out of scope. The referenced item is a specific resource within a specific application. It's currently out of scope for AppD to handle this and instead some form of "deep linking" should be used.	Out of scope. The "intent" would be specific to the target system.	Out of scope. The "context" would be specific to the target system.	Even though the Workflow involves a mobile device and the functionality is fairly specific, it has raised questions regarding whether an FDC3 protocol handler is required to handle "deep linking" or otherwise provide FDC3 functionality to a larger set of applications.
	W2	N/R	Out of scope. The referenced item is a specific resource within a specific application. It's currently out of scope for AppD to handle this and instead some form of "deep linking" should be used.	Out of scope. The "intent" would be specific to the target system.	Out of scope. The "context" would be specific to the target system.	Even though the functionality is fairly specific, it has raised questions regarding whether an FDC3 protocol handler is required to handle "deep linking" or otherwise provide FDC3 functionality to a larger set of applications.
	W3	Proposed (link to Github issue)	Market data terminals might not want to expose 100s of supported functionalities via AppD but it's technically possible.	Use a Custom Intent to launch the research tool. Standardized Intents for "in terminal" navigation might be relevant. Intent for "sendMessage" or "startChatwithMessage" would be required to satisfy the workflow.	Needs ratified Instrument Needs ratified Contact Need standardized "message" context.
	W4	N/R	Not Applicable. Standard protocols like http should be not be handled by FDC3.	Not Applicable.	Not Applicable.	Not Applicable.
	W5	Proposed (link to Github issue)		Intent for "sendMessage" or "startChatwithMessage" would be required to satisfy the workflow. Standardized Intents for "in terminal" navigation might be relevant. Raise intent ViewChart	Needs ratified Instrument Needs ratified Contact Need standardized "message" context.	Use Find Intent to find a chat application to share and to find an application able to display a chart.
	W6	Proposed (link to Github issue)		Raise Intent ViewInstrument Raise Intent StartChat Standardized Intents for "in terminal" navigation might be relevant.	Needs ratified Instrument Needs ratified Contact	Use Find Intent to find a chat application to share and to find an application able to display a chart.
Use Case 3: In house cross platform Launcher Leslie Spiro	W1	New				X
	W2	New
	W3	New
	W4	New
	W5	New
	W6	New
	W7	New
	W8	New
Use Case 4: Client-side FX Trader Credit Check Rhyddian Olds	W1	New		X	X	X
Use Case 5: Buy side Treasurer - client rates across providers Rhyddian Olds	W1	New		X	X	X
	W2	New
	W3	New
Use Case 9: Call Transcription to CRM Tom Schady	W1	New		Raise new intent, this doesn't fit existing patterns, so not sure how to phrase. verb: store/save/log? noun: AudioTranscript, Dictation e.g. "storeAudioTranscription", "logDictation"	payload needs CRM target information
Use Case 9: Call Transcription to CRM Tom Schady	W2	New
Use Case 10: Real-Time voice trades -> trade ticket population Tom Schady	W1	New		captureTrade	payload: FIX? Security identifier Order type (buy, sell, or short) Order size Order type (e.g., market, limit, stop, etc.) Order instructions (e.g., day order, fill or kill, good-till-canceled, etc.) Order transmission (broker, ECN, ATC, etc.)
Use Case 13: User launches multiple apps from same platform in one container Former user (Deleted)	W1	New	X		X	X
	W2	New
	W3	New
Use case 15: Sales Floor Base Workflow Cesar Morgadinho	W1	New		X	X
Use case 15: Sales Floor Base Workflow Cesar Morgadinho	W2	New