Create an array of UDT inside a tag. This will make tagging way easy.

I would like to be able to defer updates on the DateTime input, similar to the Text Input. This mostly applies to the "Time" portion.

I've heard some sort of offline support has been planned for a while, and the most recent related item I find is this forum post: https://forum.inductiveautomation.com/t/feedback-offline-mode/20259/6 So I'm just wondering if there is any planned offline mode, or if it's still in the roadmap? The idea of offline forms that sync up data entry to the server when back online would be extremely useful. Thanks

I believe there are quite a few of us that would benefit from the ability to force a user into a specific screen orientation during a Perspective session. Ideally this would be configurable on a per view/page basis if that's possible. Thanks!

Add the ability to search/find within the stylesheet (like how find works in a project script). Add the ability to organize a stylesheet into regions or a means to select sections from a tree view (like a project does).

It would be really nice to be able to designate in scripting how the query will format the data on return. Like if I run a query binding I can designate it to return in json format which seems to behave better within Ignition, and I should be able to pass that parameter to the system function as well.

It would be extremely helpful to have Perspective functions analogous to the Vision scripting functions for showing errors, getting confirmations, showing messages, and taking user inputs. Many functions would be useful, but these are the ones that come to mind in rough order of priority: system.gui.confirm() system.gui.inputBox(), system.gui.show [NumericKeypad/TouchscreenKeyboard] () system.gui.[error/warning/message]Box() These functions were extremely useful in Vision, and homebrewing equivalent versions with message handlers and custom scripting carry a lot of overhead.

In Vision Templates, you can not access the tag metadata for a standard tag that is linked as a Template Parameter. This severely inhibits introspection for building widgets with standard tags. However, UDTs do expose both TagName and TagPath, allowing functionally infinite introspection. Can Standard Tags be upgraded to support this as well? Having a full reference to the tag would be nice, but just access to TagPath and TagName would be enough.

When editing Named Queries created in a parent project it is possible to view them "read only" instead of overriding them in the current project. This is useful when you have a "global" project containing all queries and you want to quickly view them. The same option should be available also for views, which instead at the moment only allow overriding them temporarily to open them and then discarding the override once closed.

I suggest an additional type of template parameter that is a specialized version of the string-type parameter, for the primary purpose of allowing the templates to accept drag-and-drop from tags and immediately interpret them as their tag path. It would then also allow UDTs to interactive more natively with Indirect Tags, which has all manner of positive side-effects (repeaters, canvases, etc). Fundamentally it should be the same as a string-type parameter, but with the addition of allowing interactions with the template to prioritize using the tag path rather than other aspects of the tag. For instance if you drag and drop a UDT onto the template that has a path-type parameter flagged as the Drop Target, it will fill the field with the path of the UDT rather than a UDT-type parameter that would latch onto the UDT itself.