When we create a task flow from maf-features.xml , only bounded task flow is created . How should we create a unbounded task flow so that it could go back to the parent task flow. And also what is the use of the adfc-mobile-config.xml unbounded task flow created automatically when we create the MAF application.
From the docs: A MAF AMX application feature always contains one unbounded task flow, which provides one or more entry points to that application feature. An entry point is represented by a view activity. By default, the source file for the unbounded task flow is the adfc-mobile-config.xml file. Consider using an unbounded task flow if the following applies:
■ There is no need for the task flow to be called by another task flow.
■ The MAF AMX application feature has multiple points of entry.
■ There is no need for a specifically designated activity to run first in the task flow (default activity).
An unbounded task flow can call a bounded task flow, but cannot be called by another task flow.
Unbounded Task Flows are there to allow you to navigate to an AMX page and then usually you will call a bounded task flow from there to do more detailed work.
I do not understand what you mean by: "so that it could go back to the parent task flow" Unbounded task flows cannot be called so not sure what you mean by a "parent" in this context. If you need to navigate back to content that resides on an unbounded task flow, you could navigate using a task flow return (from the called task flow).