Release v3.0.0 - Outbound mapping support

Changes

Features

• Outbound Mapping Support: Previous release only covered a message flow that can be described as INBOUND: a json payload from an external MQTT broker is received and processed by mapping and finally send as MEAO to Cumulocity. Now the opposite message flow: OUTBOUND is supported as well. For this a MEAO in Cumulocity is transformed by an outbound mapping to a custom format and then published to the external MQTT broker on a defined topic.
• Upgrade to Cumulocity WebSDK 1016.0.128, which used Angular 14.

Fixes

• Upgrade Java library JSONata4Java to 2.2.9 to better support JSONata coverage of complex JSONata-expressions (attributes starting with _)

Breaking Changes

• All existing mappings have to be reentered/added again.

Full Changelog

v2.1.0...v3.0.0

Release v2.1.0 UX Improvements

In this release we have mainly changed the UX in the mapping UI.
It should be much more intuitive to create & update existing substitutions now.
For more details please check the documentation

We also fixed some bugs and switched to 1015 microservice SDK using API-version 2.

Release v2.0.1

v2.0.1 BugFix Release

Release v2.0

Changes

This release contains the following enhancements:

1. Feature to register a processor extension for handling binary payloads: Protobuf
2. The includes a new tab for uploading and managing processor extensions. In addition to managing extension, the mapping wizard has dropdown to choose the extension and event if a message should be processed by an extension.
3. When testing the mapping results are shown in the last wizard step.
4. Now existing mappings can be copied.
5. Migration to Cumulocity WebSDK version 1015.0.190
6. A new tab "Testing Devices" exists for test devices that are generated.
7. Sample mappings with inputs and substitutions are explained can be found in the sample document.

Fixes

1. Several bug fixes when starting & stopping the snoop process
2. Statistic on the monitor tab are persisted and reloaded after restart

v1.4_beta - Release of Dynamic MQTT Mapper

Changes

This release contains the following enhancements:

1. Feature to parse binary, flat files using a selection in a popup wizard, see documentation for details.
2. Feature to use a self-signed certificate for the connection to the broker. The connection tab was extended.
3. Feature: When the snoop process is stopped the source and target templates are initialised and a hint in th eUI is shown
4. Migration to 1015.0.172

Fixes

1. Several bug fixes when starting & stopping the snoop process
2. When a message was received with a topic name which could not be resolved, an exception was thrown and the connection to the broker was closed. Now only the statistic on the monitoring tab is updated and the exception is logged. But the connection is not closed.

v1.3_beta - Release of Dynamic MQTT Mapper

Fixes

1. Several bug fixes when starting & stopping the snoop process
2. When a message was received with a topic name which could not be resolved, an exception was thrown and the connection to the broker was closed. Now only the statistic on the monitoring tab is updated and the exception is logged. But the connection is not closed.

Changes
This release contains the following enhancements:

1. Feature to parse binary, flat files using a selection in a popup wizard, see documentation for details.
2. Feature to use a self-signed certificate for the connection to the broker. The connection tab was extended.
3. Feature: When the snoop process is stopped the source and target templates are initialised.

v1.2 - Release of Dynamic MQTT Mapper

Fixes
This release contains the following fixes for:

1. Several issues when adding, deleting and updating substitutions in the second wizard step
2. Fix for issue #20

Changes
This release contains the following enhancements:

1. Under Connectionyou can now enable/disable the logging of received payloads, to facilitate easier tracking of mapping behaviour
2. Under Mapping:
   1. You can now create a mapping as well for files in flat file format
   2. Mappings can now extract complete objects from the source payload and map these to the target
   3. The option Defines Device identifierwas removed, since this is now detected automatically
   4. The complete hierarchy of topic levels /plant1/line1/device1_measure1_Type is now added to the source payload as "_TOPIC_LEVEL_": [ "plant1", "line1", "device1_measure1_Type" ]. This allows to use any this information when resolving the external id to the intern Cumulocity [source.id]
   5. Changing rest endpoints for GET/POST of configuration for connection and service
   6. Moving buttons Snooped templates and Samples payload to the upper part of the second wizard step
   7. Adding property ``Expand Array```, see the readme doc
   8. Adding property ``Repair Strategy```, see the readme doc

v1.1 - Release of Dynamic MQTT Mapper

What's Changed

Breaking Change
In the release v1.0 we used to extract only on level of the topic names and assign this to the token _DEVICE_IDENT_.
This concept has been generalised. If you use, e.g. a topic name plant/line/device the following json attribute _TOPIC_LEVELis added to the payload:

  "_TOPIC_LEVEL_": [
    "plant",
    "line",
    "device"
  ]

The items in the array can be used, e.g. to resolve the external id to the internal Cumulocity source id.
This relates to: #13 .

The button Device Identifier is deleted for the above mentioned reasons.

Copy mappings
You can now copy an existing a mapping from the Web UI by selecting a mapping in the table of mappings.

Fixed bug
#15 : Now values for measurements are submitted correctly.

v1.0 - First Release of Dynamic MQTT Mapper

This is the first release of the Dynamic MQTT Mapper.

For the full supported features list and guidance please read the README

Microservice: mqtt-mapping-service.zip
Frontend Plugin: mqtt-mapping.zip