Skip to Main Content
Cumulocity IoT Feedback Portal
ADD NEW FEEDBACK

Cumulocity IoT Platform Services

Showing 64

Expose microservice endpoints without authentication

Example use cases: We have an Alexa integration which currently runs on webMethods and would like to have a microservice variant of that. Amazon requires of you to provide an unauthenticated REST endpoint and that you validate the certificate to e...
Nikolaus Neuerburg about 5 years ago in Cumulocity IoT Platform Services / Product Infrastructure & Microservices 1 Future consideration

Display message for Password reset email sent can be improved

Currently when the user tries to reset password using forgot password option, with wrong email id which doesn't exists, gets a standard display message that the "Password request has been sent. Please check your email". It is quite misleading to h...
Mohammed Ali Khan 9 months ago in Cumulocity IoT Platform Services / Authentication & Authorisation 1 Future consideration

Notifications 2.0 - Add the ability to filter on Managed Object fragments

Enhance the Notifications 2.0 subscription filter to enable filtering on managed object fragments such as device type and to use wild cards in filters, such as “c8y_temp*”, to match everything starting with “c8y_temp”.
Iain Mackenzie 9 months ago in Cumulocity IoT Platform Services / Data in Motion 1 Future consideration

Retention Rule for Binary Store

We create exports in our application. Now it would be nice to have the possibility to create a retention rule to delete exports older than x-days. ATM that seems not be possible.
Florian Gopp about 2 years ago in Cumulocity IoT Platform Services / Platform Management 1 Future consideration

For users created via SSO, display a more user-friendly value in the upper right corner (where the user menu is).

Sometimes the value of the User ID for users created via SSO is just a UUID value, i.e. some random string. This way it is difficult to understand which is the currently active user. Ideally a name or an email address would be displayed, similar t...
Guest over 3 years ago in Cumulocity IoT Platform Services / Authentication & Authorisation 0 Future consideration

Enable Response/Error Mapping in Smart Rest via MQTT

On behalf of TT-Control, I'd like to create the below feature request: # Feature Request - Enable Request/Response Mapping in Smart Rest via MQTT ## Requirement TT-Control implemented an Agent in Smart Rest 1 via Mqtt a while ago. They have the re...
Guest over 3 years ago in Cumulocity IoT Platform Services / Data in Motion 0 Future consideration

Data Broker Back-channel

The data broker is forwarding objects such as Alarms from one tenant to another. However, there is no mechanism to sync data back to the source tenant. One example is an alarm that is cleared in the target tenant will still be active in the source...
Guest about 5 years ago in Cumulocity IoT Platform Services / Data in Motion 1 Future consideration

Improve Application Version Visibility

As an administrator, it is not easy to identify the version no. of the application already subscribed or the version no. of the available applications for subscription (screenshot below) Tenants > Subtenants > Applications > Available App...
Rahul Talreja 5 months ago in Cumulocity IoT Platform Services / Platform Management 0 Future consideration

Databroker filtering process

Filtering process is not good enough. It does not allow to filter by different fragments. We need to create 1 filter per fragment. It would be nice to have some sort of "OR" filter for fragments, so we could add as many fragments as needed into 1 ...
Guest over 1 year ago in Cumulocity IoT Platform Services / Data in Motion 0 Future consideration

Alarm Synchronization DataBroker

Databroker currently synchronizes objects from edge instance to cloud instance based on events occurring in Cumulocity Edge. Same requests sent to Cumulocity Edge are sent to Cloud instance. When losing connection in the Edge side, Databroker is e...
Guest over 1 year ago in Cumulocity IoT Platform Services / Data in Motion 1 Future consideration