Filter
Top Products
Workaround: Manually scroll down to the section in the email.
On a Samsung Galaxy Tab 10.1 running Android 4.0.4, changing the browser's default web page is not saved. (DT
7325409)
On iOS devices, if a user creates a Task in Outlook, changes to the Notes field of that task are not synchronized between
the iOS device and Outlook. (DT 7323798)
On iOS devices, DocsToGo crashes when it is re-opened. (DT 7311799)
In the calendar app, when a user views one day and selects the arrow to move ahead one day, the calendar moves ahead
one month instead of one day. (DT 7305033)
On iOS devices, users cannot open files in the DocsToGo app if they deactivate and reactivate their device. (DT 7300452)
Workaround: Delete and reinstall the DocsToGo app.
When you update the password requirements in the work space IT policy, users are not prompted to create a new password
even though their existing work space password does not meet the new requirements. (DT 7294446)
If a user installs and opens the Work Connect app on their device before a work space is set up on their device, they cannot
resume opening the app when the work space set up is complete. (DT 7291942)
Workaround: Close and reopen the Work Connect app.
If a user deletes and reinstalls the Work Connect and Work Browser apps, in certain circumstances, the user cannot access
the work space on their device. (DT 7284925)
Workaround: Deactivate and reactivate the device.
When a user sends an email using a secured app, the action does not complete. When a secure app tries to share
Facebook or Twitter as secured apps, the secure browser opens but the user is not notified that this action is not permitted
because Facebook and Twitter are not secured apps. (DT 7272319)
When a user accesses their email in the work space for the first time, in certain circumstances the email content is blank
and the Work Connect app stops responding. (DT 7259730)
Workaround: Close and reopen the Work Connect app.
If you create a secure app in the Universal Device Service from an HTML5 based app, when your developer tries to sign the
app, it displays an error.
Workaround: The developer needs to add certain flags to the project file and rebuild the app.
If a user installs the BES10 Client on an Android device, and installs the BES10 Manager before they activate their device,
when the user opens the BES10 Manager they do not see any error messages. (DT 7245204)
Release Notes Known issues
21