Fidessa

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

Fidessa supports 7 Tracking Groups (indices 0–6), each mapped to a corresponding io.Connect Channel. The default mapping is: Red (0), Yellow (1), Orange (2), Green (3), Cyan (4), Pink (5), Blue (6). Only Channels that have a "fidessaGroup" entry in their "meta" configuration are synchronized.

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

{
    "name": "Green",
    "meta": {
        "color": "green",
        "fidessaGroup": {
            "index": 3,
            "readDataFieldPath": "market",
            "writeDataFieldPath": "market",
            "updateObject": {
                "description": "This example will alow you to verify that the update came from Fidessa",
                "lastModifiedBy": "Fidessa adapter"
            }
        }
    }
}

The "fidessaGroup" object has the following properties:

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

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

Example

Example result value in the channel context after an update of client, order and instrument, taking into account the above example configuration (with "writeDataFieldPath": "market"):

{
   "market": {
       "description": "This example will alow you to verify that the update came from Fidessa",
       "lastModifiedBy": "Fidessa adapter",
       "client": "1234567",
       "instrument": {
           "id": {
               "fim": "IN4.CA",
               "bloomberg": "IN4 CN Equity"
           }
       },
       "order": {
           "fidessaReference": "ord-id-0000123"
       }
   }
}

By default, channel context is cumulative — if you first receive an instrument update and then a client update, both fields remain in the channel data. This means an app subscribing to the channel would still see the old instrument value even though the last Fidessa action was a client selection.

To ensure the channel data always reflects only the fields sent in the most recent Fidessa update, set the standard context fields to null inside updateObject. On every update, updateObject is merged first (zeroing out those fields), and then the actual Fidessa payload is applied on top.

Example — only the field sent by Fidessa will be non-null in the channel:

{
    "name": "Green",
    "meta": {
        "color": "green",
        "fidessaGroup": {
            "index": 3,
            "updateObject": {
                "instrument": null,
                "client": null,
                "order": null,
                "instrumentList": null,
                "clientList": null,
                "orderList": null
            }
        }
    }
}

If Fidessa then sends a client update, the resulting channel data will contain only:

{
    "client": "1234567"
}

The instrument, order, and list fields will be null (effectively absent for consuming apps).

⚠️ If you do not want this reset behaviour — for example if your app needs to read all previously set fields — omit those keys from updateObject entirely. Every Fidessa update will then merge on top of whatever was already in the channel.

By default, the Fidessa Adapter writes and reads context using the standard key names: instrument, client, order, instrumentList, clientList, orderList. The "aliases" property in the "fidessaGroup" configuration allows you to rename these keys in the channel data on a per-channel basis.

This is useful when other applications on the same channel expect different property names, or when you want to avoid conflicts with context written by other adapters.

Simple Aliases

A simple string alias uses the same custom key name for both reading and writing:

{
    "name": "Green",
    "meta": {
        "color": "green",
        "fidessaGroup": {
            "index": 3,
            "aliases": {
                "instrument": "fidessaInstrument",
                "client": "fidessaClient"
            }
        }
    }
}

In this example, the adapter writes instrument data to the "fidessaInstrument" key instead of "instrument", and reads from "fidessaInstrument" when processing inbound channel updates. The same applies to "fidessaClient".

Per-Direction Aliases

For more advanced scenarios, you can specify separate key names for reading and writing using an object with "read" and "write" properties:

{
    "name": "Green",
    "meta": {
        "color": "green",
        "fidessaGroup": {
            "index": 3,
            "aliases": {
                "instrument": {
                    "read": "selectedInstrument",
                    "write": "fidessaInstrument"
                }
            }
        }
    }
}

In this example, when Fidessa sends an instrument update, the adapter writes it to the "fidessaInstrument" key in the channel. When reading from the channel, the adapter looks for the instrument value under the "selectedInstrument" key.

Alias Properties

Each key in the "aliases" object corresponds to a standard context key name. The value can be:

The supported standard key names are: "instrument", "client", "order", "instrumentList", "clientList", "orderList".

The "instrumentIdPath", "clientIdPath", and "orderIdPath" properties in the "fidessaGroup" object control how the adapter resolves context identifiers in the channel data. Each channel can specify its own paths independently.

If a path property is omitted from a channel's "fidessaGroup" configuration, the adapter uses the default value for that property ("id" for instruments and clients, "fidessaReference" for orders).

{
    "name": "Green",
    "meta": {
        "color": "green",
        "fidessaGroup": {
            "index": 3,
            "readDataFieldPath": "market",
            "writeDataFieldPath": "market",
            "instrumentIdPath": "identifier",
            "orderIdPath": "ref"
        }
    }
}

In this example, the adapter will read and write the instrument ID object at instrument.identifier instead of the default instrument.id, and the order reference at order.ref instead of the default order.fidessaReference, but only for the Green channel. The "clientIdPath" is not specified, so it uses the default "id".

You can configure a channel for one-way data flow by disabling either inbound reading or outbound writing.

Disabling Inbound Reading

Set "readDataFieldPath" to null to prevent the adapter from reading channel updates and forwarding them to Fidessa:

{
    "name": "Green",
    "meta": {
        "color": "green",
        "fidessaGroup": {
            "index": 3,
            "readDataFieldPath": null,
            "writeDataFieldPath": "market"
        }
    }
}

In this configuration, the adapter publishes Fidessa updates to the channel, but ignores any changes made to the channel by other apps.

Disabling Outbound Writing

Set "writeDataFieldPath" to null to prevent the adapter from writing Fidessa updates to the channel:

{
    "name": "Green",
    "meta": {
        "color": "green",
        "fidessaGroup": {
            "index": 3,
            "readDataFieldPath": "market",
            "writeDataFieldPath": null
        }
    }
}

In this configuration, the adapter reads channel updates and sends them to Fidessa, but does not write Fidessa updates back to the channel.

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

For details on the context data shape and how context flows between Fidessa and io.Connect apps, see Mapping Services.