Ignition Features and Ideas

Add a checkbox to run a script in the Script Console as though it were running on the Gateway. OR Check a box and the Script console would highlight lines that might not work if run as a Gateway event script. I've figured out my issues this time, but it's hardly the first time that I've been all excited that my script runs great in the console only to have it fail miserably while I paste it into a Gateway event script.

Ignition Perspective 8.1.44 (in use) I'm using Airlink to send text messages from Ignition to the user using the alarm notification pipelines (it's working fine). I'm able to receive an SMS from the user to acknowledge the alarm and with that, I can turn off the alarm using script change on the tag. I would like to have a way to receive an SMS text message and then I can read this text and then use it as I need. Example. The user sends an SMS text message to the specific number I'm using in the AirLink (I tested and Airlink can receive the text) and does reach a tag with this text received or store/read the text sent. Another example is the user by SMS text they can turn on alarms like Tornado warning...

I get an error when I call system.opcua.callMethod() from the script console. It'd make my development easier if I could call this from the script console. Screenshot from Ignition 8.1.39.

It would be helpful to change the "HasTypeDefinition" for all Boolean items in the Ignition OPC UA Server to be "TwoStateDiscreteType" instead of "BaseDataVariableType". • [UA Part 5: Information Model - 7.4 BaseDataVariableType] has a DataType of BaseDataTypeda • [UA Part 8: DataAccess - 5.3.3.2 TwoStateDiscreteType] has a DataType of Boolean

It would be super helpful for taking Ignition Data outside of the ecostructure to mapp either the Documentation or Tooltip Property of the Ignition tag to the OPC UA Item Attribute "Description". Would also be great to get units and engLow and engHigh information also as additional attributes. See this community post for more detail: https://forum.inductiveautomation.com/t/opc-ua-item-attribute-description/98879/3

There is .toWindow and .toKiosk, I think a option to minimize the current window would be suitable. Since when running in Kisok it would make the user experiance very smooth. I created a Topic on this https://forum.inductiveautomation.com/t/minimize-window-button/98847

Add basic drawing tools to Perspective (lines, circles, squares, etc.). If feasible, it would be fantastic to be able to group as well.

The Perspective Numeric Entry Field currently does not allow a configuration that updates the value before focus is lost or ENTER is pressed. This needs to be added to match the old Vision component and match the functionality of the Text Field component.

Instead of adding a tooltip to the entire Tree component, I'd like to have individual tooltips for each item in the tree.

Currently third party OPC-UA servers such as those available in CoDeSys PLCs offer the ability to create documentation on Tags using comments in the PLC Tag definition. This documentation can be included in OPC-UA but do not get imported into Ignition's OPC-UA server. This data would be very useful so that Integrators and Programmers can write comprehensive Tag Documentation in the PLC programs and have it also show up in Ignition with a minimal amount of work.