ADF Task Flow: Using Task Flow Call as Application Entry Point

Question

In our product we have a task flow structure very similar to the Fusion Order Demo application, but we are having serious trouble reproducing the documented functionality of ADF Task Flows.
Specifically, we cannot use a task flow call as an entry point for our application, which is very important for us to achieve.
The [Developer s Guide|http://download.oracle.com/docs/cd/E12839_01/web.1111/b31974/taskflows.htm#ADFFD1634] states about the [demo application|http://www.oracle.com/technology/products/jdev/samples/fod/index.html] :
"A Fusion web application always contains an ADF unbounded task flow, which contains the entry point or points to the application. Figure 14-3 displays the diagram for the unbounded task flow from the Fusion Order Demo Application. This task flow contains the Home, *MyOrders*, *checkout*, registerUser, and updateUserInfo *view activities, which are all entry points to the application*."
"The checkout-task-flow activity in Figure 14-3 is a call to an ADF bounded task flow."
When we run the Fusion Demo Application, we are only able to use home, updateUserInfo and register as entry points.
We cannot enter the application through any of the task flow call activities (MyOrders and checkout) as the documentation suggests.
What are the reasons for this and how do we fix it, so we can use task flow call activities as application entry points?
Thanks.
Edited by: Rune Glerup on Oct 9, 2009 2:51 AM
The forum did not display the link to "Developer's Guide" because the link contained the single quote char '. Single quote char removed.

Answer 1

Is what you mention here the case in the Fusion Order Demo application?
If the task flow call activities cannot be used as entry points, why is it stated in the documentation?
How do we solve this, so that the task flow call activities (including parameter bindings) can be used as entry points, like the documentation suggests?