Dynamic Mapper Release 6.2.0

News Open-Source news
, , ,
1

We just released 6.2.0 of Dynamic Mapper:

It contains a lot of feedback worked in from customers. We especially focused on SmartFunction and Java Extension, as you can see from the following list:

Features & Enhancements

  • UI for cache statistics #432

image
image1568Ă—671 52.4 KB

  • Configuration for Java Extension; this is useful for extensions that require some adaptation or configuration during mapping definition (SparkplugB).

image
image2176Ă—1257 221 KB

  • SmartFunction and Java Extension reference deviceParents/assetParents in order to send measurements to their parents #434
  • Add new samples for SmartFunction and Java Extension, including SparkplugB
  • Categorize service configuration in the UI to improve UX; previously, it was a long list of settings.

image
image1542Ă—701 83.7 KB

  • Add MQTT clientId to context for SmartFunction and Java Extension #438
  • Add a unified editor view when updating existing mappings instead of a stepper.

image
image1304Ă—871 102 KB

  • TypeScript definition for SmartFunction #440
  • Complete cycle to test transformations in the UI & sending test messages for inbound/outbound
  • Show a dialog to inform users about the upcoming deprecation of the transformation type Substitution as JavaScript
  • A new FAQ as part of the documentation #436

Bug Fixes & Code Quality & Maintenance

  • Filtering in the table of all subscriptions is not working #430
  • Report errors when loading mappings that have a deprecated or invalid JSON schema #431
  • The request API is not taken into account for inbound Smart Functions; instead, the mapping.getTargetAPI() is used. #433
  • Failed to retrieve mappings due to NullPointerException #435
  • Correctly setting the owner of devices #441
  • Extension Mappings could be created without selecting an extension #446
  • Shared code section is reset when invoking action “Init system code templates” #447
  • URL Parameters in WebHook Connector should be placed at the end of the URL #450
  • Outbound OPERATION mapping stays in PENDING when Smart Function throws a JavaScript error #451
  • Outbound Notification 2.0 subscriptions managed by UpdateSubscriptionDeviceGroupTask stop receiving messages after microservice restart #452
  • Order of execution of shared + mapping code fixed #458

Let AI agents work for you

Still, we are supporting AI-generated mappings for all kind of types, also for SmartFunctions which we also slightly improved. The agent might not be perfect (yet) but creates especially for simple payloads very usable mappings to get you quickly started without providing much, just the (snooped) source payload

image
image1543Ă—1420 232 KB

Outlook

In future releases, we will deprecate the “old” code mappings, which were substitution-based, in favor of replacing them with the new SmartFunction code mappings.
We will also investigate how we can add a better module approach for libs added to shared code and used in mapping code.

1 Like