Cumulocity IoT Feedback Portal
ADD NEW FEEDBACK

All feedback

Showing 127

Archive Feature for Microservice Application

Frontend applications have the archive feature but it is not supported for microservice applications on our tenants and it makes it hard to switch between versions for microservices. Need rollback option, as for Applications.
oana velicu 11 months ago in Cumulocity IoT Platform Services / Product Infrastructure & Microservices 2 Future consideration

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 11 months ago in Cumulocity IoT Platform Services / Data at Rest 4 Future consideration

Device Stats API - c8y_IsDevice & Device Name

The Device Statistics API should have an indication whether the inventory object is marked c8y_IsDevice or not. Some customers use this fragment to identify devices, and it would make identification of each device easier. In addition, the Device S...
Tal Dunne 12 months ago in Cumulocity IoT SaaS Enablement 0 Future consideration

Allow custom LwM2M decoder microservice to create/update arbitrary inventory fragments

A custom decoder microservice can return dataFragments to the LwM2M agent in order to update the managed object, but this is only capable of updating the fragment specific to the LwM2M resource, e.g. "dataFragments" :[ { "value" : "Hello World" , ...
Guest about 1 year ago in Cumulocity IoT Device Mgmt. & Connectivity / LWM2M 2 Future consideration

Access timestamp from custom LwM2M decoder microservice

When a decoder microservice is used as a custom action to process a LwM2M payload, it would be useful to have access to the timestamp if it it present in the SenML-JSON/CBOR message. That is, if the payload is received by the LwM2M agent as the re...
Guest about 1 year ago in Cumulocity IoT Device Mgmt. & Connectivity 2 Future consideration

Export/Import Device Management->Device protocol XML resource mapping

If a user configures a bunch of Lwm2m XMLs and links each resource with MEAs or custom actions inside one tenant, this work cannot be easily exported to another tenant and thus requires manually setting all of this again.
John Fisher about 1 year ago in Cumulocity IoT Device Mgmt. & Connectivity 2 Future consideration

Audit changes for retention in audit log

Users can add retention rules within the Administration application, e.g. add new retention rule that all tenant measurements older than 3 days shall be deleted. This action is not part of the Audit Log. We should audit the changes of retention as...
Guest about 1 year ago in Cumulocity IoT Platform Services / Data at Rest 0 Future consideration

Add PKCE to single sign-on

Add support for PKCE (https://www.rfc-editor.org/rfc/rfc7636) in the authorisation code grant flow when configuring single sign-on as an authentication method. This is related to C8YCORE-I-311.
Guest about 1 year ago in Cumulocity IoT Platform Services / Authentication & Authorisation 1 Future consideration

Provide Import / Export in Data Point Library

A user can define parameters in one tenant, but then can't utilize the same in another tenant. User should be able to export data point library from one tenant to another so that they can be used more often and with ease
Rahul Talreja about 1 year ago in Cumulocity IoT Cockpit and WebSDK / Data Point Library 0 Future consideration

"Up" button or breadcrumb for child devices in Device Management

In Device Management, and in Cockpit, it's possible to "drill down" to examine child devices, by clicking on the "Child device" link, and selecting a child device from a list. However, once you have selected a child device, there is no visual way ...
Neil C about 1 year ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Future consideration