14 Implement the UI Shell

The UI Shell is composed of four default areas: global, regional, local, and contextual, as shown in Figure 14-1.

Figure 14-1 UI Shell Areas

The basic information about the UI Shell includes:

• The shell is optimized for a screen resolution of 1280x1024 pixels.

• The four areas (refer to the circled numbers on the image) are:

  1. Global Area: The global area, across the full width at the top of the UI Shell, is static, consistent, and persistent for an individual user. It contains controls that generally affect the contents of the other three areas. See Global Area Standard Icons.

  2. Regional Area: The regional area is in the left-hand pane of the UI Shell. It has controls and content that generally affect the contents of the local and contextual areas. Tasks lists in the regional area automatically are bulleted to make it clear when a line item wraps to the next line.

  3. Local Area: The local area is in the center of the UI Shell where users do their work. It is the main work area and typically contains the transaction form with the menus and controls that enable users to be productive. Controls in, and the content or state of, the local area generally affect the contents of the contextual area.

     • Main Area: This term designates the combination of the local area and the contextual area.

  4. Contextual Area: The contextual area is in the right-hand pane of the UI Shell, with controls and contents that generally are affected by controls in, or the content or state of, the local area; although in specific cases the contextual area can also affect the contents of the local area (causing a local-area reload).

• Application designers, customers, and administrators can set the regional and contextual areas as collapsed for specific applications. End users can expand those areas at runtime.

• If there is no content in the regional or contextual area, the area is collapsed and the ability to expand it is disabled.

• The contextual area is directly bound to the local area. The application developer can bind the contextual area content to the local area such that each invocation of a local area automatically causes a relevant contextual area in the correct state to appear alongside the local area.

Creating an Oracle Fusion application also creates your application's workspace, where you will later place your page fragments and task flows. For more information about task flows, see the "Getting Started with ADF Task Flows" section of the Developing Fusion Web Applications with Oracle Application Development Framework.

For more information about starting JDeveloper, see Chapter 2, "Setting Up Your Development Environment."

To create a JSF page:

Now you can add components to the page. Table 14-1 lists the itemNode properties that can be used for a JSF page. See Working with the Applications Menu Model for how to add a menu to the page.

<itemNode id="itemNode_AppsPanelTests_TabsWA"
label="label_AppsPanelTests_TabsWA" action="AppsPanelTests_TabsWA"
focusViewId="/AppsPanelTests_TabsWA" dataControlScope="isolated">

   <af:document id="d1"
   title="#{adfBundle['oracle.apps...resource.xyzGenBundle']['Header.DefaultMain']} -
   #{adfBundle['oracle.apps...resource.xyzGenBundle']['Header.WorkAreaLabel']} -
   #{adfBundle['oracle.apps.common.acr.resource.ResourcesGenBundle']['Header.OracleApplications']}" >

When a user opens an application, he or she expects something to be displayed automatically. A task flow in the main area accomplishes this.

To add a task flow to the default Main Area:

1. Choose File > New > Web Tier > JSF > JSF Page Fragment.

   The Create JSF Page Fragment dialog shown here is displayed.

   Figure 14-11 Create New JSF Page Fragment Dialog

   

2. In the Create New JSF Page Fragment dialog:

   1. Enter a page fragment name, for example:

      The file name should follow these patterns:

      • <Object><Function>.jsff, such as PoSearch.jsff.

      • <Object>.jsff, such as PurchaseOrder.jsff.

      The page name should convey the object it presents (an employee, a supplier, an item, a purchase order, an applicant, and so on), and the function being performed (search, promote, hire, approve, view). For some pages, the object is sufficient.

      For update or create pages, just the object is necessary (unless the create and update pages are different as shown in the examples).

      Never give pages step number names, such as PoCreateStep1.jsff or PoCreateStep2.jsff. Always describe the page function, such as PoDesc.jsff or PoLines.jsff.

   2. From the Use Page Template list, select UIShellMainArea.

      Note:

      The UIShellMainArea template is only for main area task flows, not regional area task flows.

3. Click OK.

   The Local and Contextual area facets of the page fragment appear in the editor.

4. Choose File > New > JSF > ADF Task Flow to create a default task flow.

   Note:

   Most applications will have multiple task flows for the Regional, Local and Contextual areas. For instance, Figure 14-1 shows 12 task flows.

   The Create Task Flow dialog shown here is displayed.

   Figure 14-12 Create Task Flow Dialog

   

   In the Create Task Flow dialog:

   1. The file name defaults to task-flow-definition.xml. Enter a descriptive file name.

      The file name should follow these patterns:

      • <Object><Function>.xml, such as PoSearch.xml.

      • <Object>.xml, such as PurchaseOrder.xml.

      The page name should convey the object it presents (an employee, a supplier, an item, a purchase order, an applicant, and so on), and the function being performed (search, promote, hire, approve, view). For some pages, the object is sufficient.

      For update or create pages, just the object is necessary (unless the create and update pages are different as shown in the examples).

      Never give pages step number names, such as PoCreateStep1.jsff or PoCreateStep2.jsff. Always describe the page function, such as PoDesc.jsff or PoLines.jsff.

   2. From the Use Page Template list, select UIShellMainArea.

      Note:

      The UIShellMainArea template is only for main area task flows, not regional area task flows.

5. Ensure that the JSF page fragment file is selected in the Application Navigator and is displayed in the Edit view.

   1. In the Edit view, click the Source tab.

   2. Locate the line <f:facet name="localArea"/>.

   3. In the Application Navigator, select an applicable task flow, such as the one you created in Step 4, to add to the localArea. This should be an XML file located under ViewController > Web Content > WEB-INF > oracle > apps > application_name > ui > flow.

   4. Drag and drop the appropriate flow from the Navigator pane to immediately following <f:facet name="localArea"/>.

   5. From the Create menu that is displayed, select Region.

      The af:region tag is nested within the localArea facet and code resembling that shown in Example 14-2 will be inserted after it.

      In the Structure window, an af:region entry is added following the f:facet - localArea entry.

   6. Note: The instructions for the remainder of step 5 are optional. If you do not need a contextualArea, go to Step 6.

      In the Structure window, select f:facet - contextualArea.

   7. In the Component Palette, select ADF Faces > Layout.

   8. Click Panel Accordion. An af:showDetailItem entry is created automatically under af:panelAccordion.

   9. In the Source view, find and highlight the new <af:showDetailItem ...> entry.

   10. In the Application Navigator, select an applicable task flow, such as the one you created in Step 4, and drag and drop it onto the highlighted entry in the Source view.

   11. From the Create menu that is displayed, select Region.

   12. Click OK on the Edit Task Flow Binding dialog that is displayed.

       Code resembling that shown in Example 14-3 will be inserted after <af:showDetailItem ...> .

6. Now that you have created the main area page fragment, you must wrap it in an ADF task flow.

   Again, select File > New > Web Tier > JSF > ADF Task Flow and in the Create ADF Task Flow dialog:

   1. Enter a descriptive name for the task flow.

      For example, enter def_main_task-flow-definition.xml.

   2. Ensure that the Create as Bounded Task Flow and the Create With Page Fragments boxes are selected.

      Do not change the other default settings.

7. Click OK.

   The new task flow is displayed as a blank visual editor in the JDeveloper middle section.

8. In the Application Navigator, select your recently created page fragment (.jsff file), and drag and drop it onto the editor.

   The page fragment itemNode appears in the editor, as shown in Figure 14-13.

   Figure 14-13 Page Fragment itemNode

   

9. To load the menu metadata:

   Note:

   The menu data accomplishes several important jobs for you:

   • It defines properties of the page for you. For instance, it will be displayed in no-tab mode or with dynamic tabs, and define the width of the regional area.

   • It can create a task list menu for each page.

   • It can create labels for groups of tasks.

   1. In the Application Navigator, select the test_menu_taskmenu.xml file that you created using the ADF Menu Model dialog. For details about creating the menu, see How to Create an Applications Menu.

   2. In the test_menu_taskmenu.xml structure view menu tree, shown in Figure 14-14, right-click the itemNode item and choose Insert inside itemNode <task_flow_name> > itemNode.

   Figure 14-14 Task-Flow Item Node Menu Choices

   

   The Insert itemNode - Common Properties dialog, shown in Figure 14-15, is displayed.

   Figure 14-15 Insert itemNode - Common Properties Dialog

   

10. In the id field, enter a unique ID using this standard format:

    <pageID>_<taskFlowName>

    This ID example consists of the concatenated page ID (or page name), an underscore, and the task flow name, for example, ExpenseWorkArea_CreateExpense.

11. In the focusViewId field, enter the ADFc View Activity ID of the page under which you are registering the task flow.

12. Click Finish.

    The new item node is displayed in the structure view, under the menu tree.

13. With the item node selected in the structure view, click the Property Inspector tab, as shown in Figure 14-16.

    Figure 14-16 Task Flow Property Inspector

    

14. In the label field, enter a label for the task flow, such as CreateExpense.

    This label will be the title of the tab that is opened by the Task Type defaultMain.

    Note:

    Do not leave this field null. This is the label that will appear in the tab header when in a tabs page. Even if you are in a no-tabs page (see Supporting No-Tab Work Areas ), do not leave it blank because this label will be used in other ways, such as Add to Favorites, or when the system tracks the Recent Items.

15. Select test_menu_taskmenu.xml in the Project Navigator tree, and your task flow in the structure view to display its Property Inspector, or select the Property Inspector tab.

    In the Advanced section of the Property Inspector, enter the following values:

    • Task Type: defaultMain (the task flow is displayed by default whenever the page is rendered).

      The Data Control Scope should have been set to isolated, inside the task flow definition for any task flow in the menu (defaultMain or dynamicMain) or any call from openMainTask. See dataControlScope in Table 14-1.

    • Task Flow Id: ID of the task flow to be loaded.

      To enter the ID, click the ellipsis to display the Select Task Flow Id dialog, shown in Figure 14-17, and browse to the task-flow definition location. By default, following the standard naming structure, the location will be in path_to_application directory\ViewController\public_html\WEB-INF.

      Figure 14-17 Select Task Flow Id Dialog

      

      Click Open to automatically enter the location in the Task Flow field. The task flow ID is a concatenation of the file location for the task-flow definition and the task-flow name. It typically resembles /WEB-INF/MyTaskFlow.xml#MyTaskFlow. The Property Inspector for the itemNode should resemble the example shown in Figure 14-16.

16. To run the JSPX page, select the page in the Application Navigator, right-click the page file, and choose Run.

    The new page, similar to that shown in Figure 14-18, is displayed in a web browser.

    Figure 14-18 Rendered Page in Browser

    

17. Check that the newly rendered page contains one tab whose content is the task flow that you defined in this procedure.

The available itemNode properties for main area and regional area task flows for application menus are shown in Table 14-2.

<itemNode id="__ServiceRequest_itemNode_externalUrl"
   destination="http://www.yahoo.com"/>

Implementation Notes

For a dynamicMain task item that you would like to use to open the data file, there is a property called filePath in the Menu panel for the UI Shell page XML file. To enable this property in the Menu panel, during design time, the task type of the itemNode must be dynamicMain. The file URI path then should be specified against the filePath attribute in the Menu panel, as shown in Example 14-10.

You can specify any file type, such as xls, doc, pdf, txt, rtf, and ppt, that is within the application.

Example of Passing a Java Object Using openMainTask

Bind the methodParameters parameter value to a managed bean property. Example 14-15 shows the methodAction binding in the page definition of the page fragment that calls openMainTask. Also see Table 14-2.

Data control APIs are:

• FndUIShellController.openMainTask

  Note:

  When passing parameters, do not leave the label field null. This is the label that would appear in the tab header when in a tabs page. Even if you are in a no-tabs page (see Supporting No-Tab Work Areas ), do not leave it blank because this label will be used in other ways, such as Add to Favorites, or when the system tracks the Recent Items.

• FndUIShellController.closeMainTask. See closeMainTask History for more information.

To open or close a main area tab, drag and drop the appropriate data control method to create the UI functionality. Having specified the parameter values for these methods, user clicks will prompt the UI Shell to react accordingly.

To use the openMainTask data control method:

1. Expand the Data Controls and select the openMainTask item, as shown in Figure 14-19.

   Figure 14-19 Selecting openMainTask from Data Controls

   

2. Drag openMainTask and drop it onto the page fragment. When you do, the Applications Context menu shown in Figure 14-20 is displayed so you can choose one of the three options.

   Figure 14-20 Selecting an Open Option from the Applications Context Menu

   

To use the closeMainTask data control method:

1. Expand the Data Controls and select the closeMainTask item, as shown in Figure 14-21.

   Figure 14-21 Selecting closeMainTask from Data Controls

   

2. Drag closeMainTask and drop it onto the page fragment. When you do, the Applications Context menu shown in Figure 14-22 is displayed so you can choose one of the three options.

   Figure 14-22 Selecting a Close Option from the Applications Context Menu

   

Bind the methodParameters parameter value to a managed bean property. Example 14-15 shows the methodAction binding in the page definition of the page fragment that calls the openMainTask method.

Example 14-8 shows code in a managed bean for passing a hashmap to the task flow.

Then, in the managed bean of the task flow, the Java object can be read, as was shown in Example 14-9.

The testValue parameter is bound to an af:outputText value attribute, such as <af:outputText value="#{TestPanelSplitter1MBean.testValue}"/>, in the page fragment of the task flow.

Implementation Notes

• Specify the default values for the regional or main splitter position and collapsed state in the menu for the item node that represents the page, using the regionalAreaWidth and isRegionalAreaCollapsed properties. A sample entry in the menu file resembles Example 14-16.

• If these properties are not set in the menu for the top-level item node that represents the page, then these default values are used:

  regionalAreaWidth="256"
  isRegionalAreaCollapsed ="false"
  

• For programmatic control, drag and drop one of the following corresponding methods from the FndUIShellController data control.

  • discloseRegionalArea

  • collapseRegionalArea

  • setRegionalAreaWidth

Two APIs shown in Example 14-17 are exposed as data control methods under FndUIShellController data control.

Menu files will be referenced through MDS. This means they can be located in a table or in a file system directory. Determine where you want this directory to be located. This is where your root_menu.xmlfile and other menu files will be located. For Global menu attributes, see Menu Attributes Added by ().

Set Preferences

You create the actual Preferences dialog, such as shown in Figure 14-28. See How to Implement End User Preferences for the details of how to implement the Preferences menu.

Edit Current Page

This option is displayed only if the displayed page has been marked as able to be user-edited (if the isPersonalizableInComposer attribute in af:pageTemplate is set to true). Selecting this option will start the editing feature and the page will resemble Figure 14-26. Click Close to return to the page. Click Customization Manager to change the displayed page in Oracle Composer. For more information about the Customization Manager, see the Oracle Fusion Middleware Developing WebCenter Portal Assets and Custom Components with Oracle JDeveloper guide. Note that changes are for just this user and therefore are called personalization. See Creating Customizable Applications .

Figure 14-26 Edit Current Page Display

Reset to Default Content and Layout

Select this option to discard any personalization changes and return to the default settings. Note that resetting layout and content is for that page. In particular, if any task flows are personalized on that page using Oracle Composer, they are not reset by this menu item.

When you select this option, this confirmation dialog is displayed:

Figure 14-27 Confirm Reset Content and Layout

Customize [name_of_page] Pages...

Select this option to customize the current page for multiple users using the customization layer picker dialog.

For information about customization, see Creating Customizable Applications .

Customize Global Page Template

Select this option to open the page in composer mode. All the global items can be selected so you can customize them. Customization is done at the site layer so it will apply to all pages, not just the one you are on. (When you use Customize [name of page] Pages, all the content except the global content is available for customization.)

Manage Customizations...

Select this option to start the Customization Manager.

For information about customization, see Creating Customizable Applications . For more information about the Customization Manager, see the Extending Runtime Editing Capabilities Using Composer" section and the "Introduction to Composer" section of Developing WebCenter Portal Assets and Custom Components with Oracle JDeveloper.

For information about defining and configuring namespaces when promoting a page fragment to a label, see "Updating Your Application's adf-config.xml File" in the "Performing Composer-Specific MDS Configurations" section of Developing WebCenter Portal Assets and Custom Components with Oracle JDeveloper.

Manage Sandboxes...

Select this option to manage sandboxes on your system.

The Sandbox is built on top of the standard Sandbox feature from Oracle Metadata Service.

Setup and Maintenance...

Select this option to start the Oracle Fusion Functional Setup Manager application. See the Oracle Fusion Functional Setup Manager User’s Guide.

Highlight Flexfields

No separate implementation is required. This option is available to any user who has the permission to view the Administration menu.

Select this option to highlight the Descriptive Flexfields (DFF), Key Flexfields (KFF) and Extensible Flexfields (EFF) on the runtime page.

When this mode is on, the page displays an information icon by each DFF, KFF and EFF. This will be displayed whether any Flexfield segments have been configured.

Hovering over the icon shows the Flexfield details. Administrators can note the DFF, KFF or EFF code so they can search for it in the Manage Descriptive Flexfields, Manage Key Flexfields, and Manage Extensible Flexfields setup tasks in Oracle Fusion Functional Setup Manager.

The option changes to Unhighlight Flexfields so that administrators can return to the normal view of the page.

For more information about Flexfields, see Getting Started with Flexfields.

Run Diagnostics Tests

Selecting this Settings and Actions menu Troubleshooting option opens the Diagnostics Dashboard user interface in a new window. For more information, see "Understanding Oracle Fusion Applications Incidents and Log Files" in the Administrator's Guide.

Troubleshooting Options

Select this option to display the Options dialog, as shown in Figure 14-33.

Figure 14-33 Troubleshooting Options Dialog

• Enable all: Select this option to enable all other options on the dialog. When Enable all is selected, removing the selection from any of the other check boxes will deselect Enable all.

  Applications logging, severity level and modules are stored as user-level profile options in profile tables. The corresponding profile option names are AFLOG_ENABLED, AFLOG_LEVEL, and AFLOG_MODULE. See "Configuring Settings for Log Files and Incidents" in Administrator's Guide for information.

  Because applications logging, severity level, and modules are profiles, when users click Save and Close, user-specific profile values will be inserted into the profiles. If users decide to revert the setting to the default site profile, they must use the Functional Setup Manager to remove their own profile.

  After making changes to any one of the options for applications logging, severity level, or modules, the user must log out of the Oracle Fusion application, close the browser session, and log back in for the new options to take effect. These logging profiles are cached in the user session and initialized when a user logs into an Oracle Fusion application.

• Database trace: This option enables the SQL trace feature for all database connections used by the current user session.

  For SQL trace, the trace file will have the FND session ID appended to the end. For example, mysid_ora_4473_881497BF7770BEEEE040E40A0D807BB1.trc.

  The trace file can be found on the database host in the directory specified by the user_dump_dest init.ora parameter.

  • Capture bind variables:

    Select this option to enable the SQL trace option to also capture bind variables.

  • Capture wait events:

    Select this option to enable the SQL trace option to also capture wait events.

• PL/SQL profiler: This option enables the PL/SQL hierarchical profiler for all the connections used by the current user session.

  For the PL/SQL profiler, the output will be in the directory defined by APPLLOG_DIR. The exact path for APPLLOG_DIR can be found on the database host by using the SQL statement:

  select directory_name, directory_path from dba_directories where directory_name like 'APPLLOG%'

  The file names would be PLS_<some number>_<FND session id>_<timestamp>.txt, such as PLS_49774696_88740EC94E3AAD2CE040E40A0D8036D8_100607104716.txt.

  To process the collected PL/SQL profiles and view results, run the plshprof command under the $ORACLE_HOME/bin directory.

• Applications logging: Applications logging is selected by default. Disabling logging will warn users that no logging will take place.

  • Severity Level:

    Use this option to set what types of information to log, and how much of it to log.

    For more information, see "Understanding Oracle Fusion Applications Incidents and Log Files" in the Administrator's Guide.

  • Modules:

    This is the module filter for logging. This is a comma-separated list of modules to be logged. The percent sign (%) is used as a wildcard. For example, % or %financial%. The percent sign (%) is the default value and if no other value is specified, then it means everything will be logged.

    When a customer logs a service request with Oracle, the support person will help the customer enter the values necessary to filter the diagnostic logs for the needed information.

Tracing Options

This feature is designed for customers to collect diagnostic data to send back to Oracle for analysis.

When there is a performance issue that is reproducible, the tracing feature streamlines the data collection process by allowing the end user who is experiencing the problem to record a trace that will contain the necessary diagnostic information.

Before the user can access this function, the security administrator needs to assign the Business Flow Troubleshooting role to the user. On each managed server, a maximum of three users can be tracing at a time. By requiring the troubleshooting role to be granted, an administrator can grant access to users who actually need to trace, and revoke access when the issue is resolved.

To grant the role, the administrator will follow these basic steps:

• Log in to Oracle Identity Management.

• Click Administration on top right.

• Search for and select the target user.

• Click the Roles tab.

• Click Assign.

• Search for the display name Business Flow Troubleshooting.

• Select the role in the search results and click Add.

To run the trace, the user will follow these steps:

• Start the trace.

  The trace should be started only after navigating to the target managed server where the issue is happening. Note that the tracing feature only works within a single managed server; it will not span a flow involving more than one application (unless both applications happen to be on the same managed server).

  • Navigate to the target application.

  • Right before starting the problematic flow, select Troubleshooting > Tracing Options. The dialog shown in Figure 14-34 is displayed.

    Figure 14-34 Initial Tracing Options Dialog

    

  • Depending on the type of issue, select Performance or Functional trace type. The selection affects what diagnostic information is captured.

    In general, the user would select Performance when the problem is an application running too slowly, and Functional when the application does not behave as expected or when the information displayed is incorrect.

  • Trace Options defaults are based on the Trace type selection. Click Advanced Options to see what trace settings are enabled. For fine-grained control, select different trace options, as shown in Figure 14-35.

    Note:

    The user should accept the default settings or contact Oracle support for additional instructions.

    Figure 14-35 Advanced Tracing Options Dialog

    

  • Click Start Trace. A confirmation dialog, similar to Figure 14-36, with the trace ID will be displayed. Make a note of the trace ID.

    Figure 14-36 Trace Start Confirmation

    

    Subsequent clicks will be traced. The trace will run for a maximum of 30 minutes. If there are more than three simultaneous tracing sessions, an error message will be displayed.

    If the Applications Trace option is selected (enabled by default for the Performance trace type), the server also needs to have at least 200MB of free memory in the JVM heap.

• Run the flow to reproduce the issue.

• Stop the trace.

  • After executing the steps that have issues, select Troubleshooting > Tracing Options again. When tracing is active, only Stop Trace and Cancel will be active, as shown in Figure 14-37.

    Figure 14-37 Stop Trace

    

  • Click Stop Trace. Figure 14-38 shows the two options to control whether to create an incident.

    Figure 14-38 Select Stop Trace Option

    

    If the issue is reproduced, select Stop trace and create incident.

    Click OK. A confirmation will be displayed with the incident number. Note the incident number in addition to the trace ID captured earlier.

    The collected diagnostic information will be captured in an incident with the given incident number. See the "Troubleshooting Oracle Fusion Applications Using Incidents, Logs, QuickTrace, and Diagnostic Tests" chapter in the Administrator's Guide.

    If Stop trace and do not create incident is selected, then the confirmation will not have an incident number.

User Productivity Kit

The User Productivity Kit (UPK) is an optional, separately-purchased application that provides a content development, deployment, and maintenance platform for increasing project, program, and user productivity. The menu option will be available if Oracle UPK has been purchased, installed and configured.

This context-param entry must be added to the web.xml file:

<context-param>
  <description>This parameter notifies ADF Faces that the ExecutionContextProvider service provider is enabled.
    When enabled, this will start monitoring and aggregating user activity information for the client initiated
    requests. By default this param is not set or is false.
  </description>
  <param-name>oracle.adf.view.faces.context.ENABLE_ADF_EXECUTION_CONTEXT_PROVIDER</param-name>
  <param-value>true</param-value>
</context-param>
For recording, it may be necessary to turn on automation if all client components need to be sent down. The following parameter should be present in the application web.xml:
 
<context-param>
  <description>
      This parameter notifies ADF Faces that test automation is being used.
      When enabled, this will cause the ids of components with testId
      attributes to be set to the value of the testId and the client component
      attribute of the component to be forced to true.
 
      TestId attribute is now deprecated; use the 'id' attribute instead.
  </description>
  <param-name>oracle.adf.view.rich.automation.ENABLED</param-name>
  <param-value>true</param-value>
</context-param>

Also, "upk" must be provisioned by the System Administrator. That is, an entry with DEPLOYED_MODULE_NAME = "upk" must be added in the ASK deployment tables. These tables are populated at deployment time through Oracle Fusion Functional Setup Manager tasks. Without the entry, the menu item "User Productivity Kit ..." will not be shown in the Help menu.

Applications Help

Select this option to open the help system in a separate window.

Privacy Statement

Select this option to display the privacy statement, which will appear in a new browser window. This option is always inactive until it is implemented. To set up the privacy statement, enter a fully-qualified URL in the PRIVACY_PAGE profile option.

Open the Setup and Maintenance work area, and use the Manage Applications Core Administrator Profile Values task to find the Privacy Statement URL profile option. In the Profile Value column, enter the full URL of the web page that contains the privacy content you want the menu item to link to.

Also see About Setting and Accessing Profile Values.

About Applications

Select this option to display the Oracle copyright statement and information about the application.

About This Page

Select this option to display version information for Oracle Fusion Applications, including details of the Oracle Application Development Framework, Oracle Metadata Services, the database, and the Applications Core. This makes it easier to know to which product the current page belongs and makes it easy to log a Service Request or find a patch for the correct product.

Note: This information is visible only to users with specific privileges. The privileges are controlled by the profile option FND_VIEW_VERSION_INFORMATION_PRIV, which an Administrator can enable or disable.

Session impersonation is a feature that enables a user (the impersonatee) to allow other users (impersonators) to log in and act as himself without sharing his password to the other user. The impersonator can login as himself and switch to the impersonatee. Once switched, he can access all the roles of the impersonatee. This switch will be valid only for the current session; it must be done again in the next login. The impersonator can switch back to himself at any time.

To set up the impersonation, follow these steps.