"tom.baeyens(a)jboss.com" wrote : a wizard always relates to 1 task. the form in that case is just spread out over multiple pages. we currently don't forsee support for that in our default webapp console forms mechanism. | | getting the next task of the process if it is assigned to the logged on user is fairly easy to add to the current webapp. After a user ends a task in the task form, the webapp could check if there is a new task assigned to this user. If so, navigation could be redirected to this task form instead of the task list home page. | | does that answer the question ? I was thinking more of automatic execution of a form by an integrated mechanism (not having to wire it). I know you can do this via Seam, jBPM and pageflows. However, wouldn't it be better to have all this information defined in a single file? I mean, shouldn't this form-attached-to-a-task be part of the process definition? At this moment (and you can see it in the dvd-store example), you can have different jpdl definition files, and they seem unrelated among them, there is no unified view of your process and the forms it needs to run. Besides, it is not clear how roles apply to pageflows and forms; roles are (at this moment) related only to tasks, which is correct, but they should also be related to pageflows (IMHO). On the other hand, a single file containing all this information would be (at least for complex processes) unreadable. Considering this, a single file is NOT such a good idea. Maybe, you could have multiple diagrams/files (even sub-processes), each one describing part of your process, including any necessary pageflows. This way, you don't need a huge file, but a set of related files each one describing a part of the process. So, you could model an extremely complex project, without the burden of a complex and hard to understand file. Yet, the only requirement would be that the files were related somehow (jBPM/GPD managing these relationships), because is not so useful to have multiple jpdl files and not having a precise definition of how they relate to each other. Regarding the automatic redirect, I'm not sure if that would be a nice feature. I mean, what if you don't want to execute that task at this moment?. That?s why you have a task list, to execute tasks whenever you want. What do you think about this?. Regards. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979211#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...