Cumulocity IoT Feedback Portal
ADD NEW FEEDBACK

Cumulocity IoT Platform Services

Showing 126

moving up from child MO to parent MO in the hierarchy issue

Kemin encountered this situation: a Device has a child device assigned. An user has inventory read access on a device group, both devices are assigned to this device group. For Kemins use case, they need to find the ID of the parent device based o...
Guest 4 months ago in Cumulocity IoT Platform Services / Data at Rest 1 Planning / planned

UPdate fields available for Azure SSO integration

When we configured Cumulocity to integrate SSO with azure, we needed to use the custom template to have OAUTH2 work. Specifically, we needed to add the scope field and set the scope to ${clientId}/.default
Dave Presuhn 2 months ago in Cumulocity IoT Platform Services 0

Implementation of Sorting and Filtering option for Audit logs

Currently, the audit logs in Administration application has no sorting options and also filtering options available are limited. We are proposing the implementation of the below that would enhance the UI experience and also help in troubleshooting...
Mohammed Ali Khan 12 months ago in Cumulocity IoT Platform Services / Platform Management 1 Future consideration

Password expiry warning

Problem Statement: At the moment user doesn't get any warning about their password expiry. If user didn't login for a while and password lifetime expired, then they only get to find it out at the time of login. This becomes a problem when user use...
Khademul Kabir over 1 year ago in Cumulocity IoT Platform Services / Platform Management 1 Future consideration

Add the Ability to Clone a Tenant

Currently setting up a new tenant is a manual (and error prone) process e.g., users must be added, widgets added and customized, smart rules created, and device protocols configured. To quicken this process, it would be useful to be able to clone ...
Iain Mackenzie 11 months ago in Cumulocity IoT Platform Services / Platform Management 3 Future consideration

Notification 2.0 API - Allow to subscribe to events from all devices

The Notification 2.0 API only allows to subscribe to events for a single device / managing object at a time. Subscription to all events (i.e. at the tenant level) is needed for the wm.io Cumulocity trigger
Frédéric Joulin over 2 years ago in Cumulocity IoT Platform Services / Data in Motion 0 Planning / planned

add a field "received_time" in measurements

I have a use case with logical devices that send batches of measurements. It happens that the data is completed or recomputed at ground side and measurements are sent again to Cumulocity. We experience problems when deleting existing measurements ...
Guest over 1 year ago in Cumulocity IoT Platform Services / Data at Rest 4 Future consideration

disable unused features

Not all features are used by all users. For example, we do not use the platform to send commands to our medical devices. It would enhance security if features could be disabled so they could not be used by an attacker when they are not used as par...
Dave Presuhn 3 months ago in Cumulocity IoT Platform Services / Platform Management 1 Future consideration

Notification API 2.0 - Allow to subscribe to measurements to all devices

We would like to subscribe to the measurements from all managed objects (devices) on the platform using the Notification API 2.0. Currently, a subscription must be created for each individual managed object.This makes it easier to subscribe to the...
Thomas Kühn about 2 years ago in Cumulocity IoT Platform Services 1 Unlikely to support

Digital Twin: Include last measurements and events in the managedObject of the device

To improve performance of dashboards, and to allow faster access to digital twin, it would be good, if for each measurement and event type, the last received object was also cached in the managedObject. In case new measurement/event of the same ty...
Peter Gaspar almost 3 years ago in Cumulocity IoT Platform Services / Data at Rest 4 Planning / planned