Working with Navigation Flows - Oracle ADF 11gR2 Development Beginner's Guide - page 184

Visibility
The opions available in this category are as follows:
URL Invoke : This will allow the bounded task flow to be called directly from a URL
link. The three properies supported are calculated , url-invoke-allowed ,
and url-invoke-disallowed . The calculated opion will allow a URL to
invoke the bounded task low if there is no iniial URL speciied.
Library Internal : Someimes we package the task low as an ADF library for
reusability. If this value is set to true , then the bounded task flow will be
considered internal to the library.
Based on a template
The opions available in this category are as follows:
Document : The template will be based on a task flow template to have standard
and common aciviies and addiional aciviies. The task low template ile is
specified for this property.
Based on Template ID : The task flow ID is provided to base the bounded task flow
on a task flow template.
Managed beans
A managed bean is similar to a backing bean, but can have higher scopes. Backing beans
are special uses of managed beans. Unlike a backing bean, the fields and methods of the
managed beans are added by the user and not all the components are ied up to a property
in the bean. A managed bean can be added to the unbounded or the bounded task flow.
pageFlowScope is just one of the scopes in ADF. To add a managed bean to the task flow,
we need to provide the three values that are mandatory:
Name : The name of the managed bean, which we will use in our applicaion
to refer to the bean object.
Class : The actual Java class that represents the managed bean.
Scope : This atribute will deine the lifespan of the managed bean object at
runime. You will see memory scopes explained later in this chapter.