I am working on a Jbpm project that currently has process instances active in a production evironment, but we are looking to migrate from 3.0.3 to 3.1.2.
When testing against the production data with the jbpm-3.1.2.jar in the classpath, we come across an error in the workflow. Any task that is supposed to be suspended waiting for an action from an actor is ignored. Using the production data in conjunction with jbpm3.1.2, I complete a task but instead of it continuing on and suspending at the next task needing an action, it schedules the necessary actions but is never suspended. All tasks are executed in the appropriate order until the last ending task is completed. Are there any known issues of migrating process instances versioned on jbpm3.0.3 to 3.1.2? If so, what issues need to be addressed, and if not, are there any ideas of what I can do to address this issue? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3997908#3997908 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3997908 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
