Cumulocity IoT Feedback Portal
Currently, clicking on non-device objects such as microservice application from events, opens the device info page for that object which is ideally not correct nor user-friendly.
Issue impact?
When users have large amount of assets (devices/non-devices), it would be highly difficult for the user to distinguish between both object types by mere display of every object via. device info page. Also displaying of non-device object as device object is a bad user-interface.
How it can be useful?
When devices and non-devices objects are displayed in a different page according to their types, it will give user the good user-interface and allow them to easily identify the object type accordingly, saving a lot of time from trying to figure out the object.
Proposed solution:
Display device and non-device objects in a separate window according to their types instead of displaying everything in device info page.
Hi Jane,
It can be via. two ways - one is from the 'Events' menu under 'Overview' or another from the simple MO search in the Device Management application.
From 'Events' menu in Device_Management -> Overvies: If the source is a microservice and the user wants check the source then upon cliking on it, it opens a device_info screen (similar to the one displayed for devices) for that microservice instead of navigating to the microservice itself.
From search bar in Device Management application: If there are any MOs returned as part of search which are not devices and the user clicks on those MOs, it again opens up a device_info screen for that MO instead of navigating to the original MO (anything displayed other than devices and groups such as device profiles)
Attached a screenshot for a microservice in Device management application.
Hi Mohammed,
Apologies for the delay in responding. Can you please provide more clarification on precisely which view you use to click on the microservice that then takes you to the device page? Some screenshots would be useful.
Thank you, Jane.