Adding Live telepo data widgets to portal Dashboard

IMPORTANT NOTE: The information below is useful for setting up the LEGACY type of live widgets.
For the current Live Wallboard type setup, see https://destinygroup.atlassian.net/wiki/spaces/DA/pages/1635254291/Enabling+Live+Wallboard+D4SP+Core+Live

Requirements

Meridix Platform - v. 3.9.15.5288 or later

Meridix MiCloud Telepo Wallboard - v. x.x.1020 or later

Add external widget manifest route to Meridix portal

Locate the folder config under the root folder where the portal is installed
If the file external-widgets.json does not exist remove dist from external-widgets.dist.json and then modify that file

Add the following JSON object to the array list

external-widgets.json

[
	{
		"name": "Telepo live widget",
		"enabled": "true",
		"clientId": "UniqueIdOfStudio", // Exchange to for as an example partnerNameMeridixStudioxxx
		"enabledPropertyKey": "telepo_live.widgets_enabled",
		"externalEndpointBaseAddress": "UrlToMeridixMiCloudTelepoWallboard", // Exchange with correct url
		"externalEndpointServerSideBaseAddress": "UrlToMeridixMiCloudTelepoWallboard", // Exchange with correct url
		"manifestPath": "/api/externalwidgets/manifest",
		"manifestPathVerb": "POST",
		"endpointRequiredProperties": [
			{
				"propertyKey": "micloud.baseUrl",
				"defaultValue": "customerTelepoBaseUrl" // Can be omitted if the customer domain is configured in the wallboard installation 
			},
			{
				"propertyKey": "micloud.domain",
				"defaultValue": "test.com" // Will show test data when this property is not set
			},
			{
				"propertyKey": "micloud.username",
				"defaultValue": "testusername" 
			},
			{
				"propertyKey": "micloud.token",
				"defaultValue": "testtoken" 
			}
		]
	}
]

You can change the enabled Property key-value "telepo_live.widgets_enabled" in the JSON object to any name Ex. "Telepo_live.Meridix_Sweden_enabled" but it must be added exactly the same value to customer properties in Meridix studio.
The key "externalEndpointBaseAddress" must have the value to the external source has the live information Ex. "externalEndpointBaseAddress": "https://telepowallboard.meridix.se"

The properties micloud.baseUrl, micloud.domain, micloud.username, micloud.token may be added either in the config file external-widgets.json or under properties for a specific customer/user in the web portal.

To add it in the config file see step 3 above.

To add it under customer/user see steps below.

Add ability to load configured wallboards into the Dashboard

Add the following block in the external-widgets.json file

Wallboard configurations into Dashboard

{
		"name": "Meridix MiCloud Wallboard Configured wallboards",
		"enabled": "false",
		"clientId": "UniqueIdOfStudio", // Exchange to same as above
		"enabledPropertyKey": "micloud_wallboard_widgets.enabled",
		"externalEndpointBaseAddress": "UrlToMeridixMiCloudTelepoWallboard", // Exchange with correct url
		"externalEndpointServerSideBaseAddress": "UrlToMeridixMiCloudTelepoWallboard", // Exchange with correct url
		"manifestPath": "/api/externalwidgets/manifest/wallboards",
		"manifestPathVerb": "POST",
		"endpointRequiredProperties": [
			{
				"propertyKey": "micloud.baseUrl",
				"defaultValue": "meridix.com" 
			},
			{
				"propertyKey": "micloud.domain",
				"defaultValue": "meridix.com" 
			},
			{
				"propertyKey": "micloud.username",
				"defaultValue": "testusername" 
			},
			{
				"propertyKey": "micloud.token",
				"defaultValue": "testtoken" 
			}
		]
	},