Cumulocity IoT Feedback Portal
ADD NEW FEEDBACK

All feedback

Showing 374 of 374

Platform connects devices with closed network.

We would like to use private network access to CUMoNoSU. Once of MVNO provides us with the private network access to AWS as follows: https://www.soracom.io/products/canal/. The service is called Soracom Canal which allows its SIM to connect to AWS...
Guest over 4 years ago in Cumulocity IoT Platform Services 2 Unlikely to support

Removal of ā€œAuto observeā€ switch object from GUI in Cumulocity portal

ā€œAuto observeā€ switch object needs to be deleted from GUI in Cumulocity 9.16 (or 10.5). This switch is located in Device Management page > Device type category > Device protocol item > any of protocols. This feature appears as we ...
Guest over 4 years ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Unlikely to support

Documentation "custom search" result links should jump directly to the found text

Example: On "https://cumulocity.com/guides/users-guide/getting-started/" add "add data subscription" (with quotation marks) in"custom search" field. Click the hit. The it brings you to the top of https://cumulocity.com/guides/users-guide/enterpri...
Guest over 4 years ago in Cumulocity IoT 2 Future consideration

no duplicate folder names for device groups

- if customer have much groups with same name > it comes to parallel effects
Guest over 4 years ago in Cumulocity IoT Cockpit and WebSDK / WebSDK 1 Unlikely to support

HTTP requests that contain a batch of multiple requests, to remove round-trip latency issues

Currently, for nearly all operations (apart from create measurements) the only option is to perform a network roundtrip - send a request, wait for a response. While it's possible to do this over multiple connections concurrently, this is inefficie...
Guest over 4 years ago in Cumulocity IoT Platform Services / Runtime Services 2 Future consideration

LwM2M Firmware repository - fragment with the MO itself to configure individual FW updates to use one protocol over another

Orignial question: We currently have support for both CoAP and HTTP based protocols for the firmware repo, how do we configure individual firmware updates to use one protocol over another? Attached is further commentary between Elias and Cris D...
Guest over 4 years ago in Cumulocity IoT Device Mgmt. & Connectivity / LWM2M 1 Unlikely to support

Allow admin-usernames with more than 50 characters

Already analyzed: https://itrac.eur.ad.sag/browse/IOT-5966 --- When creating a tenant the "ADMINISTRATOR'S USERNAME" has to have <= 50 characters. This also counts for direct API call (property "adminName"). Idea is to remove this leg...
Guest over 4 years ago in Cumulocity IoT Platform Services / Platform Management 1 Future consideration

As Legal I want a method to anonymise all traces (esp. audit logs)

Michael Gesmann told me that our approach to only have usernames in audit logs is not sufficiant for GDPR law. So for legal reason we need to have a method to remove usernames from (and user ID?) from the audit logs on user request. Michael also s...
Jens Wildhagen over 4 years ago in Cumulocity IoT Platform Services 0 Unlikely to support

GeofenceEmail smartrule UI should allow configurability for sending email on entering/leaving geofence

Origin: https://itrac.eur.ad.sag/browse/IOT-6027 Geofence Email smartrule currently doesn't allow to configure when the email has to be sent for geofence violation. ex: - Should the email be raised when a device is entering the geofence? - Should ...
Alexandra Primakina almost 5 years ago in Cumulocity IoT Streaming Analytics (inc. Apama) / Smart rules 0 Future consideration

Tenant option injection into docker environment

Currently we inject tenant options with the same category as the microservice name into each incoming request. First of all there is a risk of creating huge (maybe too huge) HTTP headers. In a technical workshop with ADAMOS, ASM and elunic we disc...
Tobias Sommer almost 5 years ago in Cumulocity IoT Platform Services / Product Infrastructure & Microservices 0 Future consideration