I have a similar need where I want a main pageflow who dispatches to sub-systems that have their own pageflow. At any point the parent pageflow may need to resume, make a decision, and dispatch again. Currently it doesn't look like you can transition to a completely separate pageflow from a decision node. Is this possible by programmatically starting the pageflow using the Seam API e.g perhaps an action listener begins nested pageflows? Michael View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056460#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...