Hey, is there a way to do this without using Apex script? I'm using a graph template, and I've created a node as shown on the right side of the screen. Everything works fine, except for the 'Find Node'. I need to provide a path, and the node's name changes if I duplicate the graph.

my twist nodes will have different suffixs everytime autamtically and this path is hardcoded

if you have multiple nodes matching the same name you would have issues in any case. Because it is then not clear anymore which node you want to find with the given path. And you ipso facto killed your humanly readable unique identifier. This is why the graph also tries to enforce unique patha. I can only recommend adding tags instead, and filtering by them.

If you already use a graph template and you just add a subnet why not use graph::AddSubnet and add the given graph template directly to a subnet? You dont need to stuff the content of your graph template then anymore in a subnet but you can work on the unpacked graph instead. And now that you are adding it as a subnet you can also give it a proper name and maybe even nice tags after you created it. Because you have now direct access to its nodeid. This should be a lot easier to manager.

esttri
if you have multiple nodes matching the same name you would have issues in any case.

Yeah, I'm aware of that. What I'm looking for is a solution to automatically set the path in the 'Find Node' and the node name. If the node name were a parameter, I could use the graph node's name, for example, since it's also unique.

With what you suggested, would I still have to enter the name manually? What I want is to automate/link this, because right now, I have to change it by hand every time I copy this component.

graph::AddSubnet automatically returns the NodeId so you dont need graph::FindNode anymore to find the new node. you would still want to automate the name creation for the graph::AddSubnet though, very likely with something in the realm of the string::Format callbacks to procedurally change the name. One way or anothery you simply dont get around the fact that you need to give your new node a good name. it very much depends on your preference and your current implementation though what you use to create that name.

Thank you, that's exactly what I needed.

Is there an option to set values for the inputs of this subnet (with default values)?

I connect the first two inputs, but the rest are values I want to easily access on the autorig component