Enhancement Request
The recently merged FDC3 API Metadata feature:
Has added required support for setting additional API metadata (see ContextMetadata) when making FDC3 broadcast, open, raiseIntent or raiseIntentForContext API calls and when returning an IntentResult from an IntentHandler, and receiving that metadata via handlers registered via addContextListener and addIntentListener.
FDC3 workbench already supports some limited rendering of metadata received, to support the previous optional originatingAppMetadata feature (see FDC3 2.2's ContextMetadata type). It should be updated to support the setting of all AppProvidableContextMetadata fields when making the above API calls (currently manually settable traceId and signature fields and an arbitrary custom object) and any necessary additions made to support rendering of received ContextMetadata - which was not previously supported for an IntentResult.
Enhancement Request
The recently merged FDC3 API Metadata feature:
Has added required support for setting additional API metadata (see
ContextMetadata) when making FDC3broadcast,open,raiseIntentorraiseIntentForContextAPI calls and when returning anIntentResultfrom anIntentHandler, and receiving that metadata via handlers registered viaaddContextListenerandaddIntentListener.FDC3 workbench already supports some limited rendering of metadata received, to support the previous optional
originatingAppMetadatafeature (see FDC3 2.2'sContextMetadatatype). It should be updated to support the setting of allAppProvidableContextMetadatafields when making the above API calls (currently manually settable traceId and signature fields and an arbitrarycustomobject) and any necessary additions made to support rendering of receivedContextMetadata- which was not previously supported for anIntentResult.