This section explains features and requirements regarding special item types. These include:
|•||Contact Distribution Lists|
|•||Calendar, Contact and Task items with special Message Classes (Custom Forms)|
Recurring meetings are a special item type within Exchange. Because of limitations in the programming interfaces offered by Exchange, Add2Exchange has certain limitations in how recurring meetings are synchronized.
Global Recurrence Cutoff
Each calendar relationship in Add2Exchange has a synchronization window, a period of days based around the current day. Regular, non-recurring meetings which fall within the relationship's synchronization window are synchronized and meetings outside the window are not. Recurring meetings have a separate synchronization window. For details, See the section Global Options.
Distribution lists have some limitations in two-way synchronization. One-way synchronization is fully supported. Distribution lists became supported as a contact type in Add2Exchange release 5.2.
One-way support for distribution lists means that distribution lists can be synchronized from any contact source folder to any contact destination folder. See the section Recommended Relationship Settings for details on the settings of one-way relationships.
In a one-way relationship, changes to the source item are synchronized to the destination while changes to the destination item are typically discarded. Distribution lists support this behavior, allowing them to be controlled and pushed from a source folder without recipient users being able to modify them.
In a two-way relationship, however, while changes to the source item are still synchronized to the destination, changes to the destination item are synchronized back to the source rather than being discarded. While distribution lists may be included in such relationships, distribution lists will be synchronized in only a one-way fashion, despite the relationship settings.
One-way synchronization of distribution lists in a two-way relationship does have one difference from normal one-way synchronization. Normal one-way behavior is to immediately overwrite changes to a destination copy. The exclusion is that, for changes to a destination copy of a distribution list in a two-way relationship, the destination changes will remain intact until such time as the original source distribution list is modified and resynchronized to the destination. At that time, the changes to the destination list will be discarded. Until then, however, the changes will have been preserved.
Exchange items may be created with special message classes. These message classes are usually created either by application add-ons to Outlook or by administrators creating a custom form which captures additional information from the user.
For example, an application may create a subclass of the regular contact message class, "IPM.Contact", which includes additional information about that contact. The special class will be given an additional qualifier on the message class name, such as "IPM.Contact.DidItBetter".
Special message classes pose a challenge for synchronization because they specify additional information that is not predefined. Add2Exchange supports synchronization of these customized information fields. Synchronization of special message classes which do not have custom forms is seamless. No additional configuration is necessary.
For items with custom forms, the custom forms must be published on all folders which are subject to synchronization. If you are using private-to-private relationships, this includes the hidden Pivot Folder. For details on how to publish custom forms, see the Microsoft tutorial at: http://office.microsoft.com/en-us/outlook/HA012106101033.aspx
It is possible to create a custom form containing VBScript designed for a private mailbox structure, this type of form may have to be redesigned if replicating to a public Folder.
Note, however, that it is acceptable to use such forms on private-to-private relationships despite the fact the public pivot folder is involved. The custom form must still be published to the pivot folder, but since it will not be invoked, synchronization may work properly in such a case.
See Microsoft's VBScript documentation for details on functions that will not work on public folders.
DidItBetter can quote development support services for custom forms on a case-by-case basis. Please contact your account representative for such requests.
blog comments powered by Disqus