Proposal: Implementing 'Symbolic Links' for Script Nodes in KNIME

I’d like to propose a feature that could significantly improve workflow management, especially for complex projects involving multiple script nodes with identical content.

Current Challenge:

In complex workflows, particularly those with numerous script nodes, we often find ourselves using nodes with identical content in multiple places. When changes are required, we must manually edit each affected node, which is time-consuming and prone to errors.

Proposed Solution: ‘Symbolic Links’ for Nodes

I propose implementing a feature that allows users to create ‘symbolic links’ (or mirror/shadow nodes) to a specific node. This would work as follows:

  1. Users can designate a node as the ‘source’ node.
  2. Other nodes can be set to reference this source node.
  3. When the source node is updated, all referencing nodes automatically reflect these changes.

Benefits:

  • Reduced error risk: Eliminates the need to manually update multiple identical nodes.
  • Time-saving: Streamlines the process of making changes across a workflow.
  • Improved consistency: Ensures all linked nodes remain identical.

I’m aware that KNIME allows for the creation of custom nodes, but this process can be disproportionately time-consuming for simpler use cases. The proposed ‘symbolic link’ feature would offer a more lightweight solution for many scenarios.

Questions for the Community:

  1. Does a similar feature already exist that I’ve overlooked?
  2. What are your thoughts on this proposal? Would it be useful in your workflows?
  3. Can you foresee any potential drawbacks or challenges in implementing such a feature?

I look forward to hearing your feedback and insights on this idea. Thank you for your time and consideration.

Hi, @ekadagami
have you ever try sharing-components feature?

3 Likes

Or splitting a workflow apart and calling it remotely i.e. using Call Workflow Service:

1 Like

I had actually considered this as an alternative option. But it seems a bit ‘overkill’ to me…thanks for the tip anyway.

Ah, that’s interesting! I didn’t realise you could share components. I never thought of converting a single node into a component. But I will be very happy to try it out. Thanks for the tip.

1 Like