windream 6.5

Release Notes and Known Issues

windream GmbH, Bochum

Copyright

© 2016 by windream GmbH Wasserstr.219 44799 Bochum Issue: 12/16 – 6.5.0.7

All rights reserved. No part of the contents of this book may be reproduced or transmitted in any form (print, photocopy, or any other form) or by any means without the explicitly written permission of windream GmbH.

windream and the VFS technology are registered trademarks of windream GmbH. All other brand names and product names are trademarks or registered trademarks of their respective owners.

Important Note

All information and technical specifications in this book have been collected by the authors with great care. They cannot, however, either guarantee, take legal responsibility for or make any other warranty resulting from the use of this information.

We would also like to point out that all software and hardware logos and names are the exclusive property of the Trademark, Brandname or Patent right holders. These are naturally protected by the appropriate laws and trade agreements.

Errors and short-term modifications reserved.

Content i

Content

windream 6.5.0.7 Release 1

Release Notes 1

Note Concerning Migration of windream 5.5 Server and Previous Versions 1 Restrictions 3

windream 6.5.0.7 - Known Issues 7

windream 6.5.0.7 Release 1

windream 6.5.0.7 Release

The following document contains Notes and Known Issues about the new windream Version 6.5 (Client Version 6.5.0.7, Sever Version 6.5.0.7).

Release Notes

The new features of windream 6.5 will be described in a more detailed way in "windream 6.5 – What's New". Additionally, the document "windream 6.0 – What's New" has to be regarded especially if it is planned to directly update from windream 5.5 to windream 6.5.

Important Note: With version 6.5 not all modules of windream will be released.

Note Concerning Migration of windream 5.5 Server and Previous Versions

Important Note: A migration of windream version lower than 6.0. will only be possible based on windream 5.5 (Server) and requires the Server DMS Patch 23. We recommend to keep windream Server 5.5 updated to the latest patch level. Versions lower than windream 5.5. have to be migrated to windream 5.5 first. For further information, please refer to the file „How2Migrate55To60.txt“, which can be found in the installation folder of the windream Server. This file and the installation instruction contain notes that have to be regarded when using an Oracle data base. For a direct migration of windream 5.5 to windream 6.5 which is supported as well this information is also valid. windream 6.0 can easily be upgraded via the server setup to windream 6.5. The setup does not make any big changes on the data base. A windream Client with windream version 5.5 (or lower) can only be connected in a very limited way to a windream 6.0.0.8 or windream 6.5.0.7 Server, as for example the search profiles created since version

2 Release Notes

6.0 cannot be read anymore. The compatibility cannot be guaranteed anymore due to the converting of the data base to Unicode. Another issue are the new 64 Bit ID columns in the windream data base schema that were introduced with windream 6.0. The windream 5.5 Client is not able to process IDs bigger than 32 Bit, so that the respective documents cannot be processed properly. The same goes for history entries etc.

Release Notes 3

Restrictions

For the Release of windream 6.5.0.7 please consider the information in the following table! The table shows whether a windream module or product can be run with windream version 6.5.0.7 or not.

Important Note: Microsoft Windows Server 2016 is not supported yet (planned for first quarter 2017).

windream Modules

Version

Compatible Planned for

Comment

windream ToGo 5.5

Testing 1st quarter 2017

windream Solo 6.5 Yes On 64 Bit Windows platforms only; separate setups for Client and Server

windream Web Portal (W2P/W2P2)

6.0.5.0

Yes

windream Share Drive 6.5 Yes SMB1 only

windream Proxy Server

6.5

Yes Deployment requires low network latencies

windream Sync

2.5.14

Yes Restricted

windream Mobile

2.5.14

Yes

windream 6.0, 6.5 without support of annotations, Unicode, 64 Bit-IDs

windream Web Service

5.0 Yes

Windream Object Store

7.0

Yes

4 Release Notes

windream Modules

Version

Compatible Planned for

Comment

MultiIndicer 6.0.X Yes

Notifier 6.0.X Yes

Config Wizard 6.0.X

No 1st quarter 2017

Reminder 6.0.X Yes

Gadgets 5.5 Yes - Additional tool

required

- Without Support

- 6.5 Sidebar as a

Replacement

MoveTo 6.0.X Yes

ChangeProperty 6.0.X Yes

WMShow 5.5 Yes

windream Signature 6.0 Yes

Mail archiving

Exchange Client (excluding ECM extension)

6.0.9

Yes

Exchange Client including ECM extension

6.0.9 Yes

Exchange Server 6.0.0.2 Yes

Standalone 6.0.9 Yes

OWA (Microsoft Outlook Web Access)

6.0.0.1 Yes OWA 2013 in 1st quarter 2017

Without Unicode and 64 Bit-IDs; for Exchange Server 2010;

Lotus Notes / Domino

- No On

request

BPM

Engine

5.5.0.13

Yes 5.5.0.23 – January 2017

Release Notes 5

windream Modules

Version

Compatible Planned for

Comment

Designer 5.5.0.29 Yes

Client 5.5.0.35 Yes

Web Client 5.5.0.6 Yes

BPM Gadgets

5.5

Yes - Additional tool

required

- Without Support

- 6.5 Sidebar as

Replacement

SAP

ArcLink 5.0.7

6.0.1.0

Yes On request

DirectLink (Transfer) 5.0 Yes

SAPCommand (ScanLink)

5.5.0.4

Yes

Capturing Solutions

windream Imaging 6.0.29.0 Yes No support of windream 64–Bit-IDs

(BizHub) Connect

3.4.0.25

Yes 3.5.0.1 – January 2017

Solutions Kernel

XMLImportManager

5.0.8 Yes No Unicode

windream DocMon

5.5.10.0 Yes

Indexing

CADIndexer

5.0.1.0

On request

6 Release Notes

windream Modules

Version

Compatible Planned for

Comment

Mobile Apps

iOS 5.0 Yes

iOS

6.5

No 1st quarter 2017

Android

5.0

Yes Web Service 5.0 required

Android

6.5

Yes Web Service 6.5 required

windream 6.5.0.7 – Known Issues 7

windream 6.5.0.7 – Known Issues

Topic

Note

Compatibility of Third Party Components and Scripts

Before updating a productive system to windream 6.5, components and scripts used with windream have to be tested for compatibility.

Migration of Annotations

With windream 6.0 or 6.5 the creation and management of annotations has changed. Annotations, that have been created with windream versions until 5.5, shall be migrated after the update installation to windream 6.0/6.5. The migration can be performed at any point of time after the installation, even during running operations and can be executed via a tool. The tool will be provided on request in the 1st quarter 2017.

Note: Even if no migration of the annotations is performed, annotations created with a windream version lower than 6.0, can still be edited and new annotations to the document can be created.

No Archiving of Annotations

While archiving the documents the respective annotations will not be archived (concerning windream versions 6.0, 6.5). Even archiving the annotations only as it was possible until windream version 5.5 is not possible. Up to windream 5.5 (saving of the annotations analogously to the documents in the file system) the document type of the annotations can be configured that way that the annotations will be archived directly at capturing or manually via the context menu.

Annotations Mapping of Index Fields of the Element Type for Annotations

The Index fields of the object type for Annotations (Annotation-

NL) have defined data types. The import of the object type will fail, if the data type of a predefined index fields (wmVar00 until wmVar08 and wmVar93 and wmVar94) was changed on the windream system.

In this case a new element type with respective index fields has to be created in the WMC and the mapping of the index fields has to be configured in the registry of the windream server.

To do so create under the key

[HKEY_LOCAL_MACHINE\SOFTWARE\A.I.S.

GmbH\windream\3.6\Annotation]the registry entry

8 windream 6.5.0.7 – Known Issues

AnnotationMapping of the type String and determine the mapping according to the following pattern:

"AnnotationMapping"=(STRING)

"#title=wmVar93;#text=wmVar94;#textlenght=wmVar00;#top

=wmVar01;#bottom=wmVar02;#left=wmVar03;#right=wmVar04;

#bgcolor=wmVar05;#textcolor=wmVar06;#annotationtype=wm

Var07;#annotationdocument=wmVar08

Note: Not all columns have to be filled out. It is sufficient to configure the mapping for the columns that differ from the default values. When using proxy servers the mapping of the index fields only needs to be configured in the registry on the windream main server.

My windream Vector Index Fields for the Creation of the Subfolders of the Dynamic View

Via the entry (AllowVectorIndexForDynamicSubfolders) in the Windows Registry it can be defined if vector fields shall be listed

in the selection list of the indices (Value = 1) or not. By default, vector fields will not be displayed (Value does not exist in the registry

or 0). The entry (Character string as REG_DWORD) under the key [HKLM\Software\A.I.S.

GmbH\windream\3.6\Shell\Namespace] has to be created if it does not exist yet.

Note: If using vector fields for structuring the subfolders of the dynamic view the following limitations are known: In the search on which the dynamic lists bases it is not possible to search for the catalog ID (for example “ files only“, or “folders only“) and dwFlags.

Sidebar Sidebar loses configuration

It is possible that the sidebar loses its configuration settings. The solution for that will be provided within the next patch for windream 6.5.0.7 in the 1st quarter 2017. Workaround:

Save the files „TilesConfiguration.xml“ and „PivotViewConfiguration.xml“ in the folder „%AppData%\windream GmbH\Sidebar “after the configuration and if necessary copy it back into this folder.

Sidebar “Hide “is not considered

At the reboot of the Sidebar (for example via changing the scaling) the condition “hide “will not be considered.

Sidebar Display Problems During the Use of Several Monitors With Different Scaling

windream 6.5.0.7 – Known Issues 9

If primary and secondary monitor have different scaling and the Sidebar is configured for the secondary monitor, the Sidebar will not be displayed correctly anymore.

Configuration (TFS 7757)

Empty Client-Script Cache

The function does not delete the local files in the script cache.

Search (TFS 7108)

Preview Function in the DMS-Browser

The preview function in the DMS Browser is currently not available or does not show the selected document.

Search

(TFS 7172)

Search in Annotations Only Possible in the Quick Search and Text Search

This only concerns the new annotations from windream version 6.0 / 6.5 on which are saved in the windream “Node & Leaf “structure.

Search Function “Save as Default “Only Has Effect on the Currently Selected Search Tab

The function “Save as default” from the Ribbon of the windream Search saves the current settings as default only fort he currently active tab page.

Proxy Server The “new “Annotations Cannot Be Used If the Client is Connected Via A Proxy Server

The new annotations available from windream version 6.0 on will no more be saved as file objects in the windream file system but in a structure “Node & Leaf „in the windream data base. The storage and loading of the annotations via the proxy server is not available yet.