Ignition Features and Ideas

I have lost progress on projects and not been able to trace issues because Project Auditing was not enabled or configured correctly. I suggest a Gateway Setting to "Enable Default Project Auditing" and if enabled an Audit Profile selection. If set, any new project would be created already recording to the selected Audit Profile.

For the builtin icons, it would be nice if icons had multiple descriptors that are searched against, rather than just the name (and instead of listing them twice). For example, "X" or "remove" might show the "close"/"clear" icons. As it is now, it can be faster to scroll through all icons than to guess different names an icon may be under (particularly a problem because material builtin doesn't contain all material icons). Sometimes, it is so hard to find that it becomes easier to just go to iconify and copy one in.

Add an easy way to add resources like icons or icon packs to the gateway.

In scenarios where we may have multiple designers opened that are connected to unique gateways but happen to share the same project name and same gateway name yet differ by deployment mode (e.g. "dev" and "qa"), it would be nice to have the deployment mode also displayed at the top. Currently I have to dig down to the System tag provider in the tag browser to find the deployment mode tag to differentiate the two. The title could look something like: <Project Name> - <Gateway Name> | <Deployment Mode>

Symptom: Table object's selection is stuck after a refresh in the browser. Selected row and selected dataset holds the last value from before the refresh, and resetting these properties does not work. Setup: Table object, query binding that returned dataset with 3 columns. Row selection and multiple interval selection are enabled. Four columns are configured in column properties. The fourth uses a custom view to show a calculated status, with 'field' set to 'column_4', which does not exist in the dataset. The view has a parameters bound to the implicit 'value' and 'rowData'. Suspicion: Table object fails when 'value' is null/undefined for a column whose field isn’t in the dataset. This seems to leave the table’s selection state stuck after a refresh.

Support more formats than RGB/HSL types - Such as OKLAB. This is already technically possible, but giving it a picker like RGB has would be nice.

It would be great for the tag report tool to include the option to include tags with configured alarm pipelines.

Requested Enhancement: Provide a configurable pre-login challenge/token timeout. Alternatively, automatically refresh or renew the challenge/token while the login page remains open. Allow administrators to define an appropriate timeout based on operational requirements and security policies Details : Currently, the Perspective pre-login authentication challenge/token has a hardcoded ~5-~15 Min timeout that cannot be configured. Once the login page remains idle beyond this timeout, users can enter valid credentials but receive an HTTP 400 error on the /next-challenge request. The user must manually refresh the login page before authentication can proceed successfully. This behavior has been reproduced in both web browsers and Perspective Workstation and has been confirmed as the current expected product behavior. Additional Notes: This functionality should be independent of the existing Perspective Session Inactivity Timeout setting. Increasing the session inactivity timeout does not prevent the pre-login challenge from expiring. The current behavior can lead to failed login attempts and user confusion when login screens remain open for extended periods before authentication.

Are there any plans to add a dark theme to the ignition designer? I see that this question has been posted a few years ago but its 2020 now so I thought I would ask again.

I'm generating some reports and saving them to a database. I'd also like to save the data used to generate the report, so it can be used in downstream analytics. It would be helpful if system.report .executeReport returned both the binary report and the data dict used to construct it. My workaround is going to be to save the data object to the database as the last script in the Data tab of the report, then update that row with the report binary in the caller. That's approach is a little trouble prone.