IBM Daeja ViewONE, 5.0.11 Release Notes

These release notes provide information about new features, fixes, and known problems for IBM Daeja ViewONE, Version 5.0.11.

Important: The most current version of the file can always be found online.

Content

Release notes IBM Daeja ViewONE, Version 5.0.11

Abstract

These release notes provide information about new features, fixes, and known problems for IBM Daeja ViewONE, Version 5.0.11.

Release description

IBM Daeja ViewONE, Version 5.0.11, 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.11

You must run the installer as an administrative user.

Before you install IBM Daeja ViewONE, Version 5.0.11:

• Uninstall any previous version of IBM Daeja ViewONE before you install IBM Daeja ViewONE, Version 5.0.11.
• Ensure that the Java™ Runtime Environment (JRE) V8 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.11

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:

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

To install the viewer silently, enter the following command:

DAEJA_VIEWONE_5.0.11_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:

To install the viewer silently, enter the following command:

./DAEJA_VIEWONE_5.0.11_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:

New features

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

Coverpage should always be printed on a new sheet when printed from IBM Content Navigator.

Coverpage will always be printed on the front side of the new sheet when multiple documents are combined as multipart document.
From this feature, separation of individual document after printing is possible.

• For individual documents having even number of pages in multipart document -> blank page will be added after every even paged document.
• Documents with odd number of pages -> no blank page added.
• Even paged document as last document -> no blank page added.
• Odd paged document as last document -> no blank page added.

Users should enable the coverpage option to use this feature.
Steps:

1. Login to ICN
2. Browse for the document
3. Right click on the item in document list
4. Select Print
5. Select Document / All Parts
6. Enable Cover Page

User should be able to select font type for annotation text

Annotation font type drop down, lets the user choose a particular font for text annotation.

By default, font selected is Arial and the drop down is disabled.

User can add additional fonts that enables the drop down to choose their preferred font.

Configuring ICN(IBM Content Navigator) for additional fonts:

1. Set parameter annotationCustomFonts with comma separated font family names. Open the administrator tool and click Settings > Daeja ViewONE.
   Under Server, add the following parameter name and value pair:
   Example: Parameter name: annotationCustomFonts
   Value: Courier New, Times New Roman
2. After adding the parameter, restart the server and open any document. This will initiate the font resource file generation process required for Daeja ViewONE for the additional fonts to be populated in the font type drop down.
3. After the generation process completes, reopen the document, font type drop down should be populated with newly added additional fonts and are available for the selection.

Configuring standalone Daeja ViewONE for additional fonts:

1. Add the parameter annotationCustomFonts in viewone.properties file
   Open the WEB-INF/viewone.properties file in a text editor and add an entry
   Example: annotationCustomFonts=Courier New, Times New Roman
2. Restart the server and the font resource file generation required for Daeja ViewONE gets initialized and opens AWT Windows as part of the font generation process which gets closed automatically once the process completes.
3. Open the document, the font type drop down should be populated with additional fonts and are available for the selection.

User can continue to use Daeja ViewONE while the font generation process is in progress.

In general, any font would have Regular, Bold, Italic, Bold Italic font styles and the respective TTF files.

For example, Arial font has the following font styles and its corresponding TTF files.

Arial Regular– arial.ttf

Arial Bold – arialb.ttf

Arial Italic- ariali.ttf

Arial Bold Italic – arialbi.ttf

In font resource file generation process, for each font style, an AWT window gets opened, hence for each font, that has four styles, four AWT windows gets opened simultaneously.

On the server machine, AWT Windows opens as part of the font generation process and gets closed automatically once the process completes.

User must mention the font family name as the value for the server parameter.

Note:

• Only TTF (True Type Font) fonts are supported.
• If font location property (exclusiveFontDirectory, fontRepositoryBaseLocal) is not specified then the TTF files for additional fonts should be installed as System fonts. If specified, then the TTF files should be present in that location and need not be installed as System fonts.
• Add file.encoding=UTF-8 as JVM argument in the Application server.
• Enable the display in Linux/container environment required for the font resource file generation process (AWT windows gets opened only if the GUI/Display is enabled).
• In LINUX and UNIX environments, to generate additional fonts correctly, DISPLAY must be running and the JVM argument java.awt.headless must be set to false.
  To ensure that DISPLAY is running, use the command xclock .
  Additionally:
  • DISPLAY 's running and java.awt.headless=false are required only when additional fonts are generated. This is also a one-time operation.
    After the additional fonts are generated, java.awt.headless can be removed or set to true, and DISPLAY no longer has to run.
  • Updating Daeja deletes the generated font files. The font files ( cftlist.txt and .v1 ) are kept in the temp directory, which is deleted during the upgrade. In preparing to upgrade Daeja, back up the font files to avoid regenerating them afterward.
    The temp directory in the IBM WebSphere Application Server is at the following location:
    \profiles\\temp\icnNode\icn\navigator\navigator.war\v1files\viewone\rep\00XXXXXX0.rep
    After the upgrade, you can copy the saved font files into the new temp directory.

  Ability to print the sticky note summary page while the printUseManualDownload is set to true.

  With this feature, user will be able to print and download the sticky note summary page along with original document even when the printUseManualDownload is set to true.

  Steps:

  1. Set the HTML parameter printUseManualDownload to true.
  2. Add Sticky Note to the document.
  3. User can save the changes or directly click on Daeja Print icon.
  4. Check the Sticky Note Summary Checkbox in Print Dialog
  5. Click on Prepare File button.
  6. Click on Download File button.
  7. New browser tab opens the locally downloaded file with Sticky Note Summary page.

  Download File button can take few seconds to get enabled once the printing process is completed.

  User should be able to download/save a redacted file using a different name.

  Now end user can save redacted document with any custom name. Previously, it used to take original file name.
  To enable this functionality, user needs to set new HTML Parameter as:
  

  While using ICN, user need to perform redaction and choose the Local File option in permanent redaction mode and save document with custom name after setting the HTML parameter as mentioned below:

  1. Open ICN and navigate to Administration > Settings.
  2. Under Virtual section refer Additional settings and click on the New button to add the new HTML parameter.
  3. In the pop up, add the following parameter name and value pair:
  4. Name: showRedactedCustomFilename
     Value: true
  5. After adding the parameter, click Save and Close button.
  6. Refresh the browser to apply new settings.

  Provide an option to download entire document or specific page from a document.

  User can download specific page of document from viewer.
  By clicking download document button, dialog will appear to accept input that determines whether to download specific single page or to download entire document.
  Document - Select this option to download entire document with original mime type.
  Page - Select this option to input specific page to download in PDF format.

  Fixes

  IBM Daeja ViewONE Virtual, Version 5.0.11, includes all fixes and features up to and including IBM Daeja ViewONE Virtual Version 5.0.10 iFix 3.

  Additional Release Notes

  Daeja ViewONE as an integrated solution

  When running Daeja ViewONE 5.0.11 as a component inside IBM Content Navigator, the minimum supported version of ICN is 3.0.12, unless stated otherwise by the specific ICN release.

  System requirements

  Go to the page at Software Product Compatibility Reports to create a high-level report for operating systems, hypervisors and prerequisites.

  Optimized performance of printing PDF documents

  When printing PDF documents with annotations, the annotations are embedded in the downloaded PDF document as native PDF annotations. This reduces the time taken to print documents, especially large documents.

  This process currently only applies to printing PDF documents when 'Print Original Size' is selected in the print settings. If this is not selected or the printed document contains other file formats, the print process completely flattens the content of each page.

  The time it takes to prepare a PDF with annotations for print using the optimized print depends on the total number of annotations. In most cases you need to have several hundreds of annotations in a single document before the time difference becomes noticeable.

  With the optimized print any annotations created in IBM Daeja ViewONE Virtual are embedded into the document as native PDF annotations. Therefore they are recognized as active annotations when the PDF is viewed by tools that support editing of PDF documents. If this document is subsequently viewed by IBM Daeja ViewONE Virtual, any annotations will be treated as static content where loading a document with pre-applied native annotations cannot be edited. To prevent document or annotation modification appropriate security would need to be set via a tool that supports editing or via some PDF printers.

  Sticky Notes
  Sticky Note annotations will appear on top of other annotations regardless of z-order.

  Line Width
  The maximum line width of native annotations is 12pt and will be limited to this for print output.

  Solid Text
  If a solid text annotation is set to be semi-transparent the fill background and the text will become semi-transparent, previous behavior left the text solid and only the fill became semi-transparent.

  Image Stamps
  Image stamp annotations will appear underneath any other annotation types regardless of the z-order. This is due to the fact that they added to the content of the PDF and not as separate native PDF annotations.

  Limitations

  The optimized PDF print does not occur in the following circumstances:

  • PDF documents with digital signatures.
  • PDF documents with password encryption and edit protection.
  • PDF Documents with any ruler or angle annotations.

  Deprecation of Annotation Types

  As of IBM Daeja ViewONE Virtual Version 5.0.6 the following annotation types are deprecated:

  • Ruler
  • Angle
  • Transparent Highlight

  These annotation types will be removed in a future version of the product.

  Deprecation of Email Render = 1

  As of IBM Daeja ViewONE Virtual Version 5.0.3, the default value for parameter emailRenderer is set to '2' which represents the email module that allows for paginated output. See more details for this module below. As of IBM Daeja ViewONE Virtual Version 5.0.6, the ability to switch the email module to the alternative value "1" has been deprecated. The value will be removed as a valid setting for the parameter in a future release.

  The email module that produces paginated output is now the default setting for the standalone product. This email module supports the display of EML (MIME RFC 822) and MSG (Microsoft Outlook and Exchange) formats as paginated content, and allows for streaming and redaction of emails. It requires the IBM ViewONE Office Module to be licensed. To redact emails, the IBM ViewONE Permanent Redaction module is also required. When opening emails that have annotations saved using the older email rendering mechanism, the HTML parameter 'emailUseAnnotationDefinedModule' defines the behavior.

  The 'emailUseAnnotationDefinedModule' parameter can have the following values:

  always: The default behavior is to always attempt to use the renderer that is defined in the annotation.

  never: The renderer that is defined in the annotation is never used. Instead, the email is opened using the renderer specified in the viewer. This may cause the annotations to move. The user will be notified that 'The annotations on this document were saved with a different version of the viewer. Annotation may have moved and will need checking'. The annotation save button will be enabled and user will be prompted to save before they leave the document unless the 'annotationAutoPrompt' HTML parameter has been set. The 'annotationAutoSave' HTML parameter does not work for this annotation change.

  prompt: The user receives a prompt when annotations were created using a different renderer, giving them the option to open using the renderer defined for the viewer (Yes) or attempt to open with the renderer that is specified in the annotation (No). If the user click Yes they will then be notified that 'The annotations on this document were saved with a different version of the viewer. Annotation may have moved and will need checking'. The annotation save button will be enabled and user will be prompted to save before they leave the document, unless the 'annotationAutoPrompt' HTML parameter has been set. The 'annotationAutoSave' HTML parameter does not work for this annotation change.

  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 into 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 main documents
  5. The document builder user builds the modified document
  6. Because one or both of the main documents were altered during the document builder session, the built document contains the pages from the latest saved version of the main documents

  Result: The document currently displayed in the viewer differs from the newly built document in the system. To prevent this issue occurring, the main 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 will only affect 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 into 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 main documents
  5. The document builder user builds the modified document
  6. The built document contains the pages from the latest saved version of the main documents. For pages where the document builder user has not modified annotations in the viewer, the annotations for those pages come from the latest saved annotations 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 main 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:

  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.11 known problems
  • IBM Daeja ViewONE, Version 5.0.11 known problems and documentation updates
  • All IBM Daeja ViewONE, Version 5.0.11 documents on the IBM Support site

  Supported File Formats in ViewONE Virtual

  For information on the supported file formats refer to the tech note below. Please note that this is a live document and might get updated frequently. https://www-01.ibm.com/support/docview.wss?uid=ibm10730429

  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.

  Microsoft browser limitation

  For additional information on IE/Edge limitations, refer to the following tech notes:

  • https://www.ibm.com/support/pages/node/876592
  • https://www.ibm.com/support/pages/node/875492

  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 behavior may not be optimal for your end user viewing experience.

  Prompt to save redacted documents uses hexadecimal filename

  After a document is permanently 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:

  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 for non PDF documents. When printing PDF documents, with 'Print Original Size' selected, these annotations are printed with transparency applied.

  UI mirroring limitation

  UI mirroring is not supported for the bidi languages, Arabic and Hebrew.

  Copyright and trademark information

  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.