Troubleshooting Page Groups Oracle Fusion Middleware Online Documentation Library

4-30 Oracle Fusion Middleware Users Guide for Oracle Portal Differentiating between page group and page properties can require a little thought when a sub-page is created directly off the page group’s root page. The settings for the page group’s root page properties are not the same thing as the settings for the page group’s properties. Page group properties are those that display when you click the Configure link next to a page group selected in the Page Groups portlet’s Work In drop-down list. They’re also displayed when you click the Properties link next to Page Group in the toolbar at the top of a page that is in Edit mode. Page properties are those that display when you click the Properties link next to Page in the toolbar at the top of a page that is in Edit mode. Some properties are common to both sets; however, those properties that are set at the page group level are potentially more widely applied than those set at the page level. I selected a default style for my page group, but new pages are not using that style. Check your inheritance rules. It could be that they are set up to inherit defaults from the parent page rather than the page group. To set up inheritance rules so that newly created pages inherit defaults from the page group, go to the Configure tab of page group properties, click the Edit link under Page Defaults , and select the radio button for Use Default Properties When Creating Page . The next time you create a page in this page group, its style default will be the same as the one set at the page group level. I have selected a default templatepage skin for my page group, but it is not the default selection for newly created pages in my page group. Check your inheritance rules. It could be that they are set up to inherit defaults from the parent page rather than the page group. To set up inheritance rules so that newly created pages inherit defaults from the page group, go to the Configure tab of page group properties, click the Edit link under Page Defaults , and select the radio button for Use Default Properties When Creating Page . The next time you create a page in this page group, it will use the default templatepage skin you have chosen for the page group. I cannot remove the page skin that is applied to my page. A page’s template options are located on the Template tab of the page’s properties. On this tab, make sure that the option Do not use a template is selected. If your page is based on a Portal Template, it could be that the template incorporates a page skin. When a page is based on a Portal Template, it inherits the templates HTML page skin if one is applied. On the pages that use the Portal Template, the templates HTML page skin cannot be removed or overridden by another HTML page skin. This means when you are editing a page based on a Portal Template, you do not have the option to choose an HTML page skin. If you want to make your own page skin selection, you must first detach the page from the Portal Template. Alternatively, if you have privileges on the template, and you’re sure all other users of this template can live with the change, you can edit the template and remove its HTML page skin. Working with Page Groups 4-31 New pages are not inheriting their access privileges from the page group as I have specified. It is likely the pages in question are based on a Portal Template. Look at the Access tab for the template’s properties. If the option Enable Pages To Have Different Access is not selected, the access rules specified for the template are being enforced on all pages using the template. In such cases, the Access tab does not display for pages that use the template. For the template, select the Enable Pages… option if you want pages that are based on the template to be able to have access rules that differ from those defined through the template. The Access link in the page toolbar on pages that use the template may not display immediately. In this case, go to pages that use the template, and enter Edit mode. Click the Page: Properties link in the toolbar at the top of the page. Click the Access tab to bring it forward. Make your changes to access settings. Be sure to click the Clear Cache link after you have made your changes. This will remove any legacy privileges from the cache, enabling newly-added users and groups to have access, and preventing newly-removed users and groups from gaining access. You may also detach the page from the template to regain control of access settings at the page level. Doing this means any additional changes made to the template will not cascade to the page from which it was detached. I do not see the Move to Shared link next to my template, page, or navigation page in the Portal Navigator. Of all the page group objects, only these three cannot be moved to the Shared Objects page group. You must create them anew within the Shared Objects page group in order to share them across page groups. For more information, see Section 4.6, Sharing Objects Across Page Groups . You can share pages across page groups by publishing them as portlets. Pages published as portlets are available to all page groups through the Portlet Repository. For more information, see Section 8.5, Placing One Page Onto Another . I have exposed my portal in both Spanish and English. I have added a file item to the Spanish version. It is also displaying in the English version. Assuming that your portal’s default language is English, any content you provide to translated versions of your portal also displays in the default language version in this case, the English version. Add an English translation of the file to the English version, and that will be displayed in lieu of the Spanish version you uploaded first. Once an English translation of the document is added to the portal in the same location, users of the English version of the portal, will see only the English version of the document. For more information, see Section 19.3.1, Adding a Translated Item . 4-32 Oracle Fusion Middleware Users Guide for Oracle Portal 5 Preparing to Add Content 5-1 5 Preparing to Add Content This chapter shows you all the different things you can do to the content in your page group to make it easier for your users to locate and work with the content. It contains the following main sections: ■ Section 5.1, Things You Can Do with Content ■ Section 5.2, Working with Attributes, Item Types, and Page Types ■ Section 5.3, Setting Up Content Classification ■ Section 5.4, Setting Up Approvals ■ Section 5.5, Managing Item Behavior at the Page Group Level ■ Section 5.6, Troubleshooting Content Management Intended Audience The content of this chapter are intended for users with at least the Manage All privilege on a page group that is, page group administrators. If a particular task requires different privileges, the required privileges will be listed before the steps of that task.

5.1 Things You Can Do with Content

Portals are all about bringing together the information that users need to do their jobs more effectively. Since managing business documents and other content is an important part of most jobs, and since the portal is the focal point for user collaboration and the logical location to publish and access business content, it only makes sense that content management features should be part of the Oracle Portal framework. ■ Oracle Portal includes several attributes, page types, and item types that are intended as a starting point for describing the content in your portal. If you find that you wish to store more information about the pages and items in your portal, you can create your own attributes and add them to page and item types. You can also create your own page and item types. See Section 5.2, Working with Attributes, Item Types, and Page Types . ■ Because of its self-service features, a portal has the potential to contain a great deal of content. To make it easier for your users to find the information stored in the portal, Oracle Portal provides the ability to classify content using categories and perspectives. Users can then search for content of a particular category for example, Sales Report, or that is written from a particular perspective for example, Sales Representative. See Section 5.3.1, Working with Categories and Section 5.3.2, Working with Perspectives . 5-2 Oracle Fusion Middleware Users Guide for Oracle Portal ■ To ensure validity of content, Oracle Portal can route content for approval before it is published on the page. Simple or multi-step processes can be defined with single or multiple reviewers at each step. Notifications are sent to each approver in the approval process indicating that action is required, while the Approval Status portlet tracks the item’s progression from the contributor’s point of view. Expiry notifications let users know about content that will expire soon. See Section 5.4, Setting Up Approvals . ■ Additional features support collaborative document creation, ease content management tasks, and make finding published items very easy. These features include item version control, check-incheck-out, publish and expiration dates, and automatic indexing. Users can also subscribe to items or pages and are notified whenever the subscribed content changes. See Section 5.5, Managing Item Behavior at the Page Group Level .

5.2 Working with Attributes, Item Types, and Page Types

Oracle Portal provides an assortment of base attributes, page types, and item types that you can expose to the user community. Each page and item type includes attributes that are used to store information about the page or item. If the base page and item types do not quite meet your requirements, you can create your own page and item types. This means that you can control what information is stored by specifying which attributes to include in page or item types. Furthermore, if the base attributes do not cover the kind of information you want to store about your pages or items, you can create your own attributes and add those to your page and item types. You can also control exactly which page and item types are made available to the users of your page groups. Oracle Portal also includes a selection of built-in extensible item types. If you do not want to create your own item types, you can edit these built-in item types to meet your requirements. This section contains the following sub-sections: ■ Section 5.2.1, Working with Attributes ■ Section 5.2.2, Working With Item Types ■ Section 5.2.3, Working with Page Types

5.2.1 Working with Attributes

There are two types of attributes: Note: One way to control the display of attributes in item regions is through the use of HTML content layout substitution tags. For more information, see Section 12.3.2, Using HTML to Define the Layout and Appearance of Region Content . Note: Any user with at least the Manage Classifications privilege on a page group can create and manage attributes and types. To edit the built-in page and item types, you must have at least the Manage Classifications privilege on the Shared Objects page group. Preparing to Add Content 5-3 Content Attributes Content attributes are associated with item types and page types, and store information about an item or page, such as the associated category, description, or perspectives. These attributes are included in the add and edit pages where users can provide information about the item or page they are adding or editing. Page group administrators can create their own item types and page types and specify exactly what information they want users to supply by choosing which attributes to include. In addition, page group administrators can create their own attributes for containing extra information. For a list of the content attributes provided by default, see Section A.2.1, Base Content Attributes . Display Attributes Display attributes are associated with regions, and display information about an item or portlet, such as the author, display name, and creation date. Page designers can choose which attributes to display in a region. Some content attributes can also be used as display attributes. See Section 10.2.9, Changing the Attributes Displayed in a Region . For a list of the display attributes provided by default, see Section A.2.2, Base Display Attributes .

5.2.1.1 Creating an Attribute

To create an attribute:

1. In the Navigator, click the link for the page group in which you want to create the

attribute. To get to the Navigator click the Navigator link on any page. By default you can find a Navigator link on the Portal Builder page.

2. Click the Attributes link.

3. Next to Create New, click the Attribute link.

4. In the Display Name field, enter a descriptive name for the attribute. The display

name is displayed as a label for the attribute whenever the attribute is used. Use up to 256 characters of any kind, except commas. When the Display Name contains one or more commas, it does not display properly in search-related attribute selection boxes. Although the attribute display name has no enforced uniqueness requirement, consider keeping it unique across your page groups. If you do not, users see duplicate names on attribute pick-lists, and are unable to determine which attribute belongs to which page group. For example, attributes display on a pick-list when a user creates a custom item type or selects custom search criteria.

5. From the Datatype list, choose the type of data that the attribute will store.

■ Boolean stores a value of 1 for TRUE or 0 for FALSE. Tip: If you create an attribute in a particular page group, that attribute is available only in that page group. If you want the attribute to be available in multiple page groups, either create it in the Shared Objects page group, or if the attribute already exists promote it to the Shared Objects page group. See Section 4.6, Sharing Objects Across Page Groups .