Backwards compatibility node update

We have developed a set of KNIME nodes, we are now planing to release a newer version of these nodes with input and output ports changed. Preexisting workflows that use our nodes will be compatible only if they are reset. Does this mean that we need to add code for backwards compatibility, please advice on best practices.

Hi @wbibile,

The best practice is to keep an old, unmodified version of the nodes in your code, but mark them as deprecated in the NodeFactory.xml file and the plugin.xml.

See for example this deprecated node:

This way workflows created with old versions of the nodes continue to work, but the old nodes are marked as deprecated and not shown in the node explorer.