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

**URL:** <https://forum.knime.com/t/proposal-implementing-symbolic-links-for-script-nodes-in-knime/83366>\
**Category:** Feedback & Ideas\
**Tags:** python, java-snippet, node\
**Created:** [September 19, 2024, 10:05am UTC](https://forum.knime.com/t/proposal-implementing-symbolic-links-for-script-nodes-in-knime/83366 "2024-09-19T10:05:12Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![ekadagami](https://forum-cdn.knime.com/user_avatar/forum.knime.com/ekadagami/32/64248_2.png) [@ekadagami](https://forum.knime.com/u/ekadagami)\
**Post date:** [September 19, 2024, 10:05am UTC](https://forum.knime.com/t/proposal-implementing-symbolic-links-for-script-nodes-in-knime/83366/1 "2024-09-19T10:05:12Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![HaveF](https://forum-cdn.knime.com/user_avatar/forum.knime.com/havef/32/1124_2.png) [@HaveF](https://forum.knime.com/u/HaveF)\
**Post date:** [September 19, 2024, 11:02am UTC](https://forum.knime.com/t/proposal-implementing-symbolic-links-for-script-nodes-in-knime/83366/2 "2024-09-19T11:02:03Z")

</div>

Hi, @ekadagami  
have you ever try [`sharing-components`](https://docs.knime.com/latest/analytics_platform_components_guide/index.html#sharing-components) feature?

---

<div class="post-metadata">

**Author:** ![mwiegand](https://forum-cdn.knime.com/user_avatar/forum.knime.com/mwiegand/32/66896_2.png) [@mwiegand](https://forum.knime.com/u/mwiegand)\
**Post date:** [September 19, 2024, 12:27pm UTC](https://forum.knime.com/t/proposal-implementing-symbolic-links-for-script-nodes-in-knime/83366/3 "2024-09-19T12:27:28Z")

</div>

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

> **[Call Workflow Service](https://hub.knime.com/knime/extensions/org.knime.features.personalproductivity/latest/org.knime.workflowservices.knime.caller2.CallWorkflow2NodeFactory)**
>
> Calls another workflow and obtains the results for further processing in this workflow. The workflow can receive inputs via Workflow Service Input nodes and re…

---

<div class="post-metadata">

**Author:** ![ekadagami](https://forum-cdn.knime.com/user_avatar/forum.knime.com/ekadagami/32/64248_2.png) [@ekadagami](https://forum.knime.com/u/ekadagami)\
**Post date:** [September 20, 2024, 7:33am UTC](https://forum.knime.com/t/proposal-implementing-symbolic-links-for-script-nodes-in-knime/83366/4 "2024-09-20T07:33:28Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![ekadagami](https://forum-cdn.knime.com/user_avatar/forum.knime.com/ekadagami/32/64248_2.png) [@ekadagami](https://forum.knime.com/u/ekadagami)\
**Post date:** [September 20, 2024, 7:39am UTC](https://forum.knime.com/t/proposal-implementing-symbolic-links-for-script-nodes-in-knime/83366/5 "2024-09-20T07:39:46Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![system](https://forum-cdn.knime.com/uploads/default/original/1X/ab3ccf34482a0329361734a18199390177204f15.png) [@system](https://forum.knime.com/u/system)\
**Post date:** [December 19, 2024, 7:40am UTC](https://forum.knime.com/t/proposal-implementing-symbolic-links-for-script-nodes-in-knime/83366/6 "2024-12-19T07:40:22Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
