Ignition Features and Ideas

Currently there doesn't appear to be a way to login to an Ignition application using a password manager lastpass, onelogin, keeper etc. This would be very useful for enterprise situations where staff usually have a password manager and use it to open and login to applications automatically.

Currently Perspective projects rely on the keyboard of the OS. This can be very unreliable sometimes, especially with Windows IoT OS. Having a built-in keyboard would eliminate the need to build a custom keyboard in the project and help users move from Vision apps to Perspective workstation. It would also be helpful if the keyboard could be limited, such as to only letters or a number pad, for certain apps. This would help limit inputs from operators.

Similar to a Unix kill, Windows disconnect/logoff, Oracle and SQL Server kill session. We need the ability to free resources being edited by an absent user (on sick leave, vacation, etc.). Yes, their unsaved edits will be lost but that is more acceptable than losing your work when they come back a week later and save their work over the top of what you did while they were away. Also see: https://forum.inductiveautomation.com/t/perspective-session-says-user-me-is-still-editing-resources-even-though-i-have-saved-updated-and-closed-the-project-is-there-something-i-am-missing/92527

Give the possibility di add additional anchor points or edit the existing, for a Perspective component (e.g. pump, valve, vessel, etc) or an SVG, so that piping can piping can be linked tp a specific position of the component/SVG, for example bottom-left, instead of center-left NOTE: The builtin Perspective Symbol "Vessel" already have 3 anchor points on each side, instead of the 1 as most of the other components. It would be great to have the possibility to add, remove and edit these points

I do this all the time, forgetting I have to switch back to the Designer main window to be able to save.

It would be great if the existing DateTime Input and DateTime Picker components could be modified to allow selecting a datetime range in the one component. E.g. Select Start date and then End date, and change start/end times if needed as well, all in the one calendar interface. It's a lot more intuitive for users to select a date range from one interface rather than have to use two Input components and have to navigate to the right month/year in each, independently. Bonus features: highlight "today"! highlight other days with custom styling, tooltips, icons, based on an array of params

Support Folders as a data type in the Multi-Instance Wizard for quickly spawning sequentially numbered folders for later use.

I would like the ability to lock (freeze) the left most column or columns in the Perspective Table component so that when you scroll to the right the selected columns are always left visible. This would be the equivalent of freeze panes in Excel.

One of my biggest pet peeves is the lack of a great way to handle red/error/empty values in components while a page is still loading. Currently, when components are loading in their values, they often display a red bar or error message until the values are loaded, which can take several seconds. Disabling the overlay is not a great option because it prevents the user from knowing when an actual error occurs. Therefore, I propose a new feature that would greatly enhance the usability and user experience of Ignition. This feature would allow users to set a buffering time or load time, defined in seconds or milliseconds, at the project or component level. During this specified time, components would display a custom message, loading icon, or empty value, instead of the red bar or error message. Once the values are evaluated, the overlay would be displayed as usual. This new feature would be particularly useful when switching views and pulling in tag values, as it would allow for a set amount of time for the values to load before displaying the overlay. I believe this would greatly improve the overall operator and user experience and make Ignition even more user-friendly. Thank you for your time and consideration.

It would be really helpful to have shared Data Types between gateway platforms in Ignition Scale-Out Architecture. for example, if we have Pump UDT we could make an instance either on local tags folder or remote tag providers.