The Rules Engine allows the creation of different Actions to manage data flows. As part of the first Release, a limited amount of Actions are available which can be activated and take effect for the whole Customer Organization. Each Action is listed in the Rules Engine and shows the Current Status. A new Action can be added by clicking the “Create” button on the Page:
The menu for creating new Rules is opening and the desired action can be selected. Depending on the Action different Settings are shown.
Currently, we support the following rule types:
AWS IoT Core Bridge
Creates bridge to forward messages to specified AWS Account IoT Core MQTT Topic.
Creates new Translation Template for binary payload translation.
The Rules Engine will get more active over time in order to support various processing steps for the data and be able to integrate into further Cloud Platforms as well as SaaS Solutions.
In the example below an AWS Account need to be selected in order to create a new bridge:
The AWS Accounts first need to be successfully added and connected in the Account Connection Page to be available for selection.
The page also contains the checkbox "Bridge Payload in JSON Format", which specifies if the payload for this bridge should be forwarded in JSON format or in String format.
JSON should be in a format as described in https://www.json.org/json-en.html. "null" values are being ignored, nested structures and arrays are being supported.
In the screenshot below you can see an example of both formats:
In the example below is shown Translation Template creation form, where you can enter a name for a new Template, put the template itself in JSON format, and select protocols to which Template should be applied:
If the rule should be updated, it can be done by clicking on the necessary rule, which should open a side window with details of the selected rule, where details can be updated and saved.
Each Action can be deleted if it is not necessary anymore:
Updated 29 days ago