FDC3 in AdapTable
Summary
- AdapTable provides powerful FDC3 functionality - with full support for FDC3 2.1
- All FDC3 Intents and Contexts can be raised, broadcast and listened to as required
- Custom FDC3 is also fully supported
Understanding FDC3
AdapTable provides full and comprehensive support for FDC3 - the Open Standard for the financial desktop.
The mission of the Financial Desktop Connectivity and Collaboration Consortium (FDC3) is to develop specific protocols and taxonomies to advance the ability of desktop applications in financial workflows to interoperate in a plug-and-play fashion, without prior bi-lateral agreements.
FDC3 provides an open standard for interoperability between applications on the financial desktop.
End-users of AdapTable are able to access FDC3 in a number of ways including:
- raise, and listen for, FDC3 Intents
- broadcast, and listen for, FDC3 Contexts
- use Custom Intents and Contexts
Important
In Version 19, AdapTable provided full support for FDC3 2.1 - a major re-write of the FDC3 standard
How it Works
FDC3 support in AdapTable is provided at design-time by developers using FDC3 Options.
AdapTable's FDC3 configuration is managed via a 2 step-process:
- provide FDC3 data mappings - essentially mapping formal FDC3 types against AdapTable Columns
- use these mappings to raise and listen for Intents, and broadcast and listen for Contexts
Note
- Most AdapTable users who access FDC3, also use a FDC3-supporting platform like OpenFin, interop.io or Connectifi
- AdapTable provides a plugin for each container which automatically connects to the FDC3 implementation
- For instance, AdapTable will wire up its FDC3 Broadcasts and Intents and publish them on a shared channel
Hint
- It is possible to use FDC3 in AdapTable natively without using the containers listed above
- FDC3 provides a powerful way of communicating between multiple AdapTable instances
Grid Data Mappings
AdapTable's FDC3 support is data-centric.
Grid Data Mappings provide the "glue" to map the Grid's data and columns to FDC3 behaviour.
Essentially they tell AdapTable which columns in the Grid to use when creating Intents and Contexts.
Mappings are provided in the gridDataContextMapping property of FDC3 Options.
ֵEach entry has a key of a formal FDC3 type and an associated mapping to existing Grid Columns.
Find Out More
See FDC3 Grid Data Mappings for full details
Intents
Intents are FDC3 actions that a user wants to perform or react to.
According to the official FDC3 Documentation:
FDC3 Intents define a standard set of verbs that, in conjunction with context data acting as nouns, can be used to put together common cross-application workflows on the financial desktop.
AdapTable supports Intents through the intents property in FDC3 Options.
This contains 2 properties:
-
raises- provides a list of FDC3 Intents which can be raisedNote
Intents can be raised either via a Context Menu item or by creating an Action Column Button
-
listensFor- lists the FDC3 Intents to which the Grid will listenHint
Intents are listened to by implementing the
handleIntentproperty function - also in FDC3 Options
Find Out More
See FDC3 Intents for the full, official specification
Contexts
If Intents are the verbs that define actions, then Contexts are the accompanying nouns.
According to the official FDC3 Documentation:
FDC3 Context Data defines a standard for passing common identifiers and data between apps to create a seamless workflow....Context objects are used when raising intents and when broadcasting context to other applications.
AdapTable supports FDC3 Contexts through the contexts property in FDC3 Options.
This contains 2 properties:
-
broadcasts- publishes information about a given FDC3 ContextNote
Context can be broadcast either via a Context Menu item or by creating an Action Column Button
-
listensFor- lists the FDC3 Contexts to which the Grid will listenHint
Context is listened to by implementing the
handleContextproperty function - also in FDC3 Options
Find Out More
See FDC3 Contexts for the full, official specification
Custom FDC3
Typically users will want to raise intents and broadcast contexts which are officially provided by FDC3.
However AdapTable also supports Custom FDC3 context and intents.
This can be used to communicate between multiple AdapTable instances or between AdapTable and other applications in your workflow.
Find Out More
See Providing Custom FDC3 for full details
FDC3 UI Components
Developers are easily able to configure the AdapTable UI to perform FDC3-related actions.
FDC3 Action Columns
This is primarily achieved through FDC3 Action Columns.
These are normal Action Columns (used widely in AdapTable) which are leveraged for FDC3 purposes.
These dynamically created Columns will display buttons used for Raising Intents or Broadcasting Contexts.
FDC3 Action Columns can be provided in 2 ways:
-
By providing Action Buttons - which AdapTable will then display in the default FDC3 Action Column
-
By providing a custom FDC3 Action Column - which AdapTable will render as required
Caution
Both types of Column need to be directly referenced in any Layouts you provide
The Buttons and Action Columns are defined inside whichever Intents and / or Contexts they reference.
FDC3 Context Menu Items
Another way to use the AdapTable UI to perform FDC3 activity is through Context Menu Items.
Note
These can used to raise Intents or to broadcast Context.
Developers provided the menu configuration details in FDC3 Options, and AdapTable will wire up the menu items automatically.
Find Out More
See FDC3 UI Components for full details
FDC3 Message Event
AdapTable fires the FDC3 Message Event whenever an FDC3 Message is sent or received.
UI Entitlements
The UI Entitlements behaviour for FDC3 is that ReadOnly and Full Access Levels are identical (since everything is provided at design-time).