I agree with you that it is not intuitive when you have a workflow property on a step. This happened to me on a DTS package I was given to maintain and was a real pain to find out what was going on. My solution once I found it was to just put an annotation note next to the step regarding the workflow property. After that experience, I said to myself that I would probably not use them in the future. But, after reading this article I may have to rethink that position. A simple note about a workflow property would let you know to look into the step for the code. Nice simple article.