"david.lloyd(a)jboss.com" wrote : - The "new tasks" list is now a list of created tasks, not assigned tasks. This should fix the problem that no tasks are being presented on the screen when a process is started having a start task and no swimlanes or assignment magic. | i would call that list the "Unassigned tasks". it's a good idea. also you could make the initiator responsible for the assignment in case a task is created without an assignment. "david.lloyd(a)jboss.com" wrote : | Also one question I have is this: when a process starts that does not have a task on the start state (and therefore, I presume, no reason to wait), should the token automatically proceed out of the start state? Right now the user must signal the token manually in this case. wether or not the process should signal automatic with the start should be in the process definition. not in the webapp. currently there is no such feature in which you can specify that the default transition has to be taken automatically when a process instance is created. for functional behaviour i don't think this is really necessary. you can always add an action on event process-start. then a developer could always turn the start-state into a wait state. but of course, this seriously limits the modeling freedom. another way to solve this is to do the same as in SEAM page flow. there you can specify an attribute initial="myStartNode" in the process-definition. that way, you are not forced to have a start-state as the initial node in your process definition. i think this would be the most elegant solution. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3997859#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...