Differences

This shows you the differences between two versions of the page.

--- cloudappliance/applupdatev1712 [2018_02_06 18:44] – [New Features] added links to new/updated articles steven
+++ cloudappliance/applupdatev1712 [2018_03_21 17:29] – dan
@@ Line 86: / Line 86: @@
   * [SME-3682] - In some cases spurious Audit Log records indicating incorrectly that an email template has been modified are created when Policies settings are changed.
   * [SME-3752] - When some character sets are used in file names UTF-8 decoding is done incorrectly, preventing the files from being uploaded through CloudFTP.
 ===== v1712.01 =====
@@ Line 92: / Line 93: @@
   * [SME-3765] - When an object storage provider that exposed more than one bucket was synchronised using Provider Re-sync, empty copies of folders from one bucket were sometimes created in another bucket. This has been resolved.
+===== v1712.02 (release pending) =====
+==== New Features ====
+  * [SME-3695] - M-Stream's fast transfers of large files have been extended to the filesystem (FS) storage provider.
+==== Improvements ====
+  * [SME-3722] Memory consumption when printing PDF files from the browser has been reduced.
+  * [SME-3836] - Performance when listing the contents of a folder containing hundreds or thousands of direct subfolders has been improved.
+==== Resolved Issues ====
+  * [SME-3716, SME-3798] - Issues with uploading and operating on large files when SSE is enabled for S3 and Open S3 storage providers have been resolved.
+  * [SME-3597] - The iOS app showed empty directories when versions were hidden from users.  This has been resolved.
+  * [SME-3841] - Updated files were sometimes saved to invisible  locations if the original files had been imported to an object storage provider under specific conditions.  This has been resolved.
+  * [SME-3818] - When Google Storage was used in S3-compatible mode, sometimes only the first 50 items were shown when the contents of a directory was being listed.  This appears to have been the result of a defect in Google's S3 interface.  A work-around has been implemented in the File Fabric to resolve the issue.