Fidessa

The Fidessa Tracking Groups can be mapped to the io.Connect Channels by using the channels.json Channels configuration file of io.Connect Desktop. This allows passing context between Fidessa apps and interop-enabled apps.

To map a Fidessa Tracking Group to an io.Connect Channel, use the "fidessaGroup" property of the "meta" object in the Channel definition:

{
    "name": "Red",
    "meta": {
        "color": "red",
        "fidessaGroup": {
            "index": 5,
            "readDataFieldPath": "",
            "writeDataFieldPath": ""
        }
    }
}

The "fidessaGroup" object has the following properties:

ℹ️ For more details on defining io.Connect Channels, see the io.Connect Desktop > Developers > Configuration > Channels section.

The context passed from the Fidessa Adapter to the interop-enabled apps and vice versa has the following shape:

{
    instrument: {
        // "VOD.L" or { fim: "VOD.L", bloomberg: "VOD:LN", ... }
        id: string | object;
        [prop: string] : any
    },
    client: string | object,
    order: {
        fidessaReference: string
    }
}

On how to update and subscribe for changes to a Channel context, see the io.Connect Channels API.

A Channel is updated every time the user selects an instrument, order or counterparty in a Fidessa app or in an interop-enabled app.

When an update from a Fidessa app arrives, the mapping service handles the conversion of instrument codes from FIM (Fidessa Instrument Mnemonic) to other standards (Bloomberg, Reuters Instrument Code, etc.). For instance, when a Fidessa app returns "VOD.L", the Application Adapter translates that mnemonic to other standards as well and updates the context object accordingly:

{
    instrument: {
        id: {
            bloomberg: "VOD:LN",
            fim: "VOD.L",
            ric: "VOD.L"
        }
    }
}

If there is no active mapping service, the value for the instrument.id property is the string literal received from Fidessa:

{
    instrument: {
        id: "VOD.L"
    }
}

When an interop-enabled app updates the Channel context, the Fidessa Adapter first tries to retrieve the instrument ID from the configured "fimPath" (see Connection Settings) and if no instrument ID is available there, the value of the instrument.id property is sent to the mapping service. If no mapping service is available, or if the mapping service returns an object which doesn't contain an instrument.id.fim property, the update is ignored.