Best way to apply version control or hash checks to KNIME workflows for consistency?

[bluecar007]

I’ve set up a KNIME workflow that I run every month. Before running it, I usually need to update a few variables (e.g., month references) and also change the path to the Excel input file for the new month.

What I’d like to do is ensure that apart from these expected changes, the rest of the workflow has not been modified. Ideally, I want to be able to show others that no other nodes were altered, so that we can be confident the outputs are consistent and reproducible across runs.

Is there a recommended way in KNIME to:

• Run a hash check (or checksum) on the workflow file?
• Or apply some form of version control to the entire workflow (e.g., Git, KNIME’s built-in tools, or external tools)?

I’d love to hear what methods/tools others are using to track workflow integrity while still allowing small input variable updates.

Thanks in advance!

[MartinDDDD]

Hey there,

Two things come to mind:

If you are using KAP desktop only I think you can now “Version” your workflows.

I’m addition in classic UI you can highlight two workflows and compare them / show differences. You could save a version of your WF as sort of a “ground truth” and then compare it to the one where you are modifying the variables to proof nothing else has changed.