I once inherited a semingly innocent 3 queue Life Cycle, that was untill I expanded the tree and ended up with over 300 unique rules and actions, nested and burried. I had to understand the entire system before I could update any logic.
I utilized MS Visio to draw out each step and document the logic. It actually only took me about an hour. I did find that much of the logic was actually not being used (it was just admin tools created by the former WF Admin under ad hoc user tasks).
I paid particular attention to the Actions Transition Document and Add/Remove Document to Life Cycle. These really worked well as inidcators for connector lines in Visio. Zooming out, I drew outline boxes around the grouped flowchart symbols to indicate queues. Going out even further I was able to group out my life cycles.
I've not found an easier way to do this. Perhaps someone else has a better method.
