Improvement Idea: Make it possible to give names input / output ports

Hi Iris,

I do use Metanodes where I want to clean my workflow. As you stated in Improvement Idea: Make it easier to explore connections between nodes in a workflow. : “With these workflows my first recommendation would be a major cleanup using metanodes.” You didn’t mention components.

In accordance with what you stated there, I use Metanodes to clean up my workflow and I use Components when I identify a cohesive and possibly reusable piece of code. And I usually make the component shared to make it really reusable.

Well, this is why I have to prefer Metanodes over Components in some cases:

  1. Using workflow credentials inside components
  2. Wrapped Metanode with Quickforms in inactive branches together with Wrapped metanodes in inactive branches stop the workflow These two issues origin from the pre-Components era so they point Wrapped Metanodes. I reproduced the issue with Components in 4.1.2 today.

I still vote for making it possible to name ports of Metanodes. Thank you.

1 Like