Administering Content References

URL Information

The fields that appear in this group box are based on the selection that you make in the URL Type field.

Pagelet Attributes

The Pagelet Attributes group box enables you to manage pagelet behavior and appearance.

See Using Attributes to Enhance Pagelets.

Content Reference Attributes

Content reference attributes provide a framework to specify and store free-form information about a content reference. For example, you can use content reference attributes to specify and store keywords, help information, related content properties, and related links for content references.

In addition, portal-aware applications can use content reference attribute information for application-specific processing. Portal-aware applications are those that:

• Know about the portal registry and API.

• Know how to get information from a content reference.

• Contain code that can access the properties of content references and do something meaningful with the information.

Links

This grid appears only if content reference links that connect to this content reference exist. Click Link Definition to view the definition of each listed content reference link.

Available Content Reference Attributes

This table describes the content reference attributes that your PeopleTools portal recognizes:

Content Reference Type Parameters

This table summarizes the valid combinations of usage type, storage type, and URL type or key HTML content supported for content references:

Defining the RELLINK Content Reference Attribute

To define a related link content reference attribute:

1. Access the Content Ref Administration page (PeopleTools > Portal > Structure and Content. Navigate to the appropriate content reference; then click the Edit link.)

2. Enter RELATEDLINKS_TEMPLATE. in the Template Name field.

3. In the Name field of the Content Reference Attributes region, enter RELLINK.

   After you enter this value and move out of the field, the Attribute Information link changes to Edit Related Links.

4. Verify that the Translate check box is selected.

5. Enter a label for the related links attribute.

Creating Related Link Groups

Access the Related Links Group (PORTAL_RLNK_ADM) page.

To create a related link group:

1. In the Related Link Groups Label field, enter a name.

   This name is the heading under which you place related links.

2. To create additional related link groups, click Add and repeat step 1.

Creating Related Links

To create a link:

1. In the Related Links region on the Related Links Group (PORTAL_RLNK_ADM) page, enter a name in the Related Link URL Label field.

   This name appears as a link under the group name.

2. If you're linking to an internal site, select a node name from the list.

   If you're linking to an external site, leave this field blank.

3. In the Related Link URL field, enter URL information for the link.

   If the link is to an internal site, enter the URL or URI. The URL or URI can be to an internal site, to a portal, and so on. If you specified a value for the Portal URI Text field on the node definition, you can enter a specific document name as the target. The name is appended to the URI text for a full URL.

   If the link is to an external site, enter the URL.

4. To define additional links for the group, click Add and repeat steps 2 and 3.

5. Click OK to save the entry and return to the Content Ref Administration page.

   The Attribute Value field is populated with an XML-type formatted string. This string contains all the related link data and is stored in the PORTAL_ATTR_VAL field of the PSPRSMATTRVAL record for the content reference specified in the PORTAL_OBJNAME field. The following example shows a generated XML-type formatted string:

   <GRPLBL>Worklist Pages
   		<URLLBL>Worklist Details</URLLBL>
   		<CP>Portal</CP>		<URL>ICType=Panel&Menu=WORKLIST&Market=GBL&PanelGroupName=WORKLIST_DETAILS
   		</URL>
   		<URLLBL>Worklist Monitor</URLLBL>
   		<CP>Portal</CP>		<URL>ICType=Panel&Menu=WORKFLOW_ADMINISTRATOR&Market=GBL&PanelGroupName=WF_MONITOR_01
   		</URL>
   	</GRPLBL>
   
   	<GRPLBL>Tasks
   		<URLLBL>Task List Summary</URLLBL>
   		<CP>Portal</CP>
   		<URL>ICType=Panel&Menu=PORTAL_COMPONENTS&Market=GBL&PanelGroupName=EO_PE_TASK_LIST		</URL>
   </GRPLBL>

Testing Related Links

You should test related links to view how the page appears to users, ensure that the labels are correct, and verify that the links function properly. To test related links, click Test Content Reference on the Content Ref Administration page just above the URL Information region.

Note that:

• If the portal cache is enabled on the web server, the related link template does not appear for a content reference page accessed from the menu until the cache expires.

• Related link URLs are displayed only when a user has security access to the URLs.

  To grant security access to a related link URL, register the related link URL as a separate content reference and associate permission lists with it.

  If the related link is not separately registered, then it is treated as having public access.

  If a related link group contains no URLs to which the user has security access, the related link group is hidden. If the user does not have access to any of the related links associated with the target page, then the related links section of the template is hidden.

If the target page does not display any related links, ensure that:

• The application and portal databases are registered as content providers.

  Also check for data-entry errors.

• The templates are registered in Application Designer with the correct names.

  If the templates are registered, check for data-entry errors.

• The correct related link template is specified for the target page.

  Also ensure that the value of the PORTAL_TEMPL_NAME field in the PSPRSMDEFN record displays a correct related link template

• The RELLINK string was saved on the target page in the content registry.

  Check whether an XML string appears in the Attribute Value field on the Content Ref Administration page. If not, then delete and reenter the RELLINK attribute for all the related link information.

• You assigned security in the registry to the user for the content references listed as related link URLs.

  If not, assign security using the Content Reference Security page for registered related link URLs.

Tile Information

Use the Fluid Attributes page to configure the behavior and appearance of fluid content such as tiles, embedded related content, and related information. Certain fields pertain to tile definitions only while others pertain to all types of fluid content.

Tile Height and Width

PeopleTools supports tile sizes from 1 tile unit by 1 tile unit up to 8x8. Tile units are device dependent, which means that tiles are not actually square. The actual pixel width and height of a tile depends on the device type—either small form factor (SFF) or non-SFF as illustrated in the following table:

Dynamic Tile Content: Non-PeopleSoft URL

Use the Non-PeopleSoft URL type to display external content as dynamic fluid content.

Image: Dynamic Tile Content: Non-PeopleSoft URL

This example illustrates the fields and controls from the Dynamic Tile Content group box for a non-PeopleSoft URL. You can find definitions for the fields and controls later on this page.

Dynamic Tile Content: PeopleSoft Component

Use the URL type of PeopleSoft Component to display a fluid component as dynamic fluid content.

Image: Dynamic Tile Content: PeopleSoft Component

This example illustrates the fields and controls from the Dynamic Tile Content group box for a PeopleSoft component. You can find definitions for the fields and controls later on this page.

Dynamic Tile Content: PeopleSoft Generic URL

Use the PeopleSoft Generic URL type to display any PeopleSoft URL type as dynamic fluid content. The generic URL type can be used to define iScripts, worklists, and even component-based URLs.

Image: Dynamic Tile Content: PeopleSoft Generic URL

This example illustrates the fields and controls from the Dynamic Tile Content group box for a PeopleSoft generic URL. You can find definitions for the fields and controls later on this page.

Dynamic Tile Content: PeopleSoft Script

Use the PeopleSoft Script type to display a PeopleSoft iScript as dynamic fluid content.

Image: Dynamic Tile Content: PeopleSoft Script

This example illustrates the fields and controls from the Dynamic Tile Content group box for a PeopleSoft iScript. You can find definitions for the fields and controls later on this page.

Tile Repository

Use the Tile Repository group box to specify the category (folder) where content reference definition (or its content reference link definition) resides within the tile repository. In this regard, the tile repository refers to the portal registry subfolders under Fluid Structure Content > Fluid Pages.

Image: Tile Repository group box

This example illustrates the fields and controls in the Tile Repository group box. You can find definitions for the fields and controls later on this page.

Reviewing Content Reference Security by User

Access the User ID Queries page (PeopleTools > Security > User Profiles > User Profiles > User ID Queries).

This page contains several general-purpose security queries, along with the following links to content reference access queries for the selected user, which are described on the page:

• User ID's Content Reference Access.

• User ID's Content Reference (includes Portal) Access.

• User ID's Content Reference (includes Menu, Component and Market) Access.

• User ID's Content Reference (includes Portal, Menu, Component and Market) Access.

When you click one of the query links, a page appears in a new window, containing a grid with the information described for each content reference.

Reviewing Content Reference Security by Permission List

Access the Permission List Queries page (PeopleTools > Security > Permissions & Roles > Permission Lists > Permission List Queries).

This page is similar to the User ID Queries page, with the following equivalent links to content reference access queries for the selected permission list:

• Permission List's Content Reference Access.

• Permission List's Content Reference (includes Portal) Access.

• Permission List's Content Reference (includes Menu, Component and Market) Access.

• Permission List's Content Reference (includes Portal, Menu, Component and Market) Access.

When you click one of the query links, a page appears in a new window, containing a grid with the information described for each content reference.

Reviewing Content Reference Security by Role

Access the Role Queries page (PeopleTools > Security > Permissions & Roles > Roles > Role Queries).

This page is similar to the User ID Queries page, with the following equivalent links to content reference access queries for the selected role:

• Role's Content Reference Access.

• Role's Content Reference (includes Portal) Access.

• Role's Content Reference (includes Menu, Component and Market) Access.

• Role's Content Reference (includes Portal, Menu, Component and Market) Access.

When you click one of the query links, a page appears in a new window containing a grid with the information described for each content reference.

Target Information

Link Information

If you omit values in following fields, their values are inherited from the destination content reference:

• Label.

• Long Description.

• Product.

• Sequence number.

• Object owner identifier.

• No Template.

• Template Name.

• Valid from date.

• Valid to date.

URL Information

These fields are display-only and reflect the URL information of the content reference that you are linking to.

See “URL Information” in Defining Content References.

Content Reference Attributes

If the destination content reference has defined content reference attributes, they appear in this grid. You can copy them from the grid to the Content Reference Link Attributes group box using the following page elements:

Content Reference Link Attributes

Content reference link attributes and content reference attributes share the same page fields.

You can define content reference link attributes directly in this group box, or you can copy an attribute from the destination content reference using the Content Reference Attributes grid, and modify it to suit your purposes.

At runtime, the content reference link attributes defined here are combined with the content reference attributes defined at the link destination, and they are applied together.