Thanks guys. The wiki page is very helpful. It should be included inside the user guide.
The JFS based default web interface is very impressive, perform well and very neat. However, feature wise, it is not much different then the workflow engine I used three years ago - oakgrove. The idea is more like define the workflow context variables and store them as more like a key/value pair. When reaches certain state, by default show the webform with text field for each key, then kind of show buttons for each decision/transition (yes or no). Workflow engine save the context variables and move forward. Everything is driven by the tasklist shown on different user's homepage. Basic monitoring ability is provided. Good enough to simple automation or basic human interaction (e.g. approval process) workflow. However, for serious workflow, real case senario, a couple of things are missing: 1. more flexible UI control, besides text field, how about text area, drop down manual, etc. 2. better validation, not just required. 3. more important - how to store the context variables into business object and be able to query the business object through reporting. Like the web sales order sample workflow, all the variables are associated with the workflow instance, however, there's no concept of saving/creating an order business object. I think to build a generic form builder and be able to design the whole complex workflow driven web application is more like a fantasy, so hard to achieve, e.g. validation, backend validation, form processing, etc. However, there should be some better support from the workflow engine level. For example, may need some seperation between automation task and human interaction task. For automation task, it's more like run through a piece of code. The human interaction task is the self contained webform with data loading, form presentation, validation and form processing. I did not see this kind of seperation from the jBPML. Again, not sure if I am on the right track or asking for too much. You guys are definitely doing a great job, however, for my oppinion, there's a long way to go. Wish I have more time and can contribute something. For now, I still think jBPM is useful. My web application will be loosely coupled with the workflow engine. Everytime needs a decision where to go, query the jBPM engine through API. A lot of customized code. How it works, not sure. Thanks! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3937285#3937285 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3937285 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
