When users are granted full edit permissions on a page, they can use Oracle Composer and Oracle's Business Dictionary or Resource Catalog to customize the page in the following ways:
- Browse Components and Portlets: The Business Dictionary
and Resource Catalog contain components and portlets, which users can
add to their view of a page. Resource catalogs can contain items such
as portlets, layout components, task flows, documents, Oracle ADF Faces
components, business intelligence components, business activity monitoring
(BAM) components, enterprise application components, Google gadgets,
and more. To control which components are visible to users in the viewer,
developers can modify the default Resource Catalog or create one or
more of their own Resource Catalogs using Oracle WebCenter Framework
at design time. The Business Dictionary or Resource Catalog can be used
to deliver role-based views of these components. In this way, administrators
can see one view of the Resource Catalog and business users will get
a different view.
- Edit Component Properties: In addition to changing
visual properties of a component, task flow, or portlet, users can wire
two portlets together using Oracle Application Development Framework
navigational parameters. Note that you can also wire components together
using Oracle WebCenter Framework.
- Wire Components Together (Mashup Components): Users
can display a header or actions on the task flow, and wire the task
flow to a page parameter or directly to another component to create
their own mashups. For example, in an application or portal page, with
the Department and Employee task flows added to the page, a user can
edit the Employee task flow and define a parameter with a constant value
of 10. When the user clicks the Save button, the Employee table displays
details for employees with an ID of 10 only. Or, users could define
a simple expression that allows the Employee task flow to be changed
whenever they click on a different Department.
- Edit Page-Level Properties: Users can change visual
properties of the page, such as background color or page title, and
create page parameters that can be used by other components on the page.
For example, if a page contains a Sales Opportunities portlet, users
can create a page parameter for which they define a constant value,
such as "West Region". The Sales Opportunities portlet can
then be set to use this page parameter so that the portlet displays
the sales opportunities for the West Region.