Desktop interoperability
FDC3 is an open standard that enables financial applications to interoperate and exchange data with each other. Applications can launch each other, respond to activity in other apps and request functionality from each other.
The aim is to give users a more joined-up experience for workflows that require multiple apps. They can just click through the workflow without the need to start and stop apps or copy and paste data manually.
These pages contain an overview for working with the FDC3 protocol, using both Interop.io and Openfin - now called Here.
- FDC3 Channel Event
- A utility element that listens to events and broadcasts them on FDC3 channels
- Can send events on system color channels or app channels
- Allows mapping of event payloads before broadcasting
- Key attributes include
event-name
,channel-type
, andchannel-name
- FDC3 Context Channel Listener
- Listens to FDC3 app channels for specified contexts
- Configurable to handle different context types and provide callbacks
- Useful for listening to and handling events on app channels
- FDC3 System Channel Listener
- Similar to context channel listener but specifically for system/color channels
- Listens for specified context types on system channels
- Provides callback handling for system channel events
- FDC3 Intent Listener
- Handles intents raised against an application in FDC3 workspace
- Configurable for different intent types and handlers
- Notification Listeners (Openfin & Interop.io)
- Components for displaying notifications in respective platforms
- Can be configured with custom buttons and actions
- Link notifications to platform-specific notification panels
The documentation also includes a Foundation FDC3 overview describing:
- Core FDC3 standard implementation
- API for intents, context sharing and channels
- Installation and configuration guidance
- Usage examples for common scenarios
- Best practices for implementation
All components are designed to work with Genesis, React and Angular frameworks. Each page in this section includes a link to the relevant detailed API documentation to enable you to implement this.