Skip Headers
Oracle® Beehive Release Notes
Release 1 (1.5)

Part Number E14829-08
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

10 Oracle Beehive Extensions for Outlook Notes

This module contains the following types of information on Oracle Beehive Extensions for Outlook:

Note:

As of Oracle Beehive Release 1 (1.5), the product name "Oracle Beehive Integration for Outlook" has been changed to "Oracle Beehive Extensions for Outlook".

General Notes About Oracle Beehive Extensions for Outlook

This section includes general information about Oracle Beehive Extensions for Outlook, and includes the following topics:

Accessibility of Oracle Beehive Extensions for Outlook

Oracle Beehive Extensions for Outlook has not yet been certified as meeting Oracle's standards for accessibility.

Oracle Beehive Extensions for Outlook Users Should Not Launch or Run Microsoft Outlook During the Upgrade to Oracle Beehive Release 1 (1.5)

Prior to upgrading the system to Oracle Beehive Release 1 (1.5), Oracle Beehive Extensions for Outlook users should close Microsoft Outlook and they should not launch or run that client during the system upgrade process. This will ensure that the Oracle Beehive Extensions for Outlook client software for Release 1 (1.5) is correctly applied before users start accessing the upgraded Oracle Beehive server. Otherwise, Oracle Beehive Extensions for Outlook users may experience issues reading their e-mail before the client software upgrades have been applied.

Service Pack 2 or Later Required When Running Oracle Beehive Extensions for Outlook on Microsoft Windows XP

Microsoft Windows XP, Service Pack 2 (or later) is required on Windows XP computers where users intend to run Oracle Beehive Extensions for Outlook with non-English locales. Attempting to run Oracle Beehive Extensions for Outlook with a non-English locale on a computer with Windows XP, Service Pack 1 (or earlier) may result in the computer failing to operate normally.

Known Limitations and Workarounds with Oracle Beehive Extensions for Outlook

This section contains information on the known limitations and workarounds related to Oracle Beehive Extensions for Outlook, and contains the following topics:

Discrepancies Between Certificates on Server and Client Computers Will Cause Oracle Beehive Extensions for Outlook Installations to Fail

Bug 6870456. If your Oracle Beehive server uses a self-signed certificate and only secure (SSL-based) client connections are permitted, this certificate should be added to the trusted root of all client (end-user) computers prior to installing Oracle Beehive Extensions for Outlook. Failing to do so will prevent users from installing Oracle Beehive Extensions for Outlook. In cases where discrepancies exist, users may receive an error message that indicates an invalid server or an incorrect username and password. In either case, users will be unable to continue the Oracle Beehive Extensions for Outlook installation.

Oracle Beehive Extensions for Outlook Retains Sensitivities When Documents are Added to Folders

Note:

  • This limitation is resolved in Oracle Beehive Release 1 (1.5.1.2) and later.

  • This limitation also applies to Oracle Beehive Extensions for Explorer.

Bug 8433984. When a user adds a document to a folder, Oracle Beehive Extensions for Outlook retains the sensitivity of the document even if it differs from the sensitivity of the folder. This behavior may have unintended results, especially if the intent is to move a private document to a public folder for wider distribution. If this is the case, the user would need to manually change the sensitivity of the document ("Private") to match that of the destination folder ("Public").

Oracle Beehive Extensions for Outlook Does Not Support GAL Entries Scoped at the Organization Level

Oracle Beehive Extensions for Outlook does not support Global Address List (GAL) entries that are scoped at the organization level. In other words, users or groups that are scoped at the organization level (as opposed to the enterprise level, which is recommended) will not appear in the GAL through Oracle Beehive Extensions for Outlook. To avoid this limitation, scope all user directory entities at the enterprise level. Or, alternatively, consider using another supported client.

Known Issues with Oracle Beehive Extensions for Outlook

This section contains information on the issues related to Oracle Beehive Extensions for Outlook, and includes the following topics:

Data Loss Possible when Moving Calendar, Task, or Contact Data to Team Workspaces Without Permission

Bug 6357855. If a user who does not have permission to add content to a team workspace attempts to move calendar, task, or contact data from the user's personal workspace to that team workspace, the move operation will fail (as it should). However, if the data has not yet been synchronized between the user's computer and the Oracle Beehive server, then the data will be lost.

Windows Vista Users Unable to Check for Updates for Oracle Beehive Extensions for Outlook

Bug 6872681. Users running Windows Vista without administrator privileges cannot check for updates for Oracle Beehive Extensions for Outlook. Typically, users can check for updates by clicking the Check for Updates option (from the Help>About OBEO menu). Although this option is active and, when clicked, prompts users for their credentials, no updates occur.

Delegated Users May Be Able to View Granters' Content After Delegation Privileges Revoked

Bug 8369097. If a user revokes delegation privileges previously granted to another user, the revocation may not take full and immediate effect in Oracle Beehive Extensions for Outlook. In some cases, the delegated user may still be able to view the same content (documents, e-mail, and so on) to which he or she previously had access. However, the delegated user will no longer have any former privileges, such as being able to send e-mail on the granter's behalf or being able to view new content created by the granter.