In order to adapt the tank schema to a folder layout which is grown naturally, the names of certain task and step related directories don't match with names of any shotgun fields.
Also I have to defer the folder creation to when an actual task with a respective pipeline step is created, which seems to force me to use folders of type 'shotgun_step' , which are constrained to only be created if the step matches a given name. On disk, the created folder is named slightly differently though, and I would be catered best if I could just specify the name the folder should take, instead of being forced to the value of a shotgun field.
Is there a way to do that without using static folder types that I can't constrain to a $step, as there is no such folder in my schema.
Also I am not quite sure if doing so has a chance to work at all, as tank can't link tokens in the path to particular entities then, which might be required to figure out the context and entities of a path.