Current version: 1.7
GW Import downloads your Novell GroupWise Calendar appointments and imports them into one of your iOS device's calendars which allows you to have notifications of scheduled events and use native iOS calendar interface. This is a one-way sync from GW calendar to iPhone calendar. The app must be opened to import events, because iOS does not support scheduled execution of user background processes. Requires GroupWise WebAccess account. With GW 8+ support for multiple calendars is available and you can choose which calendars to access. You can also choose into which iOS calendar events will be imported. Please try the free GW Check app first to verify how it works with your GroupWise server.
To configure the app you need to provide your GroupWise server address which typically ends with gw/webacc path and username. If you provide the password it will be stored securely in your iOS device's keychain. If you leave the password field blank, you will be asked for password each time the app is restarted. Please note, that iOS 7 broke this functionality and it is no longer possible to enter password through the pop up dialog box. Repairing it would result in breaking compatibility with old Novell proxy servers that are used by some Groupwise installations. At the moment, the recommended solution is to let the phone store the password.
Use Days To Fetch values to define a range of days for which to import events from GroupWise calendar. If using Groupwise 7 you need to increment Days Ahead by 1 to work around GW7 bug. If the app does not show all the events you expected try setting Fetch All option in Groupwise Calendars selection. If that helps you may have defined rules that move events into subfolders in calendar. Not yet accepted appointments can be imported if the corresponding option is enabled. They will be shown in blue color.
Import Automatically option removes the Import button and events downloaded from server get imported into iPhone calendar right away.
If you get "connection error" status when configuring the app for the first time, please first check server address and then try turning on the "Ignore SSL Warnings" option in Settings. If that resolves the problem, then your server most likely is using self-signed SSL certificate. In that case you can contact your GroupWise admin to see if a properly signed SSL certificate can be installed or continue ignoring the SSL warnings.
If you have other connection issues or the app does not download any appointments and you are on GW 7 or GW 6.5, try disabling Time Zone Support in the app settings.
If you experience issues with time for downloaded appointments, try setting time zone to fixed instead of workstation in WebAccess Time Zone options (using desktop browser and choosing graphical and not basic interface at login) and disabling Time Zone Support in the app settings. Some builds of GW2012 are buggy and may have issues with DST in EST timezone.
If you do not see any calendars available when trying to select a Target Calendar in Settings and you have iOS 6, please first check in iOS Settings/Security that GW Import is allowed to access calendars. Otherwise, go to the iOS Calendar app and create a new calendar there first.
Every time the app imports new appointments it updates the already imported appointments on the iOS device. Updates include appointment time, location, subject, notes, but not the original alert time. If an appointment was deleted in GroupWise, it will also be removed from the iOS device.
If you have questions, bug reports, or suggestions please contact us through our Contact page. It would be helpful to send debug info. Go to the Settings and in the server address field replace "https" with "htTPs", that will enable debug mode. After that download appointments and go to the Settings again. Before showing the Settings screen, the app will show a Compose Email screen already filled with our support email address and debug info. There you should also add your problem description, then just press the Send button. After that you can change "htTPs" back to "https".