Nested Template workflow

[jakubjezek001]

Is there an existing issue for this?

• I have searched the existing issues.

Please describe the feature you have in mind and explain what the current shortcomings are?

Currently, the template workflow supports nesting, but setting it up can be quite complicated. This is because there are placeholders pointing to a published backdrop product which is containing other placeholders that need to be resolved. Configuring it is not easy, and we need to find a simpler solution.

How would you imagine the implementation of the feature?

Simplification can be achieved by creating group nodes within the template and using specific placeholders that reference these groups. This means that the groups become integrated into the template, and once the template is resolved and the groups are utilized, they will be removed from the script.

Are there any labels you wish to add?

• I have added the relevant labels to the enhancement request.

Describe alternatives you've considered:

I can't think of a better alternative.

Additional context:

No response

[cuID:OP-7130]

[tokejepsen]

Think this is similar to my suggestion here about tagging loaded containers as placeholders so we can work with content in the templates rather than theoretical content.

[jakubjezek001]

closing in favour of ynput/ayon-nuke#5