Specifying Dynamic Page Layouts
Dynamic layouts streamline the application for end users by allowing them to manage only the subset of information that is relevant in a given situation. For example, your company might track several different types of accounts, such as customer-type accounts, prospect-type accounts, or partner-type accounts. With the dynamic page layout feature, you can configure different layouts that show a different set of account fields and related items, based on the type of account. You can then associate the different layouts with one or more user roles. When the user drills down on a particular account record, the user is shown the appropriate page layout, based on the user’s role and the type of account.
When you define dynamic page layouts for a record type, a pre-defined picklist value is used to drive the dynamic rendering of the page layouts. You specify a page layout to be displayed for each value of the picklist. The users can then see different page layouts for different records of the same record type, based on the picklist value that they select in the record.
You must associate your dynamic page layouts with user roles as required. There is a many-to-many relationship between dynamic page layouts and user roles.
Each picklist value has only one layout associated with it, but a page layout can be associated with multiple picklist values. There is a limit of 200 associations between picklist values and page layouts. You cannot delete a layout that is already associated with a user role.
Caution: It is recommended that all dynamic layouts associated with a driving picklist include the driving picklist. If one of your assigned layouts does not have the driving picklist, and the picklist value associated with that layout is selected and saved for a record, you will not see the driving picklist on the layout, and so you cannot edit the field.
The following table shows the predefined driving picklist values for each record type.
Page Layouts and Lists
You can use page layouts and role privileges to limit the fields that users can search, view in lists, and export. When a user creates or refines a list of records or uses advanced search to find records, the privileges and page layouts assigned to the user’s role determine which fields the user can search and view.
If the All Fields in Search and Lists privilege is enabled for the user's role, then the user can search all of the fields that are made available in the search layout that is assigned to the user's role for the record type. Also, when creating or refining a list, the user can select any field to display it as a column in the list of records that is returned by the search.
NOTE: It is recommended that company administrators do not enable the All Fields in Search and Lists privilege for most user roles. When the privilege is not enabled, fields that your company does not use are not visible in search and list pages. This reduces clutter and makes it easier for users to see the fields that they are most interested in.
If the All Fields in Search and Lists privilege is not enabled for the user's role, then the user can search a field only if it meets both of the following criteria:
Also, when creating or refining a list, the user can select a field to display it as a column in the list of records that is returned by the search only if the field is displayed on at least one of the Detail page layouts, including dynamic page layouts, that are assigned to the user's role for the record type. This restriction also affects what the user can export in a list. If the List - Export Displayed Fields privilege is enabled on the user's role, but the List - Export all Fields privilege is not enabled, then the user can export only the fields that are displayed in the list. The user cannot export all fields on the records in the list.
Before you begin. To perform this procedure, your role must include the Customize Application privilege and the Customize Application - Manage Dynamic Layouts privilege.
To create or modify a dynamic page layout
|Published 5/4/2012||Copyright © 2005, 2012, Oracle. All rights reserved. Legal Notices.|