# Intelligent subflow displaynaming

**URL:** <https://discourse.nodered.org/t/intelligent-subflow-displaynaming/37200>\
**Category:** Feature Requests\
**Created:** [8 December 2020 20:23 UTC](https://discourse.nodered.org/t/intelligent-subflow-displaynaming/37200 "2020-12-08T20:23:17Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![HenrikSchmidt](https://avatars.discourse-cdn.com/v4/letter/h/3ec8ea/32.png) [@HenrikSchmidt](https://discourse.nodered.org/u/HenrikSchmidt)\
**Post date:** [8 December 2020 20:23 UTC](https://discourse.nodered.org/t/intelligent-subflow-displaynaming/37200/1 "2020-12-08T20:23:18Z")

</div>

I tried to cut together a simple demo of how I do today instead of using sub nodes because the limitation of not having a way of knowing what some params are without opening it.  
Leaving me with 100 anonymous node blocks OR having to write every command twise, once in a env and one in the Name field, and then always typing correct twise.

 ![nodered_subnode_naming](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/5/7/57649e5ec095f249c90ec1d610debfdffdb151ed.png)  
there is already a way to format the output of UI\_nodes that work well, I just want to reuse it here.

I have been waiting for the possibility to get to the Name property in the subflow, this solution would work even better to solve the same problem i think

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [6 February 2021 20:23 UTC](https://discourse.nodered.org/t/intelligent-subflow-displaynaming/37200/2 "2021-02-06T20:23:30Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [17 February 2021 10:17 UTC](https://discourse.nodered.org/t/intelligent-subflow-displaynaming/37200/3 "2021-02-17T10:17:38Z")

</div>



---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [17 February 2021 10:19 UTC](https://discourse.nodered.org/t/intelligent-subflow-displaynaming/37200/4 "2021-02-17T10:19:29Z")

</div>

Hi @HenrikSchmidt

my apologies for missing this post - thanks for the nudge.

I think there is some merit to this suggestion. Custom nodes are able to set custom functions to generate their label based on node properties. It would seem having a similar capability with the subflow nodes would be useful.

I'll add it to the backlog.

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [17 February 2021 16:47 UTC](https://discourse.nodered.org/t/intelligent-subflow-displaynaming/37200/5 "2021-02-17T16:47:34Z")

</div>

That said, there is a problem with the feature as you describe it.

If I set the subflow name to `{{Command}} {{Value}}` as you suggest, so those properties will be substituted into the label in the editor, that means the subflow will be labelled with `{{Command}} {{Value}}` in the palette - as that label isn't tied to a specific instance of the subflow to get its values.

We do have the concept of a `paletteLabel` property - which allows a node to specify what label should appear in the palette versus what label to appear when the node is added to the workspace.

If we add this feature, we'd need a way for the user to optionally also set the palette label. So it requires a bit more thought and effort than simply adding support for `{{ }}` syntax.