IBM® Daeja™ ViewONE Virtual, Version 5.0.2 Release Notes

Release description

IBM Daeja ViewONE, Version 5.0.2, makes it easier for business and IT professionals to view large documents and images in their enterprise content management (ECM) solution or in other custom applications, websites, intranets, and extranets.

Download location

To download IBM Daeja ViewONE:

1. Log in to Fix Central.
2. In the Product Group list, select Enterprise Content Management.
3. In the Select from Enterprise Content Management list, select the Daeja ViewONE edition that you want to download.

You must have a license to download this software. The file that you download is a product installer for IBM Daeja ViewONE Virtual. When you run the installer, indicate any add-on modules for which you have a license. The installer then enables only those modules you have purchased.

Prerequisites before installing IBM Daeja ViewONE, Version 5.0.2

You must run the installer as an administrative user.

Before you install IBM Daeja ViewONE, Version 5.0.2:

• Uninstall any previous version of IBM Daeja ViewONE before you install IBM Daeja ViewONE, Version 5.0.2.
• Ensure that the Java™ Runtime Environment (JRE) V7 or later is installed on the system running the installer.

To generate a hardware and software requirements report, see System Requirements.

Installing IBM Daeja ViewONE, Version 5.0.2

You can run the installer interactively or silently.

To run the installer silently, update the sample response file that is provided with the image archive before you run the installer.

Windows

At a command prompt, change to the directory where you extracted the installation image.

To install the viewer interactively, enter the following command:

DAEJA_VIEWONE_5.0.2_WIN_ML.exe

Alternatively, double-click DAEJA_VIEWONE_5.0.2_WIN_ML.exe in Windows Explorer.

To install the viewer silently, enter the following command:

DAEJA_VIEWONE_5.0.2_WIN_ML.exe -f fully_qualified_path_of_the_response_file

From version 5.0, the default installation path on Windows is C:\Program Files\IBM\Daeja ViewONE_Virtual

UNIX

At a command prompt, change to the directory where you extracted the installation image.

To install the viewer interactively, enter the following command:

./DAEJA_VIEWONE_5.0.2_UNIX_ML.bin

To install the viewer silently, enter the following command:

./DAEJA_VIEWONE_5.0.2_UNIX_ML.bin -f fully_qualified_path_of_the_response_file

From version 5.0, the default installation path on UNIX is /opt/IBM/Daeja ViewONE_Virtual

Configuring the Viewer

IBM Daeja ViewONE comes with a Toolkit rich in capabilities that enables advanced integration and customization of the viewer by using HTML parameters and JavaScript API methods. For more information on the developer’s guide refer to:

IBM Daeja ViewONE Virtual Developer's Guide

New features

IBM Daeja ViewONE, Version 5.0.2, provides the following new features:

Documents can be sent to the IBM Daeja ViewONE print service using a JavaScript print API

The JavaScript print API allows system integrators to interact with the IBM Daeja ViewONE print service. Further details are documented in Technote http://www.ibm.com/support/docview.wss?uid=swg22007748

(ER161305) Annotation editing dialogs can be moved

Annotation editing dialogs are moveable. Users can drag and reposition the annotation text entry dialog, sticky note dialog and color selection dialogs. This allows users to read document and annotation content underneath the dialogs without having to close them.

Thumbnail view contains a visible vertical scrollbar

A vertical Scrollbar is displayed on the thumbnail view when content overflows. This gives users a visual indicator of the current location within the open document. Additionally, this allows users to use click and drag functionality to navigate through a whole document in one action via the thumbnail view scrollbar. Please note, the scrollbar is not visible when the viewmode is set to 'fullpage'.

(ER148771) Annotation show/hide toggle is maintained throughout the complete browsing of a multiple page document

Users interacting with the show/hide annotation toggle button benefit from the state of that button being remembered across page changes.

(ER170756) PDF documents using non-embedded CID fonts

PDF Documents with content that depends on non-embedded CID fonts are displayed correctly. This support is available through the Platform Independent PDF Module.

(ER137383/ER124081) Fine grained control of annotation display (AnnotationAllowHideAll Parameter)

The parameter 'AnnotationAllowHideAll' determines how non-editable annotations are displayed when a user clicks on the 'hide Annotations' toggle button. If this parameter is set to true, users can hide all annotations. The default value for this parameter is false.
Example: <param name="annotationAllowHideAll" value="true" />

URIs passed to Javascript API functions are explicitly validated

For the JavaScipt API calls 'openFile(String, int)', 'setPageArray(String, int)' and 'setThumbsArray(String, int)', the URI passed in are validated to ensure that malformed URIs such as those containing whitespace characters throw a JavaScript exception detailing that the input is invalid.

Control over print quality (VectorDocumentPrintDpi configuration)

When the viewer prints a document, it produces a printable PDF file. A default DPI of 300 is used when the PDF file is generated. The 'VectorDocumentPrintDpi' server configuration property is used to override the default DPI. A higher DPI value will produce PDF files with higher resolution. The trade-off is that the time taken to produce the output will increase and the file size will be larger. The default value for this property is 300. This property will only affect print quality for PDF documents or documents opened with the ViewONE Office Module.

Page rotation event

Whenever a page is rotated, via a rotation button click or rotate() JavaScript API call, the TRANSFORM (event id: 1) event will be fired. When multiple pages are selected, a TRANSFORM event is fired for each page that is rotated.

Javascript API functions To change the size Of thumbnails

Javascript API functions 'increaseThumbsSize()' and 'decreaseThumbsSize()' change the size of all thumbnails by 25%. After each resize operation has completed, a THUMBVIEWRENDERED (88) event is fired.

Semitransparent support For annotations

This support is for Oval, Circle, Freehand, Arrow, Line Polygon, Open Polygon, Highlight and Highlight Polygon. Text, Note, Stamp and Redact are not included with this implementation. SemiTransparent Annotations are only supported in Standalone mode and for IBM Content Navigator System with an IBM CM8 repository.

(ER170376) Default thumbnails size configuration

The size of thumbnails is now configurable via two HTML parameters: 'thumbnailDefaultWidth' and 'thumbnailDefaultHeight'. These parameters take a pixel size which is used to define the size of the higlightable area of each thumbnail.
Example: <param name="thumbnailDefaultWidth" value="150" />

For online documentation, see the IBM Daeja ViewONE knowledge center.

Fixes

IBM Daeja ViewONE, Version 5.0.2, provides the following fixes:

Additional Release Notes

Daeja ViewONE as an integrated solution

When running Daeja ViewONE 5.0.2 as a component inside IBM Content Navigator, the minimum supported version of ICN is 3.0.2

APARs IO24433 and IO24174

Once this package has been installed, then APARs IO24433 and IO24174 are resolved by setting the following ViewONE parameter, useJavaPdfTTFontHinting to false.

Version information in build.txt

The Build Number associated with this package is contained in build.txt, which is located in the client/v1files directory. Historically this contained the full product version number but now it only contains the ViewONE internal build number.

Document Builder

Document Builder uses repository-document and repository-annotations when the document is created

The document will be built with the source document as it is saved in the repository. The document is also built by using the annotations that are saved in the repository, unless annotations have been edited. The following scenarios explain the effects of this behavior:

Scenario 1:

1. Two instances of the viewer are opened in document builder mode
2. A document is loaded from a repository into each viewer window
3. The document builder user copies a page from the document in viewer window 1 and pastes the page in to the document in viewer window 2
4. While the document builder user is working on the documents, another user or system process alters one or both of the master documents
5. The document builder user builds the modified document
6. Because one or both of the master documents were altered during the document builder session, the built document contains the pages from the latest saved version of the master documents

Result: The document currently displayed in the viewer differs from the newly built document in the system. To prevent this issue occurring, the master document should be locked or checked out when it is retrieved for document builder.

Note Versioned documents will not be affected by this issue. This issue only affects situations where the document that a URL refers to has changed.

Scenario 2:

1. Two instances of the viewer are opened in document builder mode
2. A document with annotations is loaded from a repository into each viewer window
3. The document builder user copies a page from the document in viewer window 1 and pastes the page in to the document in viewer window 2
4. While the document builder user is working on the document, another user or system process alters one or more of the annotations used in one or both master documents
5. The document builder user builds the modified document
6. The built document contains the pages from the latest saved version of the master documents. For pages where the document builder user has not modified annotations in the viewer, the annotations for those pages comes from the latest saved annatations version. For pages that the user has modified the annotations in the viewer, those pages will contain annotations as seen in the viewer which may not contain the latest changes

Result: The document currently displayed in the viewer differs from the newly built document in the system. To prevent this issue occurring, the master document should be locked or checked out when it is retrieved for document builder.

Restore annotations is not supported in document builder mode

When in document builder mode, the option to restore annotations is not supported. The following scenario explains the effects of this behavior:

Scenario 1:

1. Viewer is loaded in document builder mode
2. A document is loaded from a repository
3. Annotations are created by the user
4. Restore annotations button is disabled
5. Javascript API reloadAnnotations() is disabled

Result: The user cannot reload the annotations from the server. Newly created annotations and edited annotation edits remain.

To restore any newly created annotations, the user must take the following steps:

1. Remove the page on which annotations are present that you want to restore
2. Put the page with the original annotations on the clipboard (cut/copy)
3. Paste the page into the new document location

Known problems, issues, and limitations

As problems are discovered and resolved, the IBM Support team updates the Support site. By searching the Support site, you can quickly find workarounds or solutions to problems.

The following links open queries for IBM Daeja ViewONE documents on the IBM Support site:

· IBM Daeja ViewONE, Version 5.0.2 known problems

· IBM Daeja ViewONE, Version 5.0.2 known problems and documentation updates

· All IBM Daeja ViewONE, Version 5.0.2 documents on the IBM Support site

Comparison with native renderers

IBM Daeja ViewONE Virtual is designed to support as many file types as possible. However, the product is not able to render every type of file with the same accuracy as native applications, such as Microsoft Word. The flexibility of the viewer can lead to differences in the way that the documents are displayed between the native application and the viewer. The severity of the differences varies depending on the complexity of the file type. In particular, PDF files and Microsoft Office files are difficult to render with complete accuracy in a universal viewer.

Excel spreadsheet load times

Excel spreadsheet load times are impacted based on the size and complexity of the Excel document. In order to improve load times, IBM Daeja ViewONE does support tuning capabilities, such as breaking up the Excel document presentation into multiple pages. Please be aware, as this behaviour may not be optimal for your end user viewing experience.

Prompt to save redacted documents uses hexidecimal filename

After a document is permenantly redacted and the user selects Download, they are normally prompted to save the document with a file name based on the original un-redacted document. For instance mypresentation.ppt will default to mypresentation.tif. In this version the user might be prompted with a filename such as 41f96b20b97f431ebd4efd85245f1f72.tif instead. The user can still change the name to something more meaningful.

No pageN support in document builder mode

If a pageN document is open in the viewer, the user cannot switch to document builder mode. The user remains in the edit mode in which the document was opened. The following scenario explains the effects of this behavior:

Scenario 1:

1. Viewer is loaded in either annotation or redaction mode
2. A pageN document is loaded from a repository
3. A user attempts to switch to document builder mode
4. The user receives a message and remains in annotation or redaction mode

Result: This switch is not permitted and the user will stay in their current mode.

To enter document builder mode, the user must close the pageN document and then switch to document builder mode.

No docN support in document builder mode

DocN documents are not supported in conjunction with document builder mode. The combination of these features may result in unusual and/or unexpected behavior.

Document Builder supported file type limitations

Document builder is able to support TIFF and PDF files with the exception of email attachments. TIFF and PDF files that are attached to emails cannot be used as source files for a new document.

PDF files with access control flags set by the owner of the document cannot be used as a source document for document building where they require a password to view the document or where the owner has indicated that the content may not be copied.

Rendering of the semi transparency appears to blend between the outline and the fill

Annotations that have the semi-transparent property set to true, the transparent property set to true and a fill color set can appear to blend the line and fill colors near the edges.

Annotation with fill color set to black and set to transparent are not printed transparent

Annotations that have the transparent property set to true and a fill color set to black are not printed transparent .

Copyright and trademark information

http://www.ibm.com/legal/copytrade.shtml

Notices

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Other company, product, or service names may be trademarks or service marks of others.

THIRD-PARTY LICENSE TERMS AND CONDITIONS, NOTICES AND INFORMATION

The license agreement for this product refers you to this file for details concerning terms and conditions applicable to third party software code included in this product, and for certain notices and other information IBM must provide to you under its license to certain software code. The relevant terms and conditions, notices and other information are provided or referenced below. Please note that any non-English version of the licenses below is unofficial and is provided to you for your convenience only. The English version of the licenses below, provided as part of the English version of this file, is the official version.

Notwithstanding the terms and conditions of any other agreement you may have with IBM or any of its related or affiliated entities (collectively "IBM"), the third party software code identified below are "Excluded Components" and are subject to the following terms and conditions:

• the Excluded Components are provided on an "AS IS" basis
• IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND CONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT NOT LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR INTERFERENCE AND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
• IBM will not be liable to you or indemnify you for any claims related to the Excluded Components
• IBM will not be liable for any direct, indirect, incidental, special, exemplary, punitive or consequential damages with respect to the Excluded Components.