Configuration

Channels

Channels Configuration

Channels are based on Shared Contexts - named objects, holding cross-application data in the form of key/value pairs. To use Channels in your Glue42 enabled app, you need to define a channels.json file in %LocalAppData%\Tick42\GlueDesktop\config. The channels.json should contain an array of objects, each one defining a different Channel.

Here is an example of minimal definition of two Channels - red and blue:

[
    {
        "name": "Red",
        "meta": {
            "color": "red"
        }
    },
    {
        "name": "Blue",
        "meta": {
            "color": "#66ABFF"
        }
    }
]

Property	Description
`name`	Required. Unique ID of the Channel.
`meta`	Required. Meta data about the Channel. The minimum you must specify here is the Channel color. You can also define other meta data which will be visible to all applications using the Channel.
`color`	The Channel color, displayed on the Channel Selector UI and on each app using that Channel. Can be either an HTML color name or a hexadecimal color code.

You can define any number of Channels in Glue42 Enterprise for your applications to use.

Here is an example of adding a custom purple Channel to an already existing list of Channels in Glue42 Enterprise:

{
    "name": "Dark Purple",
    "meta": {
        "color": "#6400b0"
    }
}

Custom Channel

Adding Channels to Your App

To add the Channel selector to your window, you need to set allowChannels to true in your application configuration file, under the details top-level key:

  {
    "title": "Client List 🔗",
    "type": "window",
    "name": "channelsclientlist",
    "icon": "https://dev-enterprise-demos.tick42.com/resources/icons/clients.ico",
    "details": {
      "url": "https://dev-enterprise-demos.tick42.com/client-list-portfolio-contact/#/clientlist",
      "mode": "tab",
      "allowChannels": true
    }
  }