Other Troubleshooting Considerations

Custom Templates

Oracle delivers unified navigation with support for PeopleTools-delivered, iframe-based templates (for example, DEFAULT_TEMPLATE and PT_IFRAME_TEMPLATE) and WorkCenter templates.

Note:

Unified navigation supports only iframe templates.

If your remote content references use custom templates or other PeopleSoft-delivered iframe templates, then those templates must conform with the following standards:

The template HTML must include the PeopleSoft header and main menu pagelets:

For example, to include the PeopleSoft header, use HTML code similar to the following:
```
<div>
    <pagelet name="UniversalNavigation">
      <source node="LOCAL_NODE" href="s/WEBLIB_PT_NAV.ISCRIPT1.FieldFormula.⇒
IScript_UniHeader_Frame?c=%Bind(:5)" /> </pagelet>
  </div>
```
In addition, to include the PeopleSoft main menu, use HTML code similar to the following:
```
 <div>
    <pagelet name="Nav">
      <source node="LOCAL_NODE" href="s/WEBLIB_PT_NAV.ISCRIPT1.FieldFormula.⇒
IScript_PT_NAV_INFRAME?navtype=dropdown&c=%Bind(:5)" /> 
    </pagelet>
  </div>
```
Important:

In both examples, the source element’s node attribute must be set to LOCAL_NODE. Otherwise, unified navigation will fail to operate on the remote content reference.
For all pagelets included in the template HTML, except for the PeopleSoft header and main menu pagelets, the source element’s node must be set to the portal host node of the content provider system:

For example, if the content provider system is PeopleSoft HRMS, set the source element’s node to HRMS as shown in the following code:
```
<div id="omtickerpagelet">
     <iframe name="NOTETICKER" id="NOTETICKER" frameborder="no" src="">
       <pagelet name="NoteTicker">
          <source node="HRMS" href="s/WEBLIB_OM.NOTE.FieldFormula.IScript_displayNoteTicker?OSEC=1&CSEC=1&PSEC=1&LSEC=1&ASEC=1"/>
       </pagelet>
     </iframe>
</div>
```

The following HTML code represents a template that has been modified to adhere to the preceding standards. In this example, the relevant portions of the code are highlighted in bold:

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/⇒
strict.dtd">
<html dir="%Direction" lang="%LanguageISO">
<head>
<meta http-equiv="X-UA-Compatible" content="IE=8">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">

</head>
<body class="PSPAGE" id="ptifrmtemplate">
  <div>
    <pagelet name="UniversalNavigation">
      <source node="LOCAL_NODE" href="s/WEBLIB_PT_NAV.ISCRIPT1.FieldFormula.⇒
IScript_UniHeader_Frame?c=var" />
    </pagelet>
  </div>
  <div>
    <pagelet name="Nav">
      <source node="LOCAL_NODE" href="s/WEBLIB_PT_NAV.ISCRIPT1.FieldFormula.⇒
IScript_PT_NAV_INFRAME?navtype=dropdown&c=var" />
     </pagelet>
 		 </div>
  <div id="ptifrmcontent">
    <div id="ptifrmtarget">
	  <iframe id="ptifrmtgtframe" name="TargetContent" title="Target_Title" ⇒
frameborder="0" scrolling="auto" onload="ptrc.onLoadTC()" src="">
        <target Name="target" params="var"/>
      </iframe>
    </div>
  </div>
  <div id="omtickerpagelet">
     <iframe name="NOTETICKER" id="NOTETICKER" frameborder="no" src="">
       <pagelet name="NoteTicker">
          <source node="HRMS" href="s/WEBLIB_OM.NOTE.FieldFormula.IScript_displayNoteTicker?OSEC=1&CSEC=1&PSEC=1&LSEC=1&ASEC=1"/>
       </pagelet>
     </iframe>
  </div>
</body>
</html>

Errors When Accessing Remote Content Through Navigation Pages

When a remote content reference is accessed through a remote navigation page, a “not authorized” error can occur even though the user is authorized to access to the content reference on the content provider system. This error usually occurs because the portal registry definition for the remote content reference uses LOCAL_NODE, instead of a specific node. Under unified navigation, LOCAL_NODE will resolve to the portal host node on the portal system, and not a node on the content provider system. Because the content reference (component and page) does not exist on the portal system, the “not authorized” error results.

To resolve this issue, you must identify and update content references on the content provider system to use the portal host node of the content provider system. In the following example for a PeopleSoft FSCM application, a SQL statement updates the node value to ERP, the portal host node:

update PSPRSMDEFN set PORTAL_CNTPRV_NAM='ERP' where PORTAL_REFTYPE='C' and 
PORTAL_CNTPRV_NAM='LOCAL_NODE' and PORTAL_NAME='EMPLOYEE';

See Completing Configuration of Remote Content.