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.

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.

Add support to expose tags as BACnet objects so that external systems can read them. OPC UA is great, but many clients specifically request BACnet/IP access to SCADA data and therefore a protocol converter must be used.

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.

It would be great if there was an option to transition a number of style properties on a component to a style class within a perspective project. I often find myself testing looks that work nice on specific components, but have to re-copy all of these things over manually to a style. Having the style class menu be able to receive a json of all the style props copied from somewhere in the project (maybe a right click on component?) and be able to paste them in a style class of some sort would be excellent. I love making cool components, but always stumble at the hurdle of putting them at a project scale setting

Details in this post: https://forum.inductiveautomation.com/t/feature-increase-usability-of-the-perspective-power-chart-component/51474?u=nminchin

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.

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