A common problem I have is that using the standard dashboard, it is tricky to display several fields in an organised manner. Sure, you can set up 10 or 20 fields of text for a machine, but what to do when you have the same 10 or 20 fields on 30 or 40 machines? That's a lot of branching flows, and a lot of nodes that must be configured individually.
In my usual application, I had a workaround that used function nodes to transform the JSON object into an HTML string that prepares a formatted table (I used css to style the borders and warning/error themes for the out-of-bound parameters), then I feed that into a text node.
The problem for that is the humongous amount of work required for each individual template, but once it's done, it's just copy-pasting the text node for a machine, and feed it the formatted HTML string. Still, that's a workaround, and a clunky one at best.
I've been using forms lately, and I realised that forms are easy to arrange, you can display a big amount of fields in a simple column or two-column arrangements. There are also several controls to choose from.
Forms can be initialised by feeding them a proper JSON with the field names and the initial values, so each field is able to serve as a display. They can already be used to display data, but the only problem is that the fields are meant as an input, and as far as I know, that can't be disabled. Same for the submit-cancel buttons.
I was wondering... would it be possible to disable the input/button functions and use the form just as a display?
I think it would already save a lot of time and enormously simplify flows where you require to show several parameters. Of course, some options (as changing the colours of a field according to its value) would be missing, but it would still be very useful.