Use the form below to enter your search criteria. By default, all content is searched except for document comments. If you wish to search comments as well as everything else, click "Also Search Comments" below.
[267]
Comments: 0,
Last Modified: Jan 4, 2007 5:27 PM
- Find Similar
MeetingMaker features not supported by NotifyLink. Features Not Supported: 1.)   ... ; New events created from a device will default to "busy" in MeetingMaker. -  ... ; in MeetingMaker. - On devices that display "status" events synchronized ... ; Custom fields of a contact do not synchronize between the device and MeetingMaker - except for BlackBerry
[237]
Comments: 0,
Last Modified: Jan 8, 2007 9:11 AM
- Find Similar
How task priorities synchronize between MeetingMaker and devices. Task priorities from MeetingMaker will be synchronized to the device as follows: Urgent, Important, High = High Medium, Normal, None = Normal Low = Low Task priorities from the device will be synchronized to MeetingMaker as follows: High = High Normal = Normal Low = Low
[165]
Comments: 0,
Last Modified: Oct 2, 2007 10:10 AM
- Find Similar
Various issues with recurring events using MeetingMaker The following recurrence patterns are not supported in MeetingMaker. If one of these patterns is created on the device an error message ... file if an event created on the device does not appear in the MeetingMaker calendar. I.  ... one (i.e. every 2 months). VI. Monthly recurring events on the 29 th , 30 th , or 31 st . Meeting
[235]
Comments: 0,
Last Modified: Jan 8, 2007 9:56 AM
- Find Similar
If MeetingMaker is set up to use LDAP Authentication, the user's LDAP password should be used when adding the user to NLES. If MeetingMaker is set up to use LDAP Authentication, the user's LDAP password should be used when adding the user to NotifyLink Enterprise Server (NLES). If the LDAP password for a user changes, the password must be updated on the Edit User page of the NL web in order
[240]
Comments: 0,
Last Modified: Jan 4, 2007 5:44 PM
- Find Similar
Changes to a meeting from a device are not updated in MeetingMaker. Guests of meeting do not have permission to modify the meeting. This cannot be prevented on device, so if a user edits the meeting on the device, the change will not be stored in MeetingMaker. However, the user will not be notified that the update failed and the change will remain on the device.
[636]
Comments: 0,
Last Modified: Oct 4, 2007 3:00 PM
- Find Similar
MeetingMaker stores PIM in GMT format which can sometimes alter dates/times associated with events or tasks. It is important to understand that the MeetingMaker servlet stores PIM dates/times in  ... ). Since MeetingMaker does not support monthly recurring events occurring on the 29th (a day not all ... ;monthly recurring meeting that is scheduled on the 28th may result in the 
[256]
Comments: 0,
Last Modified: Jan 5, 2007 9:21 AM
- Find Similar
Usernames and passwords containing special characters. Username and passwords in MeetingMaker can contain special characters that are not handled correctly by NotifyLink. For example, the ampersand ("&") and double quotation characters.
[268]
Comments: 0,
Last Modified: Jan 4, 2007 5:30 PM
- Find Similar
Mail folders will vary based on the email system a MeetingMaker user has. Some folders that display in the Folders list via the web may not be actual mail folders and should not be selected for processing. The names of these folders will be different depending on the mail system that is being used.
[257]
Comments: 0,
Last Modified: Jan 5, 2007 10:03 AM
- Find Similar
NotifyLink does not handle upper ASCII characters in MeetingMaker passwords. Passwords in MeetingMaker can contain upper ASCII characters. NotifyLink does not handle these correctly.
[158]
Comments: 0,
Last Modified: Nov 30, 2006 3:08 PM
- Find Similar
. In MeetingMaker version 8.6 there was a new feature added that required every user created to have a foreign email address that is set up by the email administrator. Since MeetingMaker does not have ... Meeting Invitations.NotifyLink requires the email address in MeetingMaker 8.6 so that invitations ... PIM then sends the email addresses to MeetingMaker, which does a lookup to determine which Meeting
[262]
Comments: 0,
Last Modified: Jan 5, 2007 12:47 PM
- Find Similar
Issue involving tasks created in MeetingMaker that have a Percent Done value set. This issue involves tasks created in MeetingMaker that have a Percent Done value set. If the task is edited on the device, the Percent Done will be set to 100 (for completed tasks) or 0 (for incomplete tasks).
[333]
Comments: 0,
Last Modified: Mar 6, 2007 2:53 PM
- Find Similar
For contacts created on the device and then edited on the MeetingMaker server, the values of Home Address ... may have fields for Home Address and Web Page; these fields are not supported in the MeetingMaker Client. If a contact is created on the device with these fields, the contact is synchronized to MeetingMaker but these fields are not displayed. If the contact is then edited in the MeetingMaker
[265]
Comments: 0,
Last Modified: Mar 13, 2009 9:23 AM
- Find Similar
Issue involving contacts created in MeetingMaker that have a Custom 3 and/or Custom 4 value set. This issue involves contacts created in MeetingMaker that have a Custom 3 and/or Custom 4 value set. If the contact is edited on the device, the Custom 3 field will be cleared and the Custom 4 field will be set to the previous value of Custom 3. This no longer occurs after applying MeetingMaker Sync
[252]
Comments: 0,
Last Modified: Jul 24, 2009 2:58 PM
- Find Similar
;, 256, CDKEY, 1, 1, 0, -1, 'Inbox') Note that for MeetingMaker customers, this work-around ... , not just MeetingMaker. ... Work-around for issue requiring email accounts to receive meeting invitations. If a valid email account is not used, meeting invitations will not be sent to the device. As a work-around, find the ClientDeviceSAKey
[243]
Comments: 0,
Last Modified: Jan 4, 2007 5:46 PM
- Find Similar
Only the first instance of a recurring meeting appears in the invitation. This issue involves invitations/proposals for recurring meetings. When a user receives an invitation on the device, only the first instance of the recurring meeting is noted making the invitation look as if it were for a single meeting.