New Features in Cloud Connector, Flow Creator and more

New Features

Cloud Connector

• App is enabled to support multiple root CA certificates so that certificate migration from Azure does not disrupt connectivity to the Azure cloud.
• Apps are renamed to "Cloud Connector" and "Cloud Connector Configurator*.
• Cloud Connector Configurator supported with OpenShift IEM environment.
• Upgraded IE payload format to fix missing timestamps in data payload.

Connector for Azure

• App is enabled to support multiple root CA certificates so that the certificate migration activity from Azure would not cause Any disruptions with connectivity to Azure Cloud.
• Cloud Connector Configurator supported with OpenShift IEM environment.
• Upgraded IE payload format to fix missing timestamps in data payload.

Flow Creator

• Flow Creator(arm64) provides low coding data flow development environment for ARM64 devices to enable your IOT use cases such as analytics, data transfer from shopfloor to cloud and many more.​
• App provides a browser-based data flow editor that makes it easy to wire together data flows using the wide range of nodes in the palette.​
• Small footprint and resource consumption to run smooth on your ARM device.​
• This app also works with a configurator app in IEM (Flow Creator Configurator) which can be used optionally to mass configure this app (flows, custom files and node installation) in multiple devices from the IE Management​

Industrial Edge Device Kit

• API Access (Graceful Shutdown of Device) - Valuable for app developers, who now can write apps that get notified in case of power loss and can acknowledge the shutdown once all critical data is saved.​

IECTL

• Command added to see the list of available device types on IEM.

IE Hub

• App providers can upload oss_readme, oss and app binary up to 20 GB each per version.

IEM installed components version (Helm Chart)

You can now:

• Providing a report in the log package.
• Collecting IEM type, version, and host address.
• Collecting IEM Apps and catalog Apps info.
• Collecting onboarded IED info.
• Collecting IEDK and IED-OS info.

DeviceTwin

DeviceTwin is a backend service for IEM and IED communication. It is lightweight, flexible, and extensible.

• This is phase 1 work: syncing IED data to IEM.
• With the use case: IED capability syncing to IEM.

EdgeEye MetricsAgent

• Given an overview page for all configurations.
• Provide detailed error messages inside of each configuration.
• Put the forwarding switch on the home page.

IE State Service

Multiple backups per device:

• Enablement of functionality to secure more than one backup per device​
• Backups with different states can be secured (e.g. with or without app volume data)​
• Flexibility to decide which backup state is used for restoring a device​
• Securing multiple state per device mitigates the risk of losing all data if a single backup is corrupted​
  Display of device name:
• The device name is now also displayed for removed devices
  Backup of device specific data of future IEM apps​
• Implementation of a unified and dynamic interface for the backup of device specific data of future IEM apps
• Each future IEM app can be individually configured by the respective IEM app developer to have its device specific data considered upon a backup and restore

Improvements of IEM UI

User can now click "Discover a new experience" and he will get redirected to a new Experience where we plan to deliver RT by RT new features. This button is available for every page where we take currently care of. Right now it is available for the Device Overview page only.

Bug fixes

Describe what was fixed

Open issues

Describe what has not been fixed yet

Important notes

Describe what to pay attention to during an update