3
Oracle Calendar Release Notes

This document describes new features and known limitations of the components of Oracle Calendar, including:

3.1 Oracle Calendar Server

This section contains the following topics:

3.1.1 What's New in this Release

This release of the Oracle Calendar server includes the following new features.

Performance and Scalability:

Multiple server instances on a single computer (UNIX)
Multiple Corporate-Wide Services daemons/services
Multiple Lock Manager daemons/services
Threaded version for Solaris and HP
Small transaction optimization
Store attachments outside of event database

High Availability

Run unidbfix in check mode 24 x 7, while server is up
Run unidbfix concurrently on different nodes
Start and stop nodes while the server is running
Run unidbfix repairs on a stopped node
Allow sign-in during backups

Enhanced Administration Capabilities

Delegate administration rights
Major upgrade of Web-based Calendar Administrator
- New look and feel
- Manage users, resources, event calendars, groups, nodes and servers
Remote start/stop server capability
Utilities for controlling more attributes: uniuser (user directory attributes, reminders, user settings, inactive accounts), uniadminrights (admin rights), uniaccessrights (access rights, including designate rights) and unigroup (groups).
Single-user restore
Transfer of event ownership when deleting users
uniical utility to replace unicpin/unicpout for import/export

Directory Support

Dynamic LDAP groups
OpenLDAP
LDAP support for non-password-based authentication like GSSAPI and SASL
Reduce the number of access required to the directory

The LDAP libraries are "SSL enabled" for all platforms.

Other Enhancements (Client Support Required)

Remote designates
Replication of groups across nodes
Control double-booking on a per-resource basis
Automatic confirmed reply for booked resources (resource approval)

3.1.2 Known Limitations and Workarounds

This section describes known limitations and their workarounds for the Oracle Calendar server.

Various

Designates: After upgrading an Internal Directory installation of the Calendar server, the remote designate feature may not work. To fix the problem, run the unirnsync utility after the upgrade to replicate the necessary information to remote nodes. For more information, see "Appendix F, Calendar Server Utilities" in the Oracle Calendar Reference Manual.
Corrupted ini files: When the Oracle Calendar server is installed in multi-byte languages, the category.ini and categorytype.ini files are corrupted. To fix this issue, copy category.ini.sbs to category.ini and copy categorytype.ini.sbs to categorytype.ini. (3016058)
Missing man pages: The unix man pages do not exist for the following utilities: unirestore, unioidconf and unistrconv. However, documentation is available for these utilities in "Appendix F, Calendar Server Utilities" in the Oracle Calendar Reference Manual.
Solaris only: The C++ runtime Patch 108434-11 or 108435-11 may cause the Oracle Calendar server binaries to crash. If this occurs, it is recommended that you install Patches 108434-13 and 108435-13 or later.
Upgrade issue: During the upgrade from Release 1 to Release 2, the following value in $ORACLE_HOME/ocal/misc/unison.ini may be overridden by the old value and should be restored.
```
[CWS] 
smsnotifyprogram = <ORACLE_HOME>/ocal/sbin/sendalert 
```
may be replaced by the following:
```
[CWS] 

smsnotifyprogram = /users/unison/bin/sendalert 
```
and should be restored to:
```
[CWS] 
smsnotifyprogram = <ORACLE_HOME>/ocal/sbin/sendalert
```
Restarting a calendar node: If you stop a calendar node using the Calendar Administrator, you will not be able to restart the node using the Calendar Administrator. Workaround: Use unistart to restart.

3.1.3 Resolved Limitations in this Release

This section describes resolved limitations of the Oracle Calendar server.

You could not transfer an agenda to another user with the Calendar Administrator.
You could not manage holidays from the Calendar Administrator.
Mozilla 1.2.1 on Solaris did not display full pages.
You could not create an event calendar using the Calendar administrator.
You could not modify resource working hours using the Calendar Administrator.
You could not start and stop a server/node with the remote client.

3.1.4 Documentation Errata

UNIX man pages: Some updates were made subsequent to the generation of the Calendar server UNIX man pages. For the most current information on the Calendar server utilities, please refer to the "Appendix F, Calendar Server Utilities" in the Oracle Calendar Reference Manual.

3.2 Oracle Calendar SDK

This section covers these topics:

3.2.1 What's New in this Release

This release of the Oracle Calendar SDK includes the following new features:

Task operations (VTODO objects)
Contact operations (VCARD objects)
Corresponding Java classes with JNI (Java native interface)
Remote designate operations
Connection pooling

The inclusion of Java classes facilitates Java implementations that were previously implemented by third parties.

Connection pooling adds configuration options for the connection model used by the SDK. This greatly enhances resource usage and efficiency when implementing various applications (especially Web-based and multi-threaded environments), and promotes reuse of existing connections.

Old CAPI event functions have been superseded by newer CSDK functions. Customers already using the CAPI functions need to run the utility unifhconv on the server if they depend on any of the following iCalendar properties:

X-* (any X- property)
SEQUENCE
RESOURCES
RELATED-TO
CONTACT
URL
ATTENDEE where the attendee is a non-calendar user (e.g. invited only by their e-mail address)

3.2.2 Known Limitations and Workarounds

If a server connection is lost (for example, if the calendar service is stopped while a client is connected), the dead connection may not be released from the connection pool causing subsequent calls to fail. (2898775)

3.2.3 Resolved Limitations in this Release

The "blocking" behavior of the connection pool was disabled. Attempts to open a new server connection when the maximum number of connections (as set by max_users) has been reached did return an error instead of waiting until a connection became available. (2989379)
Connection pool error codes were incorrectly mapped to the CAPIStatus value CAPI_STAT_LIBRARY_INTERNAL_COSMICRAY. (2889348)

3.3 Oracle Calendar Application System

This section contains release note information on these products:

3.3.1 Oracle Calendar Web Client

This section covers these topics:

3.3.1.1 What's New in this Release

This section lists new features of the Oracle Calendar Web client.

The new Scheduler provides an efficient way to find out when multiple users and Resources are available for Meetings; the resource-scheduling mechanism allows hierarchical searches and automatic workflow for resources requiring designate approval. Users can also view details about people or resources.
The "Show time as free" feature allows users to accept invitations to meetings while remaining available for other invitations.
Support for Oracle Web Conferencing; users can join and create Web conferences from the Web client.
New designate functionality, including support for:
- Resource designates
- Event calendar designates
- Remote designates
Changes made to notification and wireless preferences are applied to calendar desktop clients.
Ability to set default reminder settings for Meetings, Daily Notes and Day Events.
Support for 24-hour meetings.
A link to the Calendar Administrator from the global toolbar (for users with Server Administration rights).
Ability for users to set the hours displayed in the daily or weekly view.
Support for additional languages, including Danish, Dutch, English, Finnish, French, German, Greek, Italian, Japanese, Korean, Norwegian, Brazilian Portuguese, Portuguese, Swedish, Spanish, Simplified Chinese, Traditional Chinese and Turkish.

3.3.1.2 Known Limitations and Workarounds

This section describes known limitations and workarounds for the Oracle Calendar Web client.

File attachments:
- After uploading a file to the server, if the user closes the browser window instead of clicking OK, the file will remain in the server's temporary directory. (2973763)
- The temporary directory used on the server should be changed to one that is write-accessible, namely, <ocas>/tmp instead of <ocas>/bin. (2973833)
- When viewing someone's agenda with full viewing rights and attempting to open an attachment to a meeting, a security violation error message appears. (2983094)
Establishing a master node connection: When a slave node is unavailable, the Oracle Calendar application system may have difficulties establishing a connection to the master node. Workaround: Set openallnodes = FALSE in the [Connectionconfig] section of the ocas.conf.
Wireless reminder option: In Entry Default preferences, the wireless reminder option is available even when wireless preferences are disabled. (2975055)
Netscape/Mozilla issues:
- Some error messages may not appear in Netscape or Mozilla after an incorrect action is performed. Also in this case, a reload must be done in order for the buttons and links to work. (2978866)
- Netscape 6.2: In order to print an agenda properly, the margin size must be set to one inch under Web client Display Preferences. (2861543)
- Netscape 6.x: The "Return to Previous" link in some error pages does not work. This is a Netscape issue. (2981030)
- Mozilla 1.x: Users may experience display problems and erratic behavior. (2847384)

Redirect issue: This line (in $ORACLE_HOME/ocas/conf/ocal.conf) will not redirect the client properly, since Alias only works for the location portion of a URL (up to the question mark):

 Alias /calendar    \
       "/private1/oracle/middletier/ocas/bin/ocas.fcgi?sub=web"

Instead, use the following:

 <Location /calendar>
   Redirect permanent /calendar \
           http://<host>:<port>/ocas-bin/ocas.fcgi?sub=web
 </Location>

(2982922)

Reminder lead time: When a user tries to set a reminder lead time greater than the server's maximum allowed value, the lead time is automatically reset to the server's maximum value without warning. (2980094)
Multiple installations of the Oracle Calendar Web client: Each Web client installation only supports calendar server nodes with common settings. To support a calendar server node with different settings, you must install another instance of the Web client.
Upgrade issue: Blank lines in ocas.conf and ocwc.conf in your R2 installation will be removed by the Upgrade Assistant. To preserve them, replace them with "#" prior to running the Assistant.

3.3.1.3 Resolved Limitations in this Release

This section describes resolved limitations of the Oracle Calendar Web client.

When editing or deleting events, e-mail notification was not sent, even if it was set to do so in preferences. (2907433)
Resource conflicts were not properly checked when resource designates issued approval, unless resource approval was set up after the Calendar server was installed. (2906858)
A resource designate would be asked to sign in after clicking a resource approval link, unless the resource was already signed in. (2907487)
"Show time as" functionality was described in the online Help even though it was not implemented in the release. (2907123)
The Scheduler page had changes made that were not reflected in the online Help. (2907159)
Adding a group to an entry could cause an error if you were acting as a designate, picking a group from a search results list, or adding an LDAP group or group you didn't create. (2852128, 2859436, 2901674, 2906654)
Entering a number followed by a space in a text box where a numerical value is required (such as the "repeat for" text box) could cause an error. An error could also occur when creating a new group and entering the new name with an extra space -- the group would not be created. (2844834, 2894371)
When a remote user was invited to a meeting, the meeting owner's status was not correctly displayed to the remote user. The owner's status would be shown as "will confirm later" instead of "will attend". This was a server issue. (2892157)
Two or more users with the same name could not sign on, even if they had different passwords. (2899249)
Line breaks were not shown in the Details section of Meeting entries.
When the first instance date of a Repeating entry did not match the default date on the General page, the default date would not be updated to reflect the Repeating date.
The Calendar Portlet page would return the message, "This service is currently unavailable, please try later," when a user had Daily Notes or Day Events scheduled for the current day and had set the calendar display preferences to not display declined meetings.
Internet Explorer 5.x Macintosh only: If the default start and/or end time in the Group View was changed and then a search for a group was performed, a "No Response from Application Web Server" page appeared.
Netscape 7.x only: Margins of one inch had to be set in order for the Printer-friendly format feature to work correctly.
The hour set in the "From" and "To" times in the Deliver reminders and notifications field in the Wireless section of the Edit Preferences page had to be greater than or equal to one. For example, using 0hr 00 min would result in an error. This was only an issue when the 24-hour display format is used.
Edit Access Rights Page: If the g: or r: prefixes were used when performing a search from the Edit Access Rights page, misleading error messages would appear.
When 12:00 p.m. was selected from the drop-down box on the Suggest Time page, 12:00 a.m. was set in the General section of the Entry Modification/Creation pages. This was only an issue when using the 12-hour time format for the Web client.
Internet Explorer 5.1 Macintosh only: When clicking Suggest Time from the Create/Modify Meeting page, the Suggest Time dialog box would open behind the main page.
When setting values for the Print section of the Preferences page, using a value greater than 3 for the Margin setting would cause the Web client to freeze.
Creating New Groups: You could only add an existing Group to a new Group by either entering a specific group name in the Search field and clicking Find, or by selecting the Groups radio button and clicking Find.
You could not upload attachments with titles longer than 41 characters.
Suggest Time Feature: Entering 24 in the Time between fields of the Suggest Date & Time page resulted in an Internal Server error. This only occurred when using the 24-hour time format.
Whenever the Oracle Calendar server was restarted, the midtier Oracle HTTP Server had to be restarted as well.
Internet Explorer 5.x Macintosh only : If the default start and/or end time in the Group View was changed and then a search for a group was performed, a "No Response from Application Web Server" page would appear.
Solaris only: The Return to Portal link at the bottom of the Web client pages would not function properly.
The "Show time as" drop-down menu appeared to be available when it should not have been. (2978497)

This section describes resolved limitations in the Oracle Calendar Web client online Help.

Translated versions of the online Help:
- Setting default reminders is now described. (2948693)
- For ADA versions, in the Display Preferences section under Setting Your Preferences, the Help explained that you could select the hours of the day you want displayed in your Daily View, but this does not apply to ADA mode. This sentence has been removed. (2949389)

3.3.1.4 Document Errata

This section describes known issues in the Oracle Calendar Web client online Help.

Device settings in standalone: When using Web client standalone, you can edit the following device setting preferences, which are not described in the Help:
- Notification of Entries in plain text format or as notes in your calendar display on your mobile phone.
- Mobile device alarm.
- Preferred service center number.

3.3.2 Oracle Calendar Web Services

This section covers these topics:

What's New in this Release

3.3.2.1 What's New in this Release

This is the first release of Oracle Calendar Web services, the newest component of Oracle Calendar. Oracle Calendar Web services allows applications to retrieve, through common XML queries, calendar data for display in any portal, client application or backend server. Developers can use the Oracle Calendar Web services toolkit, included with Oracle Calendar, to build Web services applications and create SOAP queries.

3.3.3 Oracle Sync Server

This section contains the following topics:

3.3.3.1 What's New in this Release

Oracle Sync Server is a new component of Oracle Calendar that allows you to synchronize data with any SyncML-compliant device using a standard Hypertext Transfer Protocol (HTTP) connection. Sync Server uses SyncML, the open standard for synchronization backed by the Open Mobile Alliance. With a SyncML-compliant device and Oracle Sync Server, you can synchronize calendar data, to-do lists, contact information and other relevant data across multiple networks, platforms and devices.

3.3.3.2 Known Limitations and Workarounds

This section describes general issues and their workarounds for Oracle Sync Server 9.0.4.

Ericsson R520m, T39, T68, Sony Ericsson T68i:
- Missing resource names: When the attendeesindetails parameter on the server is set to "short," resource names and statuses in event details are not synchronized to a device. This is because truncated resource names are not meaningful to users. Resources are only added to event details when attendeesindetails is set to full. (2922093)
- Missing dash in phone number: The device does not store formatted phone numbers. All non-numeric characters other than "#" are removed when phone numbers are stored on the device. (2845256)
- Missing or modified e-mail addresses: The device can store one e-mail address for a contact, while the server can store two. If a contact's e-mail address is modified on the device and synchronized to the server, it is possible that the wrong address on the server will be updated. This is because there is no way at this time for the server to detect which address is supposed to be updated.
- Missing organization field: The device can store one organization field for a contact, while the server can store two. If a contact's organization field is modified on the device and synchronized to the server, the information in both server fields is discarded in favor of the field synchronized from the device.
- Siemens S55: Memos created on the Siemens S55 synchronize as Daily Notes on the server. (Other phone devices synchronize Memos as Day Events.) (2962661).

3.3.3.3 Device-Related Issues

This section describes issues encountered by Oracle Sync Server due to the behavior of the Sync-ML client software installed on the following devices.

Nokia 3650:
- The Sync-ML client always assigns a due date for tasks. When tasks with no due date on the server are synchronized to the device, they will be given the current date as the due date. (2870062)
- Task priorities are mapped between the device and server as follows:
  
  Device Server
  
  High
  
  1
  
  Normal
  
  2
  
  Low
  
  3-9, A-Z
  
  (2842037)
- Unable to synchronize tasks created using the Oracle Calendar desktop client with the phone device. Phones that synchronize tasks and events using the same phone database MUST use "./Calendar" as the server URI. However, phones that synchronize them separately MUST use "./Calendar/Events" and "./Calendar/Tasks" as the respective URIs for the device's events and tasks databases. (2956318)
Nokia 3650 and 92xx:
- Changes to an entry's Access Level on the server are not synchronized to the device. However, a new entry's Access Level will be correctly synchronized from the server to the device the first time. (2839895)
- Unable to synchronize Business and Home addresses from the Oracle Calendar desktop client to the phone device. (2839242)
- E-mail addresses synchronized from the server to the device get reversed; that is, E-mail address 1 becomes E-mail Address 2, and vice versa. (2839795)
Nokia 3650, Nokia 7650, Nokia 92xx, Sony Ericsson T68i: The "completed" property for tasks is not supported. Tasks marked as completed on the server cannot be marked as completed on the device. (2909625)
All Nokia Devices, Sony Ericsson P800: These devices do not allow you to change their time zones. If you are travelling across time zones, it is best to avoid synchronizing until you return. However, if you must synchronize, only do so if your account on the Calendar server remains set to the same time zone as your device.
Nokia 92xx: Unable to synchronize with the Nokia 9290 phone device when KeepAlive=ON (default value set by the Collaboration Suite installation). (2862018)
Ericsson T39, T68, R520m: Task synchronization is not supported. (2909625)
Ericsson R520m, T39, T68, Sony Ericsson T68i, Siemens S55: When travelling, it is recommended that you set your device to the same time zone as your Calendar account before synchronizing.
Ericsson R520m, T39, T68, Sony Ericsson T68i:
- Contact's full name becomes a last name: The correct way to enter contact names on the device is "Lastname, Firstname". Names entered on, or synchronized to, the device without a comma will be stored on the device as last names only. (2844373)
Ericsson R520m:
- The Ericsson r520m has a limit of 150 characters in its event details field. Attendee information that exceeds 150 characters is not added to the details field. It is best to use the default server parameter of AddAttendeesInDetails = short with this phone. (2862247)
- When you create an untimed event using the device, the Daylight Savings time change can cause it to be displayed as a Meeting with a duration of 1 minute on the Oracle Calendar desktop client. (2864097)
Ericsson T68i:
- When a contact's e-mail address is modified using the phone device and contains special characters, it appears to be corrupt on the Oracle Calendar desktop client. This occurs because the phone device does not return the EMAIL vcard property in the appropriate format. (2844777)

Device	Server
High	1
Normal	2
Low	3-9, A-Z

3.3.3.4 Resolved Limitations in this Release

Modifying contact information using the phone device resulted in truncated fields on the Oracle Calendar desktop clients because the maximum character length allowed varied depending on the phone device's limitations. (2844930)

3.4 Oracle Connector for Outlook

This section contains these topics:

3.4.1 What's New in this Release

This section lists new features of Oracle Connector for Outlook.

Out of Office Assistant and Server-side e-mail rules.
View mail server quota usage.
New e-mail, voice mail and wireless preferences.
Ability to recover e-mail deleted from one or more folders for a specified period of time.
Schedule and join Oracle Web conferences through Microsoft Outlook.
New enhanced resource scheduling functionality.
Prompt for language choices when upgrading from a previous version using the /Lang command-line switch.
Assign delegate access to remote node users.
Access to complete (Calendar and non-Calendar) user directory backing the Calendar server.
Ability to resolve names against OiD distribution lists.
Reduction in number of IMAP4 and calendar API commands issued to implement frequently performed Microsoft Outlook operations
Master Node Configuration to auto-detect Calendar server account.
Local Mailbox Caching - ability to use a local copy of IMAP4 e-mail while working online.
Ability to configure folder count refreshes.
The ability to control whether the delegate name appears as "on behalf of" the folder's owner when sending messages.
The ability to automatically notify the Calendar owner when a delegate adds a meeting to the owner's Calendar.
Optimizations to the Outlook Advanced Search functionality when looking for e-mail recipients, meeting organizers and attendees.
Support for additional languages, including Danish, Dutch, English, Finnish, French, German, Greek, Italian, Japanese, Korean, Norwegian, Brazilian Portuguese, Portuguese, Swedish, Spanish, Simplified Chinese, Traditional Chinese and Turkish.
Sender's e-mail address is not included when doing a Reply to All.
Users are warned and prevented from sending e-mail messages larger than the maximum size allowed by the SMTP server.
Outlook can perform other tasks while sending large e-mail messages.
Non-delivery reports include the reason for failure of the SMTP server.
Ability to send and read S/MIME encrypted e-mail messages with Entrust Express (6.0, 6.1 and 6.1 SP 1) digital certificates.

3.4.2 Known Limitations and Workarounds

This section describes known limitations and workarounds for Oracle Connector for Outlook.

Client-Side Rules Wizard: To specify a person using the Outlook Client-Side Rules Wizard, you must provide both the user's display name and e-mail address separated by a semi-colon in order to have the rules trigger on messages received from that person. (3117097)
Synchronization: Synchronizing the Pocket Outlook 2002 Inbox using ActiveSync 3.5 with Outlook 2000 will result in unresolved items. (2932027)
Web conferences: Due to an Outlook 2000 limitation (Microsoft Knowledge Base: 272320), Outlook 2000 users require at least Office 2000 Service Pack 3 to correctly display an instance of a recurring Oracle Web conference. (2927339)
IMAP server: When using an IMAP4 server that does not support authenticating via Simple Authentication and Security Level (SASL), such as Oracle Email Server, it is recommended that you enforce Secure Sockets Layer (SSL) for all connections to your IMAP4 server to avoid sending passwords in clear text. Consult your e-mail server documentation for more information. For details on setting up Oracle Connector for Outlook server connections with SSL, see the Oracle Connector for Outlook online help.
Oracle Connector for Outlook does not change the core functionality of Microsoft Outlook/Exchange, however, the following are some examples of Outlook features that are not supported in this release.
- Unsupported formats/attachments: Oracle Connector for Outlook does not support Transport Neutral Encapsulation Format (TNEF) in e-mail messages, or winmail.dat attachments sent by Microsoft e-mail clients. (3117510)
- Microsoft POP3 service provider: Oracle Connector for Outlook cannot be installed in the same profile as Microsoft's POP3 service provider.
- Group By option: Custom folder views using the Group By option are not supported. Suggested workaround: Set the Group By field to none. (3117194)

3.4.3 Resolved Limitations in this Release

This section describes resolved limitations of Oracle Connector for Outlook.

Reading an incoming e-mail while it was being moved to another folder by an Inbox rule could result in the message being duplicated in the destination folder. (3117313)
If an open message was moved immediately after replying, a copy of that message would remain in its original location. (3117325)
Outlook 2000 on Windows 98 only: When working in another user's Calendar folder, you could not create a new meeting by simply highlighting a time and typing directly in the cells. (3117338)
When a remote user was invited to meeting, the meeting owner's status was not correctly displayed to the remote user. The owner's status would be shown as "will confirm later" instead of "will attend". This was a server issue. (2892157)
Ability to synchronize Notes and Ink Notes with Pocket PC devices.
Ability to synchronize off-line folders without first visiting them. (3117210)
Long delays were experienced at the end of the Oracle Connector for Outlook installation.
Upgrading Oracle Connector for Outlook or purging the off-line folders resulted in PST files getting deleted. (2692841)
Meetings created with attachments (Word, Excel) using an Oracle Calendar desktop client did not show the attachments when the same meeting was viewed from Microsoft Outlook XP. The attachments could be seen properly on Microsoft Outlook 2000. (3117299)
Recurring Meetings or Show Free/Busy information could not be displayed correctly if user did not have full administration privileges. (2666117)
Users with rights to manage Holidays could inadvertently delete Holidays for everyone through Outlook.
Client-side rules to move all e-mail to personal folders resulted in another, empty e-mail. (2662010)
Moving an e-mail from Oracle Connector for Outlook to a target PST folder did not delete the source message. (3117236)
Canceling a move of multiple messages from the Oracle Connector for Outlook to a target PST folder deleted the source messages. (3035337)
The time displayed in the Reminder pop-up window on Outlook XP displayed the reminder time instead of the meeting's start time. (3117709)
Synchronization with Chapura's PocketMirror did not work. (306227)
The "Work Offline" toolbar button did not work. (3101189)
Italian only: There were two "Client Rules" menu items on the "Tools" menu. (2985603)
Could not create/send e-mail messages to a distribution list embedded within another distribution list. (3028635)
If you created a group using the Group Scheduling feature, the group would not be saved after you exited Oracle Connector for Outlook. (2943564)
You could not access the second voice mail from a forwarded message that also included a voicemail from the person forwarding the message. (3057009)
Specifying X400 name for a Calendar account name instead of a UserID against a 9.0.4 masternode Calendar server resulted in bad behavior. (3101153)
E-mails received from Oracle Email 9.0.3 Auto-Reply had missing text. (3040699)
Work Offline/Work Online feature did not refresh the message in the Preview Pane. (3100989)

3.5 Oracle Calendar Desktop Clients

This section contains release note information on these products:

3.5.1 Oracle Calendar Desktop Client for Windows

This section contains these topics:

3.5.1.1 What's New in this Release

This section lists new features of the Oracle Calendar desktop client for Windows.

Support for e-mail to remote resources.
Ability to access remote groups.
Enhanced user interface for the agenda search.
Support for meetings greater than 24 hours.
Perform conflict checking on a per resource basis.*
Improved address book: Ability to create a repeating note entry from a birthday or anniversary date, ability to launch an e-mail application from an address book entry's e-mail address, ability to launch the browser from an address book entry's URL.
Support passwords longer than 15 characters.*
Enhanced resource scheduling*
The "Show time as free" feature -- allows users to accept invitations to meetings while remaining available for other invitations.*
Support for German and Japanese.

* Requires Oracle Calendar Server 9.0.4

3.5.1.2 Known Limitations and Workarounds

This section describes known limitations and workarounds for the Oracle Calendar desktop client for Windows.

iCalendar import: When attempting to import an iCalendar file to an external calendar product such as Microsoft Outlook, only the first entry in the file is imported correctly. To work around this issue, you should export/import your Agenda data in vCalendar format instead. (2859449)
VCS import: Importing .vcs files from some programs may not work properly. (2836621)
Japanese Address Book: The Japanese version of the Oracle Calendar desktop client for Windows does not support Address Book functionality.

3.5.1.3 Resolved Limitations in this Release

This section describes resolved limitations of the Oracle Calendar desktop client for Windows.

When you have new entries in your offline agenda, selecting Download To Local File did not properly reconcile the agendas. (2896226)
When attempting to print your Agenda while having a Designate Agenda window open, the system occasionally printed the Designate Agenda rather than your own. (2836683)
When attempting to print your Agenda with the time range set to span 24 hours, the application reverted to the default time range (08:00-17:00) instead. (2859640)
Downloading your agenda to a file after changing your password caused errors. (2912923)
When a remote user was invited to meeting, the meeting owner's status was not correctly displayed to the remote user. The owner's status would be shown as "will confirm later" instead of "will attend". This was a server issue. (2892563)

3.5.2 Oracle Calendar Desktop Client for Macintosh

This section contains these topics:

3.5.2.1 What's New in this Release

This section lists new features of the Oracle Calendar desktop client for Macintosh.

Support for GSSAPI Kerberos.
Better encryption in off-line database.
Daily Notes and Day Events now support details and attachments.
Open a Group View containing the agendas of the people invited to a particular Meeting by pressing the CTRL key while clicking on a Meeting and selecting Open Group View.
The redesigned Event Editor lets you quickly create and edit events within a single dialog box. With this new organization, adding an additional date to your Meeting is now achieved with a single click. The number of attendees for confirmed and unconfirmed meetings can be viewed. The Repeating Meeting dialog has also been redesigned to simplify the process of creating repeating meetings.
All user preferences are now centralized and organized in a new Preferences dialog. With this dialog, users can modify the defaults of all configurable preferences related to settings for their Agenda display, In-tray display, Entry defaults, Scheduling choices, off-line set up, Address Book organization and a number of General preferences including date, time zone, and startup settings.
With the new on-line Address Book, you can now manage all your Address Book Entries from one location, and create categories to make your contact management easier than ever before.
A new installer allows users to easily install the application. A pre-configuration file is provided for silent installation.
The redesigned toolbars, updated default color schemes and reorganized menus give Oracle Calendar a new look and feel.
Customize Meeting colors according to any scheme, to fit your desktop or preference.
You can save the state of your windows at any time so that Oracle Calendar opens in exactly the state you choose.
E-mail notification of events now includes the title of the event in the subject field.
When you modify or delete instances of a repeating Meeting, only affected instances will be listed in the mail message.
When you modify or delete instances of a repeating Meeting, by default only invitees for the affected instances will be notified by e-mail.
Reminders are now available via e-mail and wireless.
Support for meetings greater than 24 hours.
Perform conflict checking on a per resource basis.*
Improved address book: Ability to create a repeating note entry from a birthday or anniversary date, ability to launch an e-mail application from an address book entry's e-mail address, ability to launch the browser from an address book entry's URL.
Support passwords longer than 15 characters.*

* Requires Oracle Calendar Server 9.0.4

3.5.2.2 Known Limitations and Workarounds

This section describes general issues and their workarounds for the Oracle Calendar desktop client for Macintosh.

Sign-in:
- After configuring a master-node server for a specific user, the user name displayed in the Sign-in dialog is that of the previously signed-on user instead of the indicated user. (2864234)
- Attempting to sign-in to the application with a valid password containing a Euro character will fail. (2871974)
- Signing in to your agenda off-line may not always work. For instance, it is known that in the off-line configuration dialog box, if you select a different time zone and then try to sign in, you will simply be returned to the sign-in dialog box. (2893984)
Notifications:
- The pop-up notification for new entries feature does not work. (2872763)
Windows: When switching back and forth between Oracle Calendar desktop client for Macintosh and other applications, the Oracle Calendar windows appear in the foreground but remain grayed out as though they were still in the background. (2893976)
Repeating events:
- Trying to apply a change in Reply status to all instances of a repeating meeting may not work. (2884186)
Printing: When you click Print from the New Group dialog when there is no default printer set up on your system, a message is displayed asking if you wish to set up a printer. Clicking Cancel yields the following unexpected error: Module: <CST_ManageGroupsDlog.cpp>, Label: 125, Service error: 0x31002. (2842273)
Address Book:
- Address Book categories do not function correctly. (2830426, 2879849)
- If you leave your address book open while upgrading, your data may not appear to have been migrated properly. Just click on the address book icon from the toolbar to see your updated entries. (2911972)
- Creating a Daily Note from the Address Book while working off-line may not work. (2921488)
- Exporting the address book to tab-delimited/comma-delimited text files does not work. (2924992)
Duplicate Meeting: The Duplicate Meeting functionality may cause some unexpected behavior. (2874952, 2892366)
Apply to All: In the event editor, the Apply to All functionality may not work correctly for all selections. (2884158, 2884186, 2884903)
iCalendar import: You cannot import iCal files while offline. (2922180)

3.5.2.3 Resolved Limitations in this Release

This section describes resolved limitations of the Oracle Calendar desktop client for Macintosh.

Making changes to notification preferences produced a blank dialog box. (2891594)
If you expand a repeating event (Meeting, Daily Note, Day Event), select all the instances and try to change your reply status, the program terminated unexpectedly. (2919825)
You could not create a weekly meeting on a Saturday or Sunday. (2929937)
Clicking the Open All Folders button from a recently retrieved Published Address Book yielded the Save dialog. (2879881)
Creating an address book while working off-line (standalone only) caused errors to occur the next time you signed in. (2871716)
Meetings created by Event Calendars that include attendees yielded unexpected errors. (2880321)
If you opened another user's agenda as a designate and then did a refresh, you would get an error message. (2919085)
Changes to your Address Book's user-defined fields were not saved. (2832478)
In cases where there was no wireless support (such is the case for MDCC), wireless reminder check boxes were displayed in the Reminder tabs and the Entry Defaults preferences even though they should not have been. (2893809)
When creating a recurring Meeting whereby one instance had a duration long enough to create a conflict with another instance on the following day, the following message was displayed: "Two or more instances have the same date and time". (2840028)
Clicking OK in the Oracle Calendar Preferences dialog and then choosing View | Set Filter could cause the application to terminate unexpectedly. (2847602)
Attempting to create a recurring Meeting that exceeded the maximum number of instances allowed caused the following unexpected error: Module: <CST_Event_Editor.cpp>, Label: 390, Service error: 0x1812b. (2872041)
Attempting to display the Print Preview for an Agenda page that contained a Meeting spanning more than 24 hours could cause the application to terminate unexpectedly. (2877037)
A password that was changed while working off-line to a password not allowed by the server could cause the application to unexpectedly terminate when attempting to reconcile the on-line and off-line passwords. (2903625)
When a remote user was invited to a meeting, the meeting owner's status was not correctly displayed to the remote user. The owner's status would be shown as "will confirm later" instead of "will attend". This was a server issue. (2892567)

3.5.3 Oracle Calendar Desktop Client for Linux

This section contains these topics:

3.5.3.1 What's New in this Release

This section lists new features of the Oracle Calendar desktop client for Linux.

Open a Group View containing the agendas of the people invited to a particular Meeting by right-clicking on a Meeting and selecting Open Group View.
Use the startup preferences to choose when you would like your In-tray to be displayed.
With the new on-line Address Book, you can now manage all your Address Book Entries from one location and create categories to make your contact management easier than ever before.
View number of attendees for confirmed and unconfirmed meetings.
A new installer allows users to easily install the application. A pre-configuration file is provided for silent installation.
Support for meetings greater than 24 hours.
Perform conflict checking on a per resource basis.*
Improved address book: Ability to create a repeating note entry from a birthday or anniversary date, ability to launch an e-mail application from an address book entry's e-mail address, ability to launch the browser from an address book entry's URL.
Support passwords longer than 15 characters.*
Enhanced resource scheduling.*
The "Show time as free" feature allows users to accept invitations to meetings while remaining available for other invitations.*

* Requires Oracle Calendar server 9.0.4

3.5.3.2 Known Limitations and Workarounds

This section describes general issues and workarounds for the Oracle Calendar desktop client for Linux.

Address Book Folders: Changes you make to Address Book Folders preferences will remain in effect for the current session only. They are not properly saved. (2836729)
iCalendar import: Importing iCalendar files offline may not work properly. (2847503)
Reconciling your Agendas: Selecting "Download Only" from the Reconcile, Cancel, Download Only dialog box will erase any changes you have made in your off-line Agenda. You will not be warned that any changes that you make while offline will be lost. (3117497)
Running concurrent copies: You should not run concurrent copies of Oracle Calendar from one Unix account.
Default port: On some machines it may be necessary to specify the port number when connecting to a server that uses the default port. For example, if you are connecting to a server named calendar.acme.com, you will have to enter calendar.acme.com:5730. (2880571)

3.5.3.3 Resolved Limitations in this Release

This section describes resolved limitations of Oracle Calendar Desktop Client for Linux.

Attempting to create a group containing a user that was an Event Calendar caused the following unexpected error: Module: <CST_ManageGroupsEditorDlog.cpp>, Label: 135, Service error: 0x13209. (2847208)
Meetings created by Event Calendars that included attendees caused unexpected errors. (2880299)
When a remote user was invited to meeting, the meeting owner's status was not correctly displayed to the remote user. The owner's status was shown as "will confirm later" instead of "will attend". This was a server issue. (2892157)
When changing your password while working off-line, choosing a password that was not allowed by the server could cause the application to unexpectedly terminate when you attempted to reconcile your on-line and off-line passwords. (2892573)

3.5.4 Oracle Calendar Desktop Client for Solaris

3.5.4.1 What's New in this Release

This section lists new features of Oracle Calendar desktop client for Solaris.

Open a Group View containing the agendas of the people invited to a particular Meeting by right-clicking on a Meeting and selecting Open Group View.
Use the startup preferences to choose when you would like your In-tray to be displayed.
With the new on-line Address Book, you can now manage all your Address Book Entries from one location and create categories to make your contact management easier than ever before.
View number of attendees for confirmed and unconfirmed meetings.
A new installer allows users to easily install the application. A pre-configuration file is provided for silent installation.
Support for meetings greater than 24 hours.
Perform conflict checking on a per resource basis.*
Improved address book: Ability to create a repeating note entry from a birthday or anniversary date, ability to launch an e-mail application from an address book entry's e-mail address, ability to launch the browser from an address book entry's URL.
Support passwords longer than 15 characters.*
Enhanced resource scheduling.*
The "Show time as free" feature allows users to accept invitations to meetings while remaining available for other invitations.*

* Requires Oracle Calendar server 9.0.4

3.5.4.2 Known Limitations and Workarounds

This section describes general issues and workarounds for Oracle Calendar Desktop Client for Solaris.

Address Book Folders: Changes you make to Address Book Folders preferences will remain in effect for the current session only. They are not properly saved. (2836729)
iCalendar import: Importing iCalendar files offline may not work properly. (2847503)
Reconciling your Agendas: Selecting "Download Only" from the Reconcile, Cancel, Download Only dialog box will erase any changes you have made in your off-line Agenda. You will not be warned that any changes that you make while offline will be lost. (3117497)
Running concurrent copies: You should not run concurrent copies of Oracle Calendar from one Unix account.

3.5.4.3 Resolved Limitations in this Release

This section describes resolved limitations of Oracle Calendar Desktop Client for Solaris.

Creating a repeating entry: Clicking "Apply to All" in the General tab of a repeating entry would reset your Reminder and Reply options for all instances of the entry.
Resources with many designates: You would exceed the maximum mail distribution number by adding a resource with many designates.

3.6 Oracle Calendar Sync Clients

This section contains release note information on these products:

3.6.1 Oracle Calendar Sync for Palm for Windows

This section contains these topics:

3.6.1.1 What's New in this Release

This section lists new features of Oracle Calendar Sync for Palm for Windows.

Support for Oracle Web Conferencing details in events
Ability to choose whether or not to synchronize refused events to your device
Ability to choose whether or not events that fall outside your date range are to be deleted from your device (but kept on the server)
Support for synchronizing and filtering contact categories
Support for synchronizing attendees and their statuses to the device
Ability to change your attendance status from the device and synchronize it back to the server
Ability to configure which rules to use during a modify conflict on a per data type basis
Enhanced support for recurrence rule on personal events
Support for German and Japanese

3.6.1.2 Known Limitations and Workarounds

This section describes general issues and workarounds for Oracle Calendar Sync for Palm for Windows.

Modifications on the client and server: When modifying the same contact with a desktop client and the Palm device, and the rules setting is set to replace the mobile device item with the calendar server item, some fields may not be synchronized correctly. (2851814)
Information not synchronized to server: Notes, Alarms and Access Levels modified on the device may not get synchronized with the server. If you are using a the Calendar server v5.4 , Details may not get synchronized either. (2842611)

3.6.1.3 Device-Related Issues

This section describes issues encountered by Oracle Calendar Sync for Palm due to third-party device and software behavior.

Upgrades: When upgrading from Oracle CorporateSync 3.0.x for Palm, InstallShield returns random characters when reading an empty value from the registry instead of returning an error. (2872048)
Daylight savings: Recurring meetings which span the Daylight Savings time change may not be synchronized correctly. Several instances before or after the time change may have incorrect end times. (2842124)
Regional settings: Your operating system's regional settings must be the same as the Palm device's language. (3065498)

3.6.1.4 Resolved Limitations in this Release

Events and contacts that have titles ending with an "=" character did not synchronize correctly. (2864229)

3.6.2 Oracle Calendar Sync for Palm for Macintosh

This section contains these topics:

3.6.2.1 What's New in this Release

This section lists new features of Oracle Calendar Sync for Palm for Macintosh.

Support for ACE
Support for Mac OS X

3.6.2.2 Known Limitations and Workarounds

This section describes general issues and workarounds for Oracle Calendar Sync for Palm for Macintosh.

Repeating entries: You cannot synchronize the Palm organizer's Repeating Entries. You can, however, synchronize calendar server Repeating Entries.
Hand-held overwrites Macintosh: The 'Hand-held overwrites Macintosh" feature is not available.
Timed/untimed events: If you change a timed Event to an untimed Event, or vice versa, on your Palm organizer, the change will not appear in the calendar application.
Languages: Oracle Calendar Sync for Palm only fully supports English-language synchronization.
Duplicate names: Oracle Calendar Sync for Palm does not present a list of possible matches for duplicated names. To avoid this problem, enter as much unique user information as possible (e.g. organization unit).

3.6.2.3 Device-Related Issues

Time zones: The Palm organizer does not support different time zones. Make sure the Palm organizer time zone corresponds to the calendar application's.

3.6.3 Oracle Calendar Sync for Pocket PC

This section contains these topics:

3.6.3.1 What's New in this Release

This section lists new features of Oracle Calendar Sync for Pocket PC.

Support for Oracle Web Conferencing details in events
Ability to choose whether or not to synchronize refused events to your device
Ability to choose whether or not events that fall outside your date range are to be deleted from your device (but kept on the server)
Support for synchronizing and filtering contact categories
Support for synchronizing attendees and their statuses to the device
Ability to change your attendance status from the device and synchronize it back to the server
Ability to configure which rules to use during a modify conflict on a per data type basis
Enhanced support for recurrence rule on personal events
Support for German and Japanese

3.6.3.2 Known Limitations and Workarounds

This section describes general issues and workarounds for Oracle Calendar Sync for Pocket PC.

Modifications on client and server: When modifying the same contact with a desktop client and the Pocket PC device, and the rules setting is set to replace the mobile device item with the calendar server item, some fields may not be synchronized correctly. (2851814)
Information not synchronized to server: Editing a recurring event from the device does not sync (with V5.4 Server only). (2891864)
Multi-byte titles: Entries with long multi-byte titles and locations may appear partially cut off after synchronizing. (3069057)

3.6.3.3 Device-Related Issues

This section describes issues encountered by Oracle Calendar Sync for Palm due to third-party device and software behavior.

Upgrades: When upgrading from Oracle CorporateSync 3.0.x for Pocket PC, InstallShield returns random characters when reading an empty value from the registry instead of returning an error. (2872048)
Daylight savings: Recurring meetings which span the daylight time change may not be synchronized correctly. Several instances before or after the time change may have incorrect end times. (2842124)
Regional settings: Your operating system's regional settings must be the same as the language of the Pocket PC device. (3065498)

3.6.3.4 Resolved Limitations in this Release

Events and contacts that have titles ending with an "=" character did not synchronize correctly. (2864229)

3.7 Client Coexistence Behavior

This section describes coexistence issues between Oracle Connector for Outlook and the Oracle Calendar desktop clients.

Using a Calendar desktop client, adding an occurrence to a repeating event causes the event to get duplicated in Oracle Connector for Outlook.
Using Oracle Connector for Outlook, deleting an entry without sending a cancelation results in that entry showing as declined in the Calendar desktop clients.

3Oracle Calendar Release Notes

3.1 Oracle Calendar Server

3.1.1 What's New in this Release

Performance and Scalability:

High Availability

Enhanced Administration Capabilities

Directory Support

Other Enhancements (Client Support Required)

3.1.2 Known Limitations and Workarounds

Various

3.1.3 Resolved Limitations in this Release

3.1.4 Documentation Errata

3.2 Oracle Calendar SDK

3.2.1 What's New in this Release

3.2.2 Known Limitations and Workarounds

3.2.3 Resolved Limitations in this Release

3.3 Oracle Calendar Application System

3.3.1 Oracle Calendar Web Client

3.3.1.1 What's New in this Release

3.3.1.2 Known Limitations and Workarounds

3.3.1.3 Resolved Limitations in this Release

3.3.1.4 Document Errata

3.3.2 Oracle Calendar Web Services

3.3.2.1 What's New in this Release

3.3.3 Oracle Sync Server

3.3.3.1 What's New in this Release

3.3.3.2 Known Limitations and Workarounds

3.3.3.3 Device-Related Issues

3.3.3.4 Resolved Limitations in this Release

3.4 Oracle Connector for Outlook

3.4.1 What's New in this Release

3.4.2 Known Limitations and Workarounds

3.4.3 Resolved Limitations in this Release

3.5 Oracle Calendar Desktop Clients

3.5.1 Oracle Calendar Desktop Client for Windows

3.5.1.1 What's New in this Release

3.5.1.2 Known Limitations and Workarounds

3.5.1.3 Resolved Limitations in this Release

3.5.2 Oracle Calendar Desktop Client for Macintosh

3.5.2.1 What's New in this Release

3.5.2.2 Known Limitations and Workarounds

3.5.2.3 Resolved Limitations in this Release

3.5.3 Oracle Calendar Desktop Client for Linux

3.5.3.1 What's New in this Release

3.5.3.2 Known Limitations and Workarounds

3.5.3.3 Resolved Limitations in this Release

3.5.4 Oracle Calendar Desktop Client for Solaris

3.5.4.1 What's New in this Release

3.5.4.2 Known Limitations and Workarounds

3.5.4.3 Resolved Limitations in this Release

3.6 Oracle Calendar Sync Clients

3.6.1 Oracle Calendar Sync for Palm for Windows

3.6.1.1 What's New in this Release

3.6.1.2 Known Limitations and Workarounds

3.6.1.3 Device-Related Issues

3.6.1.4 Resolved Limitations in this Release

3.6.2 Oracle Calendar Sync for Palm for Macintosh

3.6.2.1 What's New in this Release

3.6.2.2 Known Limitations and Workarounds

3.6.2.3 Device-Related Issues

3.6.3 Oracle Calendar Sync for Pocket PC

3.6.3.1 What's New in this Release

3.6.3.2 Known Limitations and Workarounds

3.6.3.3 Device-Related Issues

3.6.3.4 Resolved Limitations in this Release

3.7 Client Coexistence Behavior

3
Oracle Calendar Release Notes