To save or not to save! Knowing whether config has changed since the last save...

I’ve been gradually building a wish list of things that for me would move KNIME even closer to perfection… :wink:

I would really like to have a way of knowing whether my unsaved workflow has had any “node modifications” to it since the last time I saved it, or whether the only difference from the saved version is that it has been reset/re-executed.

When I open a workflow, if all I then do is reset it and execute it, I generally do not need to save it, but if I open and reconfigure a node, or add or delete a node, or maybe move things around a bit, I would like to know about that, because then it is important that I DO save the changes.

So this item on my wish list would be to have two indications on a workflow that shows (1) if it has been reset/re-executed since it was last saved, and (2) whether it has been edited (as in manual changes made to nodes/config) since it was last saved.

Why is that important to me? Ultimately its for my own version control. If I make a config change to a workflow, I will at some point want to save this as a new version. But if the only change made today was that it got re-executed, I wouldn’t generally want to save it as a new version. I might do, but mostly I won’t.

But after a couple of hours of working and switching between flows I invariably come back to one that is showing as “modified” with the * in its title bar, and I think “Did I change the config? Did I save those config changes before I ran it?” and so I end up saving yet another version “just in case”.

I know that I could be more methodical about the way I work. But I suspect that upgrading KNIME will
ultimately be easier than upgrading me! lol

@takbb well … the KNIME server does have version control. There every time you make a significant change within your workflow you can save a version (similar to GitHub) and even list and inspect the changes you made …

Thanks @mlauber71, the full version control of the server is something I’ve yet to experience first hand although hopefully I’ll soon be using KNIME business hub so I will see if my thoughts change when I do.

At the moment within AP,
the only time a workflow does not show as needing to be saved is when it is first opened. If I breathe on it, it says it is unsaved, and a distinction between what I see as a “code change” and what for me is simply a re-execution would be good.