Component Configuration Paramter names too limiting

I greatly suggest to change the limitation for parameter / variable names. why can’t they end with a number? it breaks previous options and there is no apparent reason why “value_1” for example should be invalid here.

Thank you very much for your input. For simplification we decided to have the parameter/variable name together in the new configuration nodes. The parameter name always had the name restrictions due to technical reasons. That is why the flow variable is also bound to the parameter name’s restrictions in this case.


1 Like

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