Like any JSF application, an application that uses ADF Faces components contains a set of rules for choosing the next page to display when, for example, a button or link is clicked. You define the rules in an ADF Faces application by adding control flow rules and cases to task flows.
JSF uses an outcome String to select the control flow rule to use to perform a page navigation. ADF Faces navigation components generate an action event when users activate the component. The JSF navigation handler and default ActionListener mechanism use the logical outcome String on the activated component to find a match in the set of control flow rules. When JSF locates a match, the corresponding page is selected and rendered.
The example in the slide shows two pages in an ADF task flow:
The BrowseOrders page has a control-flow-case whose control flow from-outcome is named showItems, defining that navigation should go to the OrderItems page.
The OrderItems page has a control-flow-case whose control flow from-outcome is named goOrders, defining that navigation should return to the BrowseOrders page.
There are two command buttons on the pages:
The BrowseOrders page has a command button whose action is set to showItems.
The OrderItems page has a command button whose action is set to goOrders.