After evaluating JBPM and walking through a few use cases I have determined that the inability to quickly modify workflow instances is a problem. In classic workflow there is a workflow definition of which instances are instatiated (sound familiar - like class/object). However, it is often necessary to modify the workflow instances on the fly. For example if you have 5 chapters in which the "first draft" has to be done by technical writers before you proceed to "full document review", then you have 5 tasks in workflow which converge into a "join" in workflow which then go into a single "review entire document" task. Unfortunately, if half way through (as happens in writing) you discover you need 8 chapters, it is difficult to modify the workflow instance. This is because the workflow instance is based on a workflow def which only had 5 tasks. Basically this is a large problem. Am I missing something obvious? How could I do this in JBPM. Seems like we need a sub process that can have an arbitrary number of tasks? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4141078#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...