When working in the Workflow Configuration GUI, what actions cause the “Save” and “Send Configuration” icons to become active?
Obviously any new processes or alterations to current processes, but what else? I support users who claim even “looking” at a process makes the buttons active, and there is confusion about whether they need to Send Configuration or not.
Opening most properties or preferences dialogues and then using the OK button to close it, rather than Cancel or X, will make the configuration tool think a modification has taken place. This may be what those users are experiencing.
The same applies to loading a new debug sample, as the path to that file will be stored in the config file.
As with any sensitive production system, it’s a good habit to always hit the Cancel button if no changes were intended. You never know if something got changed accidentally when you were only intending to look. Always hitting OK is a recipe for disaster when that inadvertent change happens as you might not even know what you changed to be able to revert it.
This same argument, of course, applies to hitting that Send Configuration button. If you were not intending to make a change, don’t hit it. If your intention was only to look and that button lights up, it doesn’t really matter why it did. Don’t push it if no changes were intended.
Thank you. I believe opening Plugins and closing them with “OK” is the main culprit.