2019/08/08

Connection Service

New APIs

API

Description

Replace Device

Replace the Device Key of a device without changing its asset ID (assetId)

Changed APIs

API

Description

Create Product

2 new optional parameters: dynamicActivateEnabled and productTags are supported in request body.

  • dynamicActivateEnabled: indicate whether to activate the product dynamically

  • productTags: indicate the product tags

Update Product

A new optional parameter productTags is supported in request body, which indicates the product tags

Resolved Issues

API

Description

Create Device

The parameter deviceTags in the request body was invalid

Alert Service

New APIs

API

Description

Batch Update Active Alert Tags

Batch update the tags for the specified alerts

Create Alert Rule

Create a new alert rule

Update Alert Rule

Update an alert rule

Delete Alert Rule

Delete all the rules under the organization as per the alert rule IDs

Create Alert Content

Create a new alert content

Update Alert Content

Update an alert content

Delete Alert Content

Delete an alert content

Create Alert Severity

Create a new alert severity

Update Alert Severity

Update an alert severity

Delete Alert Severity

Delete an alert severity

Create Alert Type

Create a new alert type

Update Alert Type

Update an alert type

Delete Alert Type

Delete an alert type

Create Active Alert

Create a new active alert

Delete Active Alert

Delete a specified active alert

Create History Alert

Create a new history alert

Changed APIs

API

Description

Search Active Alerts

2 optional parameters: scope and rootAlert are supported in request body.

  • scope: Query the alerts in a specified asset tree or in an asset node on the asset tree, and specify whether to return the blocked derivative alerts. This parameter cannot be applied with rootAlert. Data type is “Scope Structure”.

  • rootAlert: Query the derivative alerts which are blocked by the specified root alert. This parameter cannot be applied with scope. Data type is “RootAlert Structure”.

Search History Alerts

2 optional parameters: scope and rootAlert are supported in request body.

  • scope: Query the alerts in a specified asset tree or in an asset node on the asset tree, and specify whether to return the blocked derivative alerts. This parameter cannot be applied with rootAlert. Data type is “Scope Structure”.

  • rootAlert: Query the derivative alerts which are blocked by the specified root alert. This parameter cannot be applied with scope. Data type is “RootAlert Structure”.