Hi Brenden,
Our case was a tad peculiar. Though it was not directly that Workflow should have addressed but was part of it. Recently we build a Recipe management system using Kentico as a backend. These recipes management system is used by our client's various Test Kitchen people. These folks will experiment with a recipe and add things or two here and there. So if a recipe is under experimentation mode it will be part of a different tree structure (Test Kitchen) and will be under a different tree staructure once approved and published.
This movement of recipe was to help Test Kitchen users clearly pick a recipe. At any given time there were not many recipes in the experimentation mode. However, our client have recipes running in thousands. So it was difficult for them to identify a recipe to work on if we let all recipes remain in one tree structure.
Further, this movement of recipes is dependent on what step of the workflow recipes are in. So we wrote some custom code to handle this movement of recipes between varipus tree structure. Similarly any recipe is checked-out will go to a testing folder and will come again to it's final folder after follwoing the approval proces.
Let me know what do you think of how we could have handled it? I would love to hear any contrarian(constructive) :) view on this. It is always better to hear from experts of how they would have build things. I would be glad to share if you need anything else you need to understand how we build things.
Happy learning.
Cheers,
Chetan