Predix Edge Manager Release Notes 2.3.0
These are the new features, enhancements, and known and resolved issues for Predix Edge Manager.
New Features/Enhancements
This release contains the following new features and enhancements:
- AppHub
- Predix Edge Manager can be configured to work with the AppHub service, allowing for custom micro-app integration. (BETA)
- Edge Manager APIs (V1)
- Edge Manager APIs have been made public to allow you to manage alerts, devices, packages, and BOMs, as well as execute commands on devices directly via RESTful API calls.
Known Issues
This release has the following known issues:
- No link for edited configurations
- After deploying an edited configuration to a device, a link for the operation details is not created. All other deployments result in a link to the operation details being provided.
- Browser Issues
- On Firefox and Chrome browsers, there is a plug-in conflict that causes the browser to crash (GE internal only) when downloading a file, or when viewing the output of a command.
The same plug-in conflict causes an error when uploading a large file (hundreds of MB).
- Execution time does not get updated
- When you update a Docker container, the Execution Time in the Deployment Schedule does not get updated in Edge Manager. However, Start and End times are updated and displayed correctly.
- Time for operations displayed differently
- Operations start, execution start, and elapsed time display differently for the top level versus operation details when there is only one operation. This is due to how the summary is calculated versus how the operation detail is calculated.
- Software and configuration packages sometimes need to be re-deployed
- If a device is placed in inventory but not enrolled, and software or configuration packages are sent to that device, and one of the Edge Manager services fails and needs to be restarted, then those software or configuration packages may need to be redeployed to that device.
- Cannot delete groups with large number of devices
- There is a known issue with deleting a group with a large number (over 5,000) of devices. Do not create such large groups, or move devices incrementally out of large groups so you can delete the group.