"tom.baeyens(a)jboss.com" wrote : forms are not included in the process definition because they are too big. also, we moved to xhtml facelets files for forms. this adds extra customizability for the users. meaning that the gpd can create flat list forms, but the users can easily customize these forms and make the user experience better. Please pardon me, I didn't mean "include the whole form definition", but a "link" to the page (a la JSF). Of course, managed by jBPM (they way you can actually do by using pageflows, but in a single file --> process definition + pageflow definition). "tom.baeyens(a)jboss.com" wrote : it remains to be seen wether in real intranet applications, the forms mechanism will be used. for some reason or another projects always include their own UI, not leveraging the task UI included in jbpm. I agree with you, I think most developers will want their own look and feel, but I don't know if it's desireable that you need to develop/code the dependencies between tasks and forms; have you seen Carnot? I'm thinking of something like that; please take a look at http://www.carnot.ag/products/workflow/products/rad/products/rad/casabac-...). However, I think pageflows are a more powerful mechanism than just defining a single page, but an integration directly from the GPD would be nice (IMHO). Let me know what you think about this. Thanks for your time.[/url] View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979388#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...