Tom, I like that suggestion. Already we've found ourselves in a predicament in which a transition was omitted from a process, only to find out weeks later that users were wondering how to do something from where they were in the process (or we where wondering how we could retry a failed integration step after it had moved into a "manual" state, that we never thought would need to be retried). The only thing we could reasonably do was to re-point an available transition to the desired node, signal the problem processes while there was little chance of normal users being on the system, then re-point the existing transition back to its original destination. What you're proposing would give us the ability to properly insert the needed transition into the running process without cheating (like we did) or figuring out a bunch of API calls--As it is, we've already built into our own "Admin" UI the abilities to upload updated resource files (like action handlers and such) and to re-direct transitions. Maybe its good to be wary of giving this ability to the business analyst, but it sure is useful in the development department. Of the two proposals, I think the merge idea is a little more dangerous as it increases the likelyhood of introducing unintended changes. -Britt View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052758#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...