"david.lloyd(a)jboss.com" wrote : I agree this is a problem. The current logic of the transition button is that if the attribute is not there, or if its value is "default", then the default transition will be taken. A value of "" will translate into a lookup for a transition named ""... this is not really optimal. | | Koen, is it possible to modify the GPD so that if there is only one transition, that the "to" attribute is not emitted? | i don't quite get the point you're trying to make. 'to' is a required attribute on the transition. only the name is optional. it should be unique in case there are multiple leaving transitions. afaik, the designer already left out the name in case there is only 1. but in case the designer should put in name="", that should work as well. mayeb the problem is in the forms.xml generation... if you want to reproduce this, just build the suite from head and create a simple new process with a start state and 1 task node. add a task to the start state. generate a minimal form for it, deploy the process, start it and end the start task. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4007955#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...