Ignition Features and Ideas

Perspective message handlers currently must be referenced by manually typed string names. This creates avoidable human errors, especially in large projects where many views define different handler names. I would like a feature that allows developers to view, browse, or auto-complete all message handlers in a project—similar to how tags or properties are discoverable. Even a simple scripting function like system.perspective.listMessageHandlers() or editor IntelliSense support would greatly improve reliability and reduce maintenance effort.

Im in need of a driver for IEC 60870-5 101/104. In Sweden it is widely used within communication with switchgears and other electrical devices. Our biggest competitor within the area is Citect and they have this driver and it’s a clear argument from the customers to not introduce more products in the line of communication, i.e. OPC. Also, the whole backbone of the Railroad administration uses 104. Here we compete with Zenon who has the driver also. I know its solvable with Kepware and such solutions, but native drivers are most often heavy arguments. So, if you see the same need as I do, please vote for it😊 https://forum.inductiveautomation.com/t/native-driver-for-iec-60870-5-101-104/86672?u=martin_esping

Currently, the Perspective login screen is not project-based, which means dynamic control via session.props.theme is not possible. The login screen inherits static Gateway branding (logo, colors, etc.), and developers have no access to override or apply project-level themes. This limitation prevents the login screen from following runtime theme changes such as night mode, leading to inconsistent user experience across HMI projects. It would be useful if the login screen could inherit project-level or session-based themes to ensure consistent styling across all views.

In Ignition SCADA, when projects have a large number of UDT (User-Defined Type) instances, and each tag contains event scripts, performance issues become noticeable during tag editing, applying changes, and especially at gateway startup. The current compilation process for these scripts contributes significantly to slowdowns, as Ignition recompiles all event scripts for every tag, regardless of whether they have changed. Impact: -Projects with extensive UDT usage experience long delays when applying changes. -Gateway restarts take significantly longer, affecting system availability. -Development workflow slows down, making iterative changes cumbersome. Suggested Improvement / Feature Request: -Optimize the startup tag change script compilation process to reduce unnecessary recompilation for unchanged tags. -Provide progress indicators or background compilation to improve developer experience during large project deployments. This feature would greatly improve performance, scalability, and usability for Ignition projects with complex UDT structures and numerous event scripts.

I'd like to be able to add an icon (with position: left, centre?, right) with colour / styling into the items of a dropdown menu list. I have a dropdown list where an operator can select items to produce. If the item has already been produced, it will have a check next to it, but they will still be able to select it to make it again. (sounds a bit odd, but that's the requirement)

I need to have dynamic min/max properties on tags, i.e. min/max tag properties should be bindable to other tags.

Perspective Table Component would benefit from a Component Event for onEditCellLostFocus. This would allow for updating values to give a more Excel like experience for users.

Currently we can only send alarms to an Alarm Journal on "Display path" or "Alarm Source" which is extremely limiting. Alarm Source is effectively just based on how you structure your tag provider folders, and Display Path can literally be anything. We've built lots of filtering on the various alarm components to utilize the alarm associated data properties. These may contain plant location, machine name, tag type etc... and would be a much more flexible way to split out alarms into different journals. Not all alarms will necessarily have the associated data property configured in the journal, but in that case it generally makes sense to allow us to bring it through or exclude it by default. Due to the nature of Ignition having tag providers accessible to all projects across the gateway, it would be nice to ensure distinctly different projects have an easier way to include / exclude alarms in their own journals based on properties we choose.

The report module has great potential but is missing some key, base functions. Being able to select multiple components with CTRL-click. Both on the page and in the page-tree (SHIFT-click doesn't work in tree either). Being able to center on page. It exists in the Vision module, so why not in the Report module? A dummy table with only sizing functionality. The Labels component has easy sizing options but you can't customize each cell individually.

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