Cumulocity IoT Feedback Portal
In different widgets, regardless whether they present data points, properties or alarms, it should be possible to provide wildcards - on top of filtering and selecting individual names. This would allow to pre-select data points, properties or alarms created in the future based on their naming scheme.
Hi Luiz, thanks a lot for sharing this feedback
We agree this would be a valuable improvement, but as per the current Alarm API it requires specific Alarm Type to be passed into it and similarly structure in other APIs such as on supported series and hence allowing wildcard might not be directly feasible.
On the idea from Neil for showing the current matches while the user is attempting to use * anywhere on the platform, we are still exploring if that is feasible and will provide you an update soon
I agree that the mechanism for locating items (managed objects, measurements or events/alarms), and the apparent use of wildcards is not intuitive in various parts of the platform.
For example: in inventory roles, its possible to use "*" to represent "all types". It's not obvious which, and how many types this represents, so you can't do a sanity-check or spot that you might have included a type that's not what you intended. It's also not obvious is you can use partial wildcards here - e.g. "*Position*" - but I'm guessing that this won't work?
In some parts of the platform this could lead to potentially serious unintended consequences: e.g. in nominating items to be part of inventory roles, or DataBroker (where unintended addition of the wrong items now or in the future could amount to a GDPR or intellecual property leak).
In general, if wildcards are used anywhere in the platform, I think it would be helpful if the user were shown a list of current matches, allowed to tick them (some or all), and also explicitly ask the question "Include future matches for this search?"