Ignition Features and Ideas

The designer currently allows you to (dis)able HTTPS and Authentication for endpoints in the WebDev module. By default, the checkboxes for these options are set to false. We would like to be able to set them to true by default, so we will never forget to turn them on when configuring a new endpoint. It would be even better to have them be true by default, and not be able to change those settings in the designer. This setting would be configured on the gateway instead.

From the Config/EAM/Agent Tasks/ Task History tab, it would be great to display a larger list by default. Currently, it only displays 10 items per page, and this number cannot be adjusted, which can make it difficult to navigate through the full history. It would also be helpful to have a filter.

Every time (so rarely) I need to use an image stored in the image management file system in Perspective, I always have to look up what the url source needs to be to get to it, i.e. the path copied from the Image Management tool needs to be prefixed with /system/images/ . It would be useful if there was an option to copy that path from the context menu. New comers would likely spend a while trying to work out why their image isn't showing.

Unless there are conditions that would prevent it, my request is that UDT Type tag json be auto-converted to bindings if the values have braces in them. This trips up a lot of people trying to quickly create UDT Types from drag/dropped OPC Browser tags by utilising notepad find/replace to replace parts with parameters. E.g. Convert: "opcItemPath": "ns\u003d1;s\u003d[{PLCName}]{DeviceName}.Speed" to "opcItemPath": { "bindType": "parameter", "binding": "ns\u003d1;s\u003d[{PLCName}]{DeviceName}.Speed" }

I believe it would be a nice addition to allow the user to manually type in the date in the date input field along with the option to use the calendar like most web interfaces now.

Support of a change and transport system in Ignition. Every change should be recorded in a change request to ensure that nothing is moved to production without a proper tracking and approval. This would help in all regulated environments without going into Git/DevOps workarounds which are not very common in the operational technology environment. Implementation Idea: Versioning of project changes when they are saved. Option to add a change request number, when the project is saved. Saved projects can be released/approved optionaly and deployed to another instance (Test, Stage, Prod)

I think it would be much more efficient if the parameters were shown and editable directly at the root level, without needing to expand or navigate further. https://forum.inductiveautomation.com/t/feature-show-parameters-at-the-root-node-in-udt-tag-editor/107750

When I copy a date value and paste it as a view parameter, it gets treated as a string rather than a date. The only way I know to convert the parameter type is to bind it to something that returns a date, and then remove the binding.

Feature Description: Support for importing Figma designs (layouts, components, or exported files) directly into Ignition Perspective to accelerate the UI/UX implementation process. This could include tools or APIs to enable: Direct import of Figma files (e.g., SVG, JSON, HTML) Automatic conversion of Figma frames or components into Ignition Perspective Views Enhanced support for third-party design-to-code workflows Business Case / Motivation: Many teams use Figma for high-fidelity design and prototyping. Translating these designs into Ignition Perspective Views manually using Coordinate or Flex containers can be time-consuming and repetitive. A toolchain or plugin that bridges Figma and Ignition would significantly speed up this up!