CorporateSync 3.0.x for Pocket PC
These release notes contain system requirements, new features and known limitations. For installation instructions and legal information, please consult the readme.
Important : In order to synchronize Contacts on your mobile device with the calendar server, you must be using CorporateTime 6.0 for Windows as your desktop calendar application.
Contents:
System Requirements
- CorporateTime Server 5.2 Patch01 or later
- 20 MB of hard disk space
- Microsoft Windows 98, 2000, ME, XP or NT 4.0
- ActiveSync 3.0 or greater
- Pocket PC (Windows CE 3.0) with MIPS, SH3 or ARM processor
- Devices
New features
CorporateSync 3.0.2 for Pocket PC is a maintenance release that provides all the features and functionality of the previous 3.0 release under the Oracle banner. This version will also provide the basis for all future upgrades.The following features were new in version 3.0:
Contacts synchronization
CorporateSync for Pocket PC now offers full Contact synchronization between your device and the calendar server (only available to users of CorporateTime 6.0 for Windows or greater).Desktop-only configuration
CorporateSync now manages all configuration settings from your desktop computer, eliminating the need to use files on your mobile device.Full synchronization
CorporateSync's Full Synchronization feature helps you reconcile all data between your mobile device and the calendar server. Consult the on-line help packaged with CorporateSync for information on when and how to perform a Full Synchronization.Automatic data recovery during synchronization
CorporateSync employs a variety of methods to automatically detect synchronization errors and recover data.Improved Repeating Meeting support
Previous version of CorporateSync only synchronized the first instance of a Repeating Meeting. CorporateSync 3.0 for Pocket PC synchronizes all instances of a Repeating Meeting if one or more instances fall within the date range.Automatic ACE detection
CorporateSync automatically detects and uses the calendar server's Authentication Compression Encryption (ACE) settings during sign-in.Detailed synchronization logs
The Synchronization log provides information about the synchronization process on an Entry-by-Entry basis.The Message Log reports any general problems encountered during synchronization.
Limitations, caveats and known problems with this release
- You cannot synchronize yearly recurring appointments that do not have end dates. (#5315)
- If your user name is a subset of another user name on the calendar server (for example, if your user name is John Waters and another user's name is John Waterson), or if you are a resource's contact person, you must use your user ID to synchronize. (#5227, 5627)
- If you synchronize an untimed Event, CorporateSync will set the Event's reminder on the calendar server to your Daily Note reminder default, instead of your Day Event reminder default. (#5176)
- CorporateTime's Task priority levels are different from those on your mobile device. If you have a Task on your mobile device and you synchronize, CorporateSync may change the priority level of that Task on the calendar server. (#5168)
- Certain devices have a smaller maximum detail size to include with events than CorporateSync's default size of 32 KB (#4224):
- If you create an Appointment with a title longer than 65 characters and perform a Full Synchronization, CorporateSync will truncate the title. This also occurs for Location (maximum 32 characters) and Details (maximum 32 KB). (#4062)
- CorporateSync will always synchronize completed Tasks.
- CorporateSync no longer requires the CSSetup configuration application on the mobile device. All synchronization operations are handled through the desktop application.
- CorporateSync only supports English-language synchronization.
- During sign-in, CorporateSync will not display a list of possible matches for duplicated names.
- Reminders for Entries and Tasks will trigger if the Reminder was set for the same day you synchronize your mobile device. CorporateSync will generate an error, and the Entry will not be synchronized.
Resolved limitations since 3.0.4
- Accounts with user IDs containing the @ symbol cannot be synchronized.
Resolved limitations since 3.0.2
- Events that are not set as Private on your Pocket PC are synchronized with the calendar server with an access level of Public instead of Normal.
- Tasks that are not set as Private on your Pokect PC are synchronized with the calendar server with an access level of Public instead of Normal.
Resolved limitations since 3.0
- Certain characters in the user name and password will not be accepted for synchronization. (#5378)
- If you are working in certain time zones, you may have problems when you update your Agenda on your device and then synchronize with the server.
Resolved limitations since 1.1.3
- For this release, CorporateSync will always synchronize refused Events.
- Windows NT or Windows 2000: If you are in a time zone with no Daylight Savings Time change, or you are in a time zone where the DST has changed, you will not be able to store recurring events on your device if you attempt to synchronize with the calendar server. (#4706)
- If you create a Repeating Meeting on your mobile device and set it to repeat yearly for 27 or more years, CorporateSync will not synchronize the Meeting. (#3336)
- Windows NT: If your working directory is not set, installation will fail. (#4616)
- The node field accepts a maximum of 10 characters. (#4387)
- Modifying a weekly Repeating Meeting with six instances: If you change only the start and end time of the second instance, the modification does not take effect. (#4337)
- Clicking Stop to abort a synchronization has no effect. CorporateSync will complete the synchronization. (#4330)
- If you are using signing in with SASL (Kerberos V4), CorporateSync does not ignore the user name and password. (#4253)
- CorporateSync will not synchronize Tentative Meetings as Tentative. (#4179)
- If you move a Meeting with a Resource attendee to another time where that Resource is already booked, synchronization will fail and the Meeting will appear differently on the mobile device and calendar server. (#3832)
- After a successful synchronization, the message "The Event Log is being initialized" is displayed in the Message Log. (#3512)
- You cannot synchronize Repeating Events.