Globo Mobile Technologies Inc - Confidential

Globo Mobile Technologies Inc

Release Notice for GO!NotifyLink Enterprise Server -

Mirapoint

REVISION HISTORY
Date / Author / Description of Changes
07/16/2012 / Anthony Costello / Version 4.8.2 Patch 2
Updated #22 and #23 under GO!NotifyLink Server Things to Know
04/30/2012 / Anthony Costello / Version 4.8.2 Patch 1
Important Things to Know:
Behavior with the synchronization of the Anniversary field for Contacts
01/23/2012 / Jodie Grazier / Version 4.8.0
11/03/2010 / Jodie Grazier / Version 4.7.1
10/25/2010 / Jodie Grazier / Important Things To Know:
-Additional contact fields supported by GO!NotifyLink, that do not have a corresponding field in Mirapoint
09/20/2010 / Jodie Grazier / Version 4.7.0
12/04/2009 / Jodie Grazier / Noted with release of GO!NLES v4.6.x Update 12
Section III.B. Noted information about data retention
02/26/2009 / Jodie Grazier / Version 4.6.0
08/31/2007 / Jodie Grazier / Version 4.5.0

I. Installer Information

II. Functional Summary

A. Installer New/Changed Features

B. Server New/Changed Features

C. User Interface (Web) New/Changed Features

III. Important Things to Know

A. Features Not Supported

B. GO!NotifyLink Server Things to Know

C. Device Things to Know

D. Mirapoint Things to Know

IV. Outstanding Issues/Bugs

A. GO!NotifyLink Server Outstanding Issues/Bugs

B. Mirapoint Outstanding Issues/Bugs

I. Installer Information

Original Release Date (GO!NLES v4.8.0):01/23/2012

Base Product:GO!NotifyLink Enterprise Server

II. Functional Summary

A. Installer New/Changed Features

B. Server New/Changed Features

1.)Tentative meeting responses sent from the device are now supported. 4778

2.)Corrected an issue so that attendees do not receive a second email from a meeting created on the device. 4852

3.)Updated meeting response handling so that comments added when responding from the device are shown on the server. 4979

4.)Improved charset handling in HTML emails when using BlackBerry devices withGO!NotifyLink 4.8 app. 5195

C. User Interface (Web) New/Changed Features

III. Important Things to Know

A. Features Not Supported

B. GO!NotifyLink Server Things to Know

1.)Mirapoint server must have XML and Calendar licenses.

2.)For devices NOT using ActiveSync, the following mail folders will not be displayed in the web and will not be available to track for new email:

  1. The “Sent Items” folder as defined for the Mail Server via the Administrative Web.
  2. The “Trash” folder as defined for the Mail Server via the Administrative Web.

3.)The following Mirapoint fields are not synchronized to devices:

  1. Contacts: primaryphone.
  2. Calendar: priority, mobile device reminders, send email, access permissions, attachments, resources other than one for location, and meeting attendees other than those made from the device, show as busy, private, categories
  3. Tasks: categories

4.)The following fields can be set on devices, but do not have a corresponding Mirapoint field:

  1. Contacts: BlackBerry device PIN, BlackBerry device Direct Connect ID, email2, email3, middlename, prefix, suffix, Home Address fields, Home Website, home fax, otherphone, Assistant Name, Assistant Phone, Home Phone 2, Business Phone 2, Spouse Name, IM Address
  2. Tasks: Reminder, Start Date, Status other than Complete

5.)With the implementation of GO!NotifyLink Enterprise Server (GO!NLES) v4.6.x Patch 12, contact and task fields supported by GO!NotifyLink, but not by Mirapoint, will be preserved when sending information back to the device. This does not fix contacts and tasks currently on the server;it will only affect contacts and tasks created or modified on the device after Patch 12 is applied.

  1. Preserved contact fields include: Home Address (Street, City, State, Zip, Country), Home Website, Email2, Email3, Radio Phone, RIM PIN, Middle Name, Suffix, Prefix
  2. Additionally, when using GO!NLES 4.7.x: Assistant Name, Assistant Phone, Home Phone 2, Business Phone 2, Spouse Name, IM Address
  3. Preserved task fields include: Alarm/Reminder

6.)The server running the GO!NotifyLink Web component attempts to connect to the Mirapoint server to pull a list of users to be displayed when the administrator is adding a new user to the GO!NotifyLink Enterprise Server. If the connection cannot be made, no users will show up on the Select Users page (accessed through User Administration > Add User) and there will be an error displayed on the web page. In order for this feature to work correctly,

  1. Verify the GO!NotifyLink Web component can connect to the Mirapoint server over port 10143.
  2. Verify that a valid Administrator username and password are configured for the Mirapoint server in the GO!NotifyLink web admin (Server Administration > Mail Servers).

7.)Folder monitoring is only supported when the user’s mail account uses the “INBOX” prefix for their personal namespace. User accounts that do not have this prefix will only be able to monitor the Inbox.

8.)Users added to the GO!NotifyLink Enterprise Server (GO!NLES) with administrator rights to Mirapoint will see all folders of every user when viewing the folders page. Loading the folders page may take several minutes due to the number of folders being listed. 6353

9.)For Pim items added or changed on the device, leading and trailing spaces are trimmed for all Task and Event text fields and most Contact fields before saving to the Mirapoint server.

10.) PIM items (calendar events, contacts, tasks) created on the device with fields exceeding 255 characters are not processed on the server. In addition, an error message will appear on the device after each PIM cycle until the timeout is reached (about 20 minutes). 6362

11.) When creating a contact on a device, at least one of FirstName, LastName, or EmailAddress must be specified; otherwise it will not be created in Mirapoint.

12.) Contacts with no first or last name will sync to the device with Display Name as their first name.

13.) A Contact’s Website field maps to Work URL.

14.) For Mirapoint version 3.6 and higher, the Event Location field will be mapped to the device's Event Location field instead of a Resource.

15.) GO!NotifyLink will send an email notification as well as a Meeting Invitation for invitations that are received to the user’s account.

16.) When a Meeting Request is initiated from the device, the Pim Server Name is used (if it's not an IP) to determine which attendees are on the Mirapoint server. Previously the user’s email address was being used.

17.) If a Meeting Request is initiated from the device, all recipients will receive an Invitation. However, only recipients in the same domain will have the item automatically added to their calendar.

18.) If the DeleteCycleTime is increased to be greater than every Pim cycle, recently changed recurring events that span across the user’s LookBack/LookAhead range but do not have an instance in the range will be synchronized to the device and then deleted in the next Delete Cycle.

19.) When Exceptions to recurring events are created on the device, they are no longer part of the main event on the server. This means that the exception will not be updated if the recurring event changes on the server (for example, the subject or location of the main event is changed).

20.) Events created on the device with a reminder time that is NOT a multiple of five will not synchronize the correct reminder to the server. GO!NotifyLink will, therefore, round up tothe nearest 5 minute interval when reminder times that are not multiples of five are entered. 5756

21.) When sending a task to the device, a task with highest priority specified in Mirapoint will be set to high priority. If lowest priority is specified in Mirapoint, the priority will be set to low when synchronized to the device.

22.)When the ‘Anniversary’ field of a contact syncs to the device, the year is always ‘2000’. 8450

  • Fixed in GO!NLES 4.8.2 Patch 2

23.) When the ‘Anniversary’ field of a contact is added on the device, it will only display back on the server if the ‘Birthday’ field is populated on the contact as well. 8452

  • Fixed in GO!NLES 4.8.2 Patch 2

C. Device Things to Know

D. Mirapoint Things to Know

1.)Some recurrence patterns are handled differently in Mirapoint as compared to the devices or the SynQ Outlook Connector:

  1. Monthly recurring events in Mirapoint on day 29, 30, or 31 will only occur in months that have those days. On the device and in Outlook the instance would be moved to the last day of the month if it did not contain the day to occur on.
  2. Monthly recurrence by first, second, etc. weekday or weekend day is handled in Mirapoint by recurring on Monday through Friday or Saturday and Sunday. The device and Outlook would handle this as the first weekday or weekend day (only one day) that falls in the pattern.

2.)When responding to a Meeting Request from your device any text added to an Accept or Decline will not be stored on the server. This is a limitation of the Mirapoint API and may be addressed in a future release of the API.

3.)Events created on the device with a start/end (duration) time that is NOT a multiple of five will be rounded down to the nearest 5 minute interval. 6360

4.)A task’s due date cannot be changed from a date to None. 5995

IV. Outstanding Issues/Bugs

A. GO!NotifyLink Server Outstanding Issues/Bugs

1.)When ‘response history’ is turned off, notifications may still contain the history of the email thread.

2.)Messages sent from Outlook using Rich Text format may incorrectly display on the device with an attachment named “winmail.dat”.

3.)If Contact Categories are created on the Server such that they only contain digits, contacts may use this number instead of the actual category field when sent to the device.

4.)When creating an exception out of GMT shadow on a recurring event in the GMT shadow, a duplicate event is created.

5.)When a pim item from the device fails to be processed by GO!NotifyLink server, an error message is sent back to the device and displayed in the device Inbox. 6351

6.)Creating an annual recurring series on the server only synchronizes the first occurrence to the device.

B. Mirapoint Outstanding Issues/Bugs

1.)When viewing Mirapoint email using the web client, read and unread status changes made on the device may not appear immediately. After logging out and logging in again, the status is correct. This problem was not seen when viewing Mirapoint email using Outlook/SynQ.

2.)For Mirapoint version 3.8.3, some upper ASCII characters in the body of an email may not convert correctly. 5498

3.)For Mirapoint version 3.8.3, declining a meeting request from the device may not delete the meeting from the server. 5499

4.)When responding to a meeting invitation from the device and including comments that span multiple lines, an email with the comments will not be sent to the organizer. 5672

10/11/18

Page 1 of 5