Skip Headers
Oracle® Fusion Middleware Release Notes
11g Release 1 (11.1.1) for AIX Based Systems (64-Bit)

Part Number E14771-06
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

13 Oracle WebCenter

This chapter describes issues associated with Oracle WebCenter. It includes the following topics:

13.1 General Issues and Workarounds

This section describes general issue and workarounds. It includes the following topics:

13.1.1 Uploading Documents in JDev Applications

An attempt to upload a document in a Documents task flow displays an error in JDev applications that are based on one of the following templates:

  • Generic Application

  • Java Desktop Application

  • Java Desktop Application (ADF)

  • Java EE Web Application

  • Portlet Producer Application

After you add a Documents task flow onto a JSPX page in an application based on one of these templates, an attempt a upload a document from the task flow, the Upload Document page displays the message "Error: A value is required".

This issue does not occur in applications created based on the following templates:

  • WebCenter Application

  • Fusion Web Application

To work around this issue and successfully upload a document from a Documents task flow, add the attribute usesUpload="true" to the af:form component on the JSPX page.

13.1.2 Including Both Data Controls and Oracle Composer Components on a Page

If your custom WebCenter application page contains a data control and Oracle Composer components, then you may encounter an exception while using Oracle Composer at runtime. To work around this issue, include the data control inside a task flow and consume that task flow in your page.

13.1.3 Including Both ADF Data Visualization Components and Oracle Composer Components on a Page

If your custom WebCenter application page contains both ADF Data Visualization components and Oracle Composer components, then you may encounter an exception while wiring events in the Component Properties dialog in Oracle Composer. To work around this issue, you must register the DvtElementObjectFactory class with the Oracle ADF FactoryManager object. To do this, add the following code to the application class that gets loaded the earliest:

...
import oracle.adfdt.model.dvt.objects.DvtElementObjectFactory;
import oracle.adfdt.model.managers.FactoryManager;
...
static
{
FactoryManager.getInstance().registerFactory(new DvtElementObjectFactory());
}

13.1.4 Performing Actions in a Personal Space

When a personal space is disabled, the end user of the personal space cannot perform the following actions:

  • Compose a new mail

  • Perform an advanced search

  • Create a link and browse the linked object

These actions fail with an "unauthorized" error. To allow these actions, the personal space must be enabled.

13.1.5 Importing Group Spaces with Security

When you import a group space (with security), security policy updates do not apply immediately. Users who are already logged in to WebCenter Spaces need to log out and log back in to adopt the new group space security policy.

13.1.6 Renaming Group Spaces After Import

When you rename a group space that was imported from another Oracle WebCenter application, you cannot reimport that group space because the group space names on the source and target applications no longer match. You must first rename the source group space or the target group space to share the same name before attempting to reimport the group space.

13.1.7 Oracle WebCenter Wiki and Blog Limitations

In 11g Release 1 (11.1.1), the Oracle WebCenter Wiki and Blog server has following limitations:

  • Wiki pages on the Oracle WebCenter Wiki and Blog server do not support global preference settings and bi-directional languages.

  • All Web Services methods for the Oracle WebCenter Wiki and Blog server are protected to prevent unauthorized access. However, the passcode is stored as cleartext in the web.xml file of the server. It is important to properly secure web.xml and to change the default passcode upon installation of the wiki and blog server. It is also recommended that all remote Web Services calls be made over Secure Socket Layer (SSL).

13.1.8 Using the Rich Text Portlet

With 11g Release 1 (11.1.1), the Rich Text Portlet is no longer registered directly with WebCenter Spaces. To use the Rich Text Portlet in your applications, you must register it explicitly.

At runtime, if you encounter a null pointer exception while trying to customize or refresh the content of a Rich Text Portlet, then reload the page and access the options to customize or refresh your portlet.

13.1.9 Displaying Web Content in a Web Clipping Portlet

When web content is displayed in a Web Clipping portlet, any invalid HTML or JavaScript in the Web Clipping may cause a parser error message of the following format to be written to the log file:

WARNING: Error Message : Encountered "x" at line n, column n.  Was expecting one of:"x","y"..

This is a site-specific issue, not a Web Clipping error. If this occurs, contact the site's administrator for assistance.

13.1.10 Opening Announcements in the Sidebar View

With custom WebCenter applications, the Announcement Manager task flow opened from the Sidebar view opens for global announcements, even though it should open for a particular forum in the backend discussions server.

With WebCenter Spaces, the Announcement Manager task flow opened from the Sidebar view opens in a specific group space, even though it should open per the parentId parameter given in Sidebar task flow.

13.1.11 Accessing Wikis, Blogs, or Discussions from WebCenter Spaces with SAML SSO Configuration

If you set up single sign-on (SSO) by using Security Assertion Markup Language (SAML) SSO with WebCenter Spaces as the source application and Oracle WebCenter Wiki and Blog Server as the destination application, then when you access a wiki or a blog either from your WebCenter Spaces application or directly through the wiki URL for the first time in your session, the home page of the wiki and blog server is displayed instead of the requested wiki or blog. Once the session has been established, for subsequent access, the requested wiki or blog is displayed. This is due to a limitation with SAML POST profile implementation provided by Oracle WebLogic Server.

If you set up SSO by using SAML SSO with WebCenter Spaces as the source application and Oracle WebCenter Discussions as the destination application, then you can access administration pages of the Discussions application from WebCenter Spaces's Manage Group Space Services screen or Configure WebCenter Services screen. However, the administration pages of Oracle WebCenter Discussions do not participate in SSO. Therefore, if you access administration pages directly, then you are required to log in to Oracle WebCenter Discussions again.

13.1.12 Editing Wiki Pages in WebCenter Spaces Screen Reader Mode with JAWS

In WebCenter Spaces in screen reader mode, after launching JAWS, editing a wiki page that has a Type of HTML with the rich text editor is not possible. It is possible edit wiki pages with the Type wiki markup. Therefore, to work around this limitation, use the Type wiki markup (instead of HTML) when creating wiki pages to allow them to be subsequently edited in screen reader mode while using JAWS.

Additionally, the WebCenter Spaces administrator can disable the rich text editor on the Administration>Settings page (clear Support WYSIWYG Editing). Note that this will disable the rich text editor for all users.

13.1.13 Specifying a Group Space Name Parameter for IMP Service Task Flow

The Group Space Name parameter, which specifies the group space for which members should be listed, applies only to the Members task flow. If you provide a value for the Buddies task flow, it is ignored.

13.1.14 Editing the Include External Buddies Parameter for the Buddies Task Flow

Changes to the Buddies task flow affect all instances of the Buddies task flow on a page. If there is more than one instance of the Buddies task flow, editing the Include External Buddies parameter for one instance affects all other instances of the task flow on the page. Changing the value of the Include External Buddies parameter for the Buddies task flow has no effect on the list of buddies in the Sidebar. The Sidebar always lists all buddies.

13.1.15 Refreshing Buddy Presence Status in Internet Explorer 7

When users refresh a task flow that contains presence tags, the presence information changes to indicate all displayed users as offline. Other task flows on the page show the correct status. This problem is intermittent and specific to Internet Explorer 7. Either of the following options will correct the issue:

  • Refresh the page to see the correct presence status.

  • View the application from another browser. Presence information renders as expected in Internet Explorer 8, Firefox, and Safari browsers.

13.1.16 Moving the Active Cursor When Launching a New Page (Accessibility Issue)

Upon selecting a link in a WebCenter Spaces application, the active cursor does not automatically move to the content area in new non-popup/popover pages that are launched. To work around this issue, you can manually tab over to the new content area.

13.1.17 Moving Favorites Into an Existing Folder (Accessibility Issue)

When using only the keyboard in WebCenter Spaces, you cannot move a favorite into an existing folder. To work around this issue, create a new, duplicate favorite within the existing folder, then delete the original favorite that exists outside the folder.

13.1.18 Logging in to an External Application

When logging in to an external application, if you clear the Remember My Login Information checkbox, then the credentials provisioned for that user session are lost in the event of a failover in a high availability (HA) environment. You are prompted to specify the credentials again if you try to access the external application content in the same user session.

13.1.19 Migrating WSRP Producer Metadata to a New URL Endpoint

If you need to move a producer to a new URL endpoint, you can use the exportProducerMetadata, setWSRPProducer, and importProducerMetadata WLST commands to migrate the existing producer metadata to the new location. Before importing the producer metadata, you must deregister the existing producer and then re-register the producer with the new URL endpoint. If you do not re-register the producer, "Portlet Unavailable" messages display in your WebCenter application.

Follow these steps:

  1. Export the producer metadata, using the WLST command exportProducerMetadata. For details, see "exportProducerMetadata" in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

  2. Change the producer's URL endpoint , using the WLST command setWSRPProducer. For details, see "setWSRPProducer" in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

  3. Use Fusion Middleware Control or the WLST command deregisterWSRPProducer to remove the existing producer connection, as well as the producer's metadata from the WebCenter application. For details, see "Deregistering Producers" in Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

  4. Use Fusion Middleware Control or the WLST command registerWSRPProducer to reregister the WSRP portlet producer with the same name but the new URL endpoint. For details, see "Registering WSRP Producers" in Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

  5. Import the producer metadata, using the WLST Command importProducerMetadata. For details, see "importProducerMetdata" in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

13.1.20 Viewing and Participating in Discussions and Announcements

After being added to a discussions server through the Oracle Discussions Administration Application, group space members whose group space role is initially given view-only permission, then given edit permission (on the group space Settings>Role page) for discussions or announcements, will not be able to participate in discussions or announcements, despite being given edit permission. If edit permission on the group space role is revoked, the group space members granted that role are unexpectedly deleted in the Oracle Discussions Administration Application.

To give edit permission to group space members whose group space role in initially given view-only permission on discussions and announcements:

  1. On the Settings>Roles page, clear the View permission checkbox for the appropriate group space role.

  2. Click Apply.

  3. Select the Edit permission checkbox for the appropriate group space role.

  4. Click Apply.

This workaround allows group space members to be upgraded from view-only to edit permission for discussions and announcements.

13.1.21 Defining User Names in Discussions and Announcements

To allow support for non-ASCII user names in the Discussions and Announcements services, the server on which Oracle WebCenter is deployed must have the environment variable LC_ALL set to utf-8.

13.1.22 Adding RSS Feeds at Runtime

When end users click the RSS icon in a WebCenter Spaces application, the user name entered in the login dialog must contain only ASCII characters.

The RSS service does not support non-ASCII user names if the character encoding of the browser-based basic authentication is different from the character encoding of the system on which Oracle WebCenter is deployed.

13.1.23 Viewing HTML Reports, Tables, and Fonts in Mail

HTML reports, tables, and fonts viewed in a mail message may not render correctly. The Mail service requires HTML data to be well-formed to display as expected in a mail message.

13.1.24 Viewing Images in Mail

In some cases, images viewed in a mail message do not render. The Mail service requires that images use an absolute path or URL to display as expected in a mail message.

13.1.25 Purging the Metadata Services (MDS) Repository in WebCenter Spaces

In 11g Release 1 (11.1.1), the MDS Repository is not automatically purged. To manually purge metadata in the MDS repository, perform the following steps:

  1. Create a jython script named mds_purge_metadata.py that contains the following code:

    #  mds_purge_metadata.py # 
    # 
     
    l = len(sys.argv) 
    if l < 7: 
            print "Usage: $OH/common/bin/wlst.sh mds_purge_metadata.py 
    <weblogic_user> <weblogic_passwd> <weblogic url> <application name> <managed 
    server name> < time in secs> [<application version>] " 
            print " Example: $OH/common/bin/wlst.sh mds_purge_metadata.py 
    weblogic weblogic1 t3://localhost:8888 mdsapp AdminServer 30" 
            exit() 
     
    i = len(sys.argv) 
    while len > 0: 
        if sys.argv[l] == 'None': 
            sys.argv[l] = None 
        l -- 1 
     
    # Assign arguments to the variables 
     
    weblogic_user=sys.argv[1] 
    weblogic_pwd=sys.argv[2] 
    weblogic_url=sys.argv[3] 
    applicationName=sys.argv[4] 
    mserverName=sys.argv[5] 
    olderThan=sys.argv[6] 
    if i == 8: 
            applicationVersion=sys.argv[7] 
    else: 
            applicationVersion=None 
     
    connect(weblogic_user, weblogic_pwd, weblogic_url) 
    longVal=Long(olderThan) 
    value = purgeMetadata(applicationName, mserverName, longVal, 
    applicationVersion) 
     
    dateVal = System.currentTimeMillis(); 
    date = java.util.Date(dateVal) 
    print date 
    print "Metadata Purge Executed" 
    print value 
     
    exit() 
     
    # End of script ####
    

    Usage:

    $OH/common/bin/wlst.sh mds_purge_metadata.py weblogic_user weblogic_passwd weblogic url application_name managed_server_name time_in_secs [application_version] 
    

    Example:

    /scratch/AS11_11.1.1/Oracle_WC/common/bin/wlst.sh ./mds_purge_metadata.py weblogic weblogic t3://localhost:8888 webcenter WLS_Spaces 0 
    
  2. In the shell, type crontab -e cmd to open a text file in vi.

  3. Enter the following code in the text file:

    Note:

    All paths must be absolute.
    0,interval_in_mins * * * * $OH/common/bin/wlst.sh script_path/mds_purge_metadata.py weblogic_user weblogic_passwd weblogic_url application_name managed_server_name time_in_secs  >> output_log_file_path 
    

    Example:(to execute every 30 minutes):

    0,30 * * * * /scratch/AS11_11.1.1/Oracle_WC/common/bin/wlst.sh /scratch/tmp/mds_purge_metadata.py weblogic welcome1 t3://myserver.foo.com:7001 webcenter WLS_Spaces 0 >> /scratch/tmp/wc_auto_purge.log 
    
  4. Save and quit the file.

The log file contains the logs generated every 30 min, as shown in the following example:

Fri Jun 19 05:04:15 UTC 2009 
Metadata Purge Executed 
Total number of versions: 64. 
Number of versions purged: 15. 

13.1.26 Web Services Limitation in Oracle WebCenter Discussions

In 11g Release 1 (11.1.1), the Oracle WebCenter Discussions server-specific Web Services messages sent by WebCenter applications to Oracle WebCenter Discussions are not encrypted. If message confidentiality is a requirement, then the Oracle WebCenter Discussions URL must be accessed over a Secure Sockets Layer (SSL) connection.

13.1.27 Running a Custom WebCenter Application Page

If your system runs out of memory after running a custom WebCenter application page a couple of times, it is probably because some components on the page added a MaxPermSize value of 256M to the project's run/debug setting, which causes a memory allocation conflict on the server. To work around this issue, install WebCenter Framework and Services Design Time version 11.1.1.1.0.090820.0735 from Oracle JDeveloper's update center. This version overwrites the currently installed WebCenter extension version of 11.1.1.1.0.090618.1120.

The new WebCenter extension bundle does not add the MaxPermSize memory setting while creating new applications. When you migrate existing applications to the latest version using the new extension bundle, the MaxPermSize memory setting is removed.

13.1.28 Installing the WebCenter Extension Bundle

After you install the latest version (11.1.1.1.0.090820.0735), the WebCenter Framework and Services Design Time option disappears from Oracle JDeveloper's update center, until there are newer versions in the future. To work around this issue, install WebCenter Framework and Services Design Time version 11.1.1.1.0.090820.0735 from Oracle JDeveloper's update center. This version overwrites the currently installed WebCenter extension version of 11.1.1.1.0.090618.1120.

13.2 Configuration Issues and Workarounds

This section describes configuration issues and their workarounds. It includes the following topics:

13.2.1 Using Oracle WebLogic Communications Server

Oracle WebLogic Communications Server (OWLCS) is provided as a sample for development only. It should not be used for production deployments.

13.2.2 Initiating a Phone Conference with Group Space Members

If you encounter an error when attempting to initiate a phone conference with Oracle WebCenter users, ensure that usernames are lowercase. If they are not, an error may occur.

13.2.3 Viewing Group Space Output Information When Language Character Set is Unsupported

If the server on which WebCenter Spaces is running does not support the character set of the language preference set in WebCenter Spaces, the output information related to group spaces will become garbled or display as question marks. To work around this issue, end users can change the session language or the Language preference to English. This will create new log file information. The log file is typically located at $WC_DOMAIN/servers/WLS_Spaces/logs.

For more information, see "Setting a Session Display Language" in Oracle Fusion Middleware User's Guide for Oracle WebCenter.

13.2.4 Opening a Group Space with a Name Containing "I" in the Turkish Language

When browser settings control the display language, if the browser language is Turkish, WebCenter Spaces end users cannot open a group space with the letter "I" in the group space name. To work around this issue, change the default language to Turkish[tr] in the Preferences dialog in WebCenter Spaces, then open the group space.

For more information, see "Setting a Default Display Language" in Oracle Fusion Middleware User's Guide for Oracle WebCenter.

13.2.5 Exporting and Importing Group Spaces in Multibyte Languages

If end users of a WebCenter application are allowed to create group spaces in multibyte languages, with the ability to export and import these group spaces, then a group space name is restricted to alphanumeric and space characters ("a" through "z", "A" through "Z", "0" through "9", and the single-byte space character, which WebCenter replaces with "_"(underscore) ). Other characters used in the group space name will cause the export or import to fail. To enforce the naming restriction, the server on which Oracle WebCenter is deployed must have the environment variable LC_ALL set to utf-8.

13.2.6 Troubleshooting WebCenter Spaces Workflows

If you experience issues with WebCenter Spaces workflows, review the following sections:

13.2.6.1 Validating the WebCenter Workflow Configuration

The Oracle Fusion Middleware Installation Guide for Oracle WebCenter describes how to install and configure WebCenter Spaces workflows. For details, see "Back-End Requirements for WebCenter Spaces Workflows". You can validate the workflow configuration as follows:

  1. Log in to WebCenter Spaces.

  2. Create a group space and then navigate to the Members tab (group space settings).

  3. Invite a new member with any role (say User2).

  4. Log out, and then log in to WebCenter Spaces as User2.

  5. Expand Worklist in the sidebar.

  6. Open the invite notification and click the Accept button.

  7. Open My Group Spaces.

If the WebCenter Spaces workflows are working properly, the newly created group space appears in My Group Spaces for User2. If the group space is not listed, there is some issue with the configuration.

13.2.6.2 Troubleshooting Issues with WebCenter Spaces Workflows

If WebCenter Spaces workflows are not working properly, follows these steps to help troubleshoot the issue:

  1. Check that WebCenter Spaces workflows are deployed on the Oracle SOA server:

    1. Log in to Fusion Middleware Control.

    2. Check that WebCenterWorklistDetailApp.ear is deployed.

    3. Verify that sca_CommunityWorkflows_rev1.0.jar is deployed.

    See also, "Oracle SOA Server - Workflow Deployment" in Oracle Fusion Middleware Installation Guide for Oracle WebCenter.

  2. Ensure the Web Service connection between the Oracle SOA server and WebCenter Spaces is secure:

    1. Check the alias in the keystore file on the Oracle SOA server.

      For example, use the following command to list the content of the keystore file on the Oracle SOA server:

      keytool -list -v -keystore bpel.jks -storepass <password>

      There should be an entry with:

      Alias name: webcenter_spaces_ws
      

      See also, "Oracle SOA and Oracle WebCenter - WS-Security Configuration" in Oracle Fusion Middleware Installation Guide for Oracle WebCenter.

    2. Verify that the credential stores for both WebCenter Spaces and Oracle SOA server are configured correctly.

      See also, "Updating the Credential Stores" in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

    3. Check that keystores exist at both ends of the connection, for example:

      - webcenter.jks (copied to WebCenter Spaces end)

      - bpel.jks (copied to Oracle SOA server end)

      For example, the following commands generate webcenter.jks and bpel.jks:

      keytool -genkeypair -keyalg RSA -dname "cn=webcenter,dc=us,dc=oracle,dc=com" -alias webcenter -keypass mypassword -keystore webcenter.jks -storepass mypassword -validity 360
      keytool -exportcert -v -alias webcenter -keystore webcenter.jks -storepass mypassword -rfc -file webcenter.cer
      keytool -importcert -alias webcenter_spaces_ws  -file webcenter.cer -keystore bpel.jks -storepass mypassword
      keytool -genkeypair -keyalg RSA -dname "cn=bpel,dc=us,dc=oracle,dc=com" -alias bpel -keypass mypassword -keystore bpel.jks -storepass mypassword -validity 360
      keytool -exportcert -v -alias bpel -keystore bpel.jks -storepass mypassword -rfc -file bpel.cer
      keytool -importcert -alias bpel -file bpel.cer -keystore webcenter.jks -storepass mypassword
      

      See also, "Generating the Keystores" in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

    4. Configure role members for the BPMWorkflowAdmin application role in Oracle SOA server (soa-infra).

      When associating the domain with an identity store that does not contain the user "weblogic", you must assign some other valid user to the application role BPMWorkflowAdmin. Use WLST commands to do this from the SOA Oracle home, for example, to assign a user named "monty" that exists in LDAP:

      cd $ORACLE_HOME/common/bin/
      wlst.sh
       
      connect('<admin username>','<admin password>', 'mysoahost.us.oracle.com:7001')
      revokeAppRole(appStripe="soa-infra", appRoleName="BPMWorkflowAdmin", principalClass="oracle.security.jps.service.policystore.ApplicationRole", principalName="SOAAdmin")
      grantAppRole(appStripe="soa-infra", appRoleName="BPMWorkflowAdmin", principalClass="weblogic.security.principal.WLSUserImpl", principalName="monty")
      

      See also, "Security Commands" in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

13.2.7 Troubleshooting Issues with WebCenter Spaces APIs

If you experience issues with WebCenter Spaces APIs, check the following:

  1. Verify that the credential stores for both WebCenter Spaces and the client custom WebCenter application are configured correctly.

    See also, "Updating the Credential Stores" in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

  2. Ensure the group space client context is set up correctly in the custom WebCenter application by checking the alias passed in the context.setRecipientKeyAlias. The alias should be the public key alias of the producer (WebCenter Spaces), for example:

    GroupSpaceWSContext context = new GroupSpaceWSContext();context.setEndPoint(endPointUrl);context.setRecipientKeyAlias("webservice_client_api");groupSpaceInternalWSClient = new GroupSpaceWSInternalClient(context);
    

    In this example the public key alias of the producer is webservice_client_api. See also, "Setting Up the Group Space Client Context" in the Developer's Guide for Oracle WebCenter.

  3. Check that keystores exist at both ends of the connection, for example:

    - webcenter.jks (copied to WebCenter Spaces end)

    - clientapi.jks (copied to custom WebCenter application end)

    For example, the following commands generate clientapi.jks and webcenter.jks:

    keytool -genkeypair -keyalg RSA -dname "cn=webcenter,dc=us,dc=oracle,dc=com" -alias webcenter -keypass mypassword -keystore webcenter.jks -storepass mypassword -validity 360keytool -exportcert -v -alias webcenter -keystore webcenter.jks -storepass mypassword -rfc -file webcenter.cerkeytool -importcert -alias webservice_client_api  -file webcenter.cer -keystore clientapi.jks -storepass mypasswordkeytool -genkeypair -keyalg RSA -dname "cn=clientapi,dc=us,dc=oracle,dc=com" -alias clientapi -keypass mypassword -keystore clientapi.jks -storepass mypassword -validity 360keytool -exportcert -v -alias clientapi -keystore clientapi.jks -storepass mypassword -rfc -file clientapi.cerkeytool -importcert -alias clientapi -file clientapi.cer -keystore webcenter.jks -storepass mypassword
    

    See also, "Generating the Keystores" in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

13.3 Documentation Errata

This section describes documentation errata. It includes the following topics:

13.3.1 Removing Your Page Personalizations (User's Guide)

In the chapter "Organizing Your WebCenter Spaces Environment" in Oracle Fusion Middleware User's Guide for Oracle WebCenter, the section "Removing Your Page Personalizations" begins as follows:

The Reset Layout command on the Page Actions menu removes all the personalizations you made to a page.

This sentence should be revised to read as follows:

If you have Personalize privilege on the current page, the Reset Layout command on the Page Actions menu removes all the personalizations you made to a page.

13.3.2 Arranging Your Display of Worklist Items (User's Guide)

In the chapter "Working with the Worklist Service" in Oracle Fusion Middleware User's Guide for Oracle WebCenter, the last paragraph in the section "Arranging Your Display of Worklist Items" reads:

"The Worklist displays up to 25 items per Worklist server connection, with the closest due date or the most overdue retrieved first. If no due date was specified, the oldest items are retrieved first. For items exceeding the 25-item limit, follow the link to the BPEL Worklist Application, where you can view and act on a larger volume of Worklist items."

This paragraph should read as follows:

"The Worklist displays the newest created 25 items per Worklist server connection. For Worklists exceeding the 25-item limit, follow the link to the BPEL Worklist Application, where you can view and act on a larger volume of Worklist items."

13.3.3 Checking a File In (User's Guide)

In the chapter "Working with the Documents Service" in Oracle Fusion Middleware User's Guide for Oracle WebCenter, the note in the section "Checking a File In" reads:

The default maximum size for an uploaded file is 20 MB.

This is incorrect. It should read:

The default maximum size for an uploaded file is 2 GB.