Ignition Features and Ideas

Add ability to specify inactivity timer per user. Or add roles selection to existing Inactivity Timer to only logout users with any or all of the selected roles.

We get a lot of warnings in the console like "Transaction '37dcaa14-3c14-42a1-82b6-969cceca1b0f' being closed due to inactivity timeout. Make sure you close your transactions." But we have no way of finding the source of those transactions. The warnings don't list any identifying information such as the database connection or project, let alone which screen or component started the transaction. Searching our projects for "commitTransaction" yields hundreds of results, too many to look at all of them to find out which one is not being closed. And there is no way to export results from Find/Replace so we can compare them to a search for "closeTransaction" which is another separate issue.

Have the ability to add script options for inactivity timeout. Currently the only options allowed are logout or end session. If there was access to the inactivity timer in the gateway for the session or if there was a script that could be run as an option, this would allow for redirect to another page or any other custom option

I would like to develop a Perspective project with an automatic logoff based on inactivity time but with the ability to have different timeout periods for different client host names. One approach would be to add some custom code to monitor the inactivity time and execute the logout command (system.perspective.logout) at the appropriate time. Please add a scripting function that provides the current inactivity duration.

I have a need to see the currently logged in OS (Windows) username from Perspective Workstation so that I can keep users logged in if their Perspective and Windows usernames match, and log them out after inactivity otherwise.

Comparing the system.perspective.logout functionality to the auto-logout (under Project Properties, Perspective → Inactivity), the latter will simply log the user out whereas the former script function will log the user out and completely restart the Perspective session. This might be useful sometimes, but most of the time I just want the session to logout and not have to reload every resource again, so adding an option to not reload the session would be great. In the same vein, it would be great to have this option available for logging in as well, as it just adds to user load times.

We restrict a lot of our windows to one user at a time, and provide a popup giving the user name if a 2nd user tries to open the window. Some windows also have a timer that will automatically close them after so much time of inactivity. This would be very convenient if it was available as a built-in property that could be utilized for any window

Please provide a comparable system.util.getInactivitySeconds variable for Perspective. One application would be to auto-logout users based on inactivity.

Currently StatusPing page only shows "state" giving info on if a gateway is starting or running etc. It would be very useful to also know the activity level here. That would also enable the creation of more robust custom redirect scripts. And help where other systems for some reason would like to know which gateway to try and communicate to. For our current use, getting "Activity Level" is what is important. This could also help as a work around for the reported bug on perspective session stuck on loading screen in redundant setups . But if it is easy to add, other info like "Synchonisation Status" and "Peer Address" may also end up being useful.

System info: Ignition 8.1.35 (running in docker container) Redundant gateway setup (cold, recovery mode manual) Browser: Chromium 112.0.5615.165 and 123.0.6312.122 How to reproduce: Restart both Ignition servers. Open one perspective session on Master and one on Backup right after it becomes running, but before it becomes active. Both perspective sessions will be stuck on loading screen now, but when Master becomes active, that perspective session will continue loading. The one towards the gateway that did not go active will be stuck until someone presses refresh. After refreshing it will manage to load the perspective session from the gateway that is not active, which will then successfully redirect it back to the active one. This is an issue for high availability systems that are required to start up by them selves without any user interaction, since some HMI clients could end up getting stuck in various different scenarios. Expected behavior: The session towards the gateway that did not become active should also continue loading (and then redirect to the active one), without the page needing to be refreshed. Related feature request: A related feature request that could help work around this issue for initial startup would be if StatusPing page also included additional info on if gateway is active, and not just if it is running. That would also enable the creation of more robust custom redirect scripts. And help where other systems for some reason would like to know which gateway to try and communicate to. This has been posted as a separate feature request for adding Activity Level to StatusPing page