Cumulocity IoT Feedback Portal
ADD NEW FEEDBACK

My feedback: Cumulocity IoT Platform Services

Showing 54

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 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 6 months ago in Cumulocity IoT Platform Services / Platform Management 3 Future consideration

Enable read-only access to certificates

We have multiple teams using certificates for mutual authentication. During their development it would be very useful for them to be able to see the trusted certificates. Right now I can grant them admin rights to certs but that lets them change t...
Dave Presuhn about 2 months ago in Cumulocity IoT Platform Services 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

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 6 months ago in Cumulocity IoT Platform Services / Authentication & Authorisation 1 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

To have editable UI option to change the Administrator's username of tenant owner via. management tenancy

Issue: Currently the Adminstrator's username field of tenant owner is non-editable on management UI, which causes problems when there is a need to change the tenant owner. Workaround: Request Software AG team to change it via. backend everytim...
Mohammed Ali Khan over 1 year ago in Cumulocity IoT Platform Services / Platform Management 0 Future consideration

Log User deleting folders by drag and drop

User can drag and drop folders, included sub folders, around all hierarchy. if they do it in the main folder, they will not see that group anymore. you need to log who is doing this kind of actions to solve arising issue.
Guest almost 2 years ago in Cumulocity IoT Platform Services / Data at Rest 0 Future consideration

Support for bulk alarm uploads using normal REST

No REST support for uploading bulk alarms. Many of our field devices don't have the capability to communicate with the cloud directly, and hence when it is connected to the docking station, the docking station will download all the data from the f...
Guest 6 months ago in Cumulocity IoT Platform Services / Data at Rest 1 Future consideration

case-insensitive filtering in inventory

today, the devices from inventory can only be filtered by case sensitive queries for name or other fragment. Idea is to implement option to filter case-insensitevly. MongoDB provides enough expressions to be used to extend filtering options and st...
Peter Gaspar over 4 years ago in Cumulocity IoT Platform Services / Data at Rest 3 Future consideration