Release notes IBM Daeja ViewONE, Version 5.0.15

Abstract

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

Latest iFixes and readmes for this release: https://www.ibm.com/support/fixcentral/swg/selectFixes?parent=Enterprise%20Content%20Management&product=ibm/Other+software/Daeja+ViewONE+Virtual&release=5.0.15&platform=All&function=all

Release description

IBM Daeja ViewONE, Version 5.0.15, 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.15

You must run the installer as an administrative user.

Before you install IBM Daeja ViewONE, Version 5.0.15:

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

Installing IBM Daeja ViewONE, Version 5.0.15

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.15_WIN_ML.exe

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

To install the viewer silently, enter the following command:

DAEJA_VIEWONE_5.0.15_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.15_UNIX_ML.bin

To install the viewer silently, enter the following command:

./DAEJA_VIEWONE_5.0.15_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.15, provides the following new features:


CSDV-56 View table of contents / bookmarks present in the PDF file

This release adds support for viewing the table of contents or bookmarks in applicable PDFs.

By clicking the Table of contents / Bookmarks button on north toolbar, users can view and navigate directly to any section of the PDF.

A new HTML parameter, enableTableOfContentsButton, controls the button visibility and getPDFTableOfContents() JavaScript API allows fetching the table of contents / bookmarks programmatically for enhanced navigation.

Example:

enableTableOfContentsButton = false to hide the Table of contents / Bookmarks button.

enableTableOfContentsButton = true to show the Table of contents / Bookmarks button for PDF with table of contents / bookmarks. Default value is true when this parameter is not configured.

JavaScript API getPDFTableOfContents() to fetch table of contents / bookmarks of documents in json format.


CSDV-84 Excel Document Rendering: Design changes

We have updated the underlying implementation used to render Excel documents. As a result, you may notice differences in page count, formatting, layout or styling in the rendered output compared to earlier versions.

Previously added annotations may also be affected, as changes in formatting and layout could impact their alignment or positioning.


CSDV-91 Support the orientation tag in JPG EXIF metadata while rendering

In this release, support for the EXIF orientation tag in JPG files has been implemented to ensure correct rendering.

The feature automatically applies required rotations and flips based on orientation metadata.


CSDV-42 Ability to use access authentication token in the request header

In this release, two JavaScript APIs have been introduced to manage custom header parameters in outgoing requests.

The first method setHeaderParameter allows setting or updating a header by accepting a key-value pair as parameters.

Once invoked, this method ensures that subsequent requests include the specified header.

Example:

viewONE.setHeaderParameter("security_token", "xabxyabyzabz")

The second method removeHeaderParameter enables the removal of a previously set custom header, passing key as the parameter.

Example:

viewONE.removeHeaderParameter("security_token")

While this feature is primarily intended for setting a 'security token' in the header, it is not limited to that purpose and can be used to configure other parameters as needed.


CSDV-73 View digital certificates present in the PDF file

PDFs can include embedded digital certificates. Starting with this release, users can view these certificates present in a PDF file.

Click on View Certificates button to open a panel displaying all the certificates contained in the PDF. Currently, the following details about the certificates are available:

A new HTML parameter, enableDigitalCertificates, has been introduced to toggle the availability of the button.

A new JavaScript API, getDigitalCertificates(callback), has been introduced to retrieve the digital certificates embedded in a PDF. This is an asynchronous function and requires a callback object to handle the results. The callback object must include the following methods:

Example:

enableDigitalCertificates = false to hide the digital certificate button.

enableDigitalCertificates = true to show the digital certificate button. Default value is true when this parameter is not configured.

JavaScript API getDigitalCertificates(callback)

 // Define the callback object
  const certificateCallback = {
    onSuccess: function (certificates) {
      console.log("Certificates retrieved successfully:", certificates);
      // Process the certificates as needed
    },
    onError: function (errorMsg) {
      console.error("Error retrieving certificates:", errorMsg);
      // Handle the error accordingly
      alert("Failed to fetch certificates: " + errorMsg);
    }
  }; 
  // Call the API 
  viewone.getDigitalCertificates(certificateCallback);


CSDV-81 View table of contents present in the PDF file

This release adds support for viewing the table of contents in applicable PDFs.

By clicking the Table of contents button on north toolbar, users can view and navigate directly to any section of the PDF.

A new HTML parameter, enableTableOfContentsButton, controls the button visibility and getPDFTableOfContents() JavaScript API allows fetching the table of contents programmatically for enhanced navigation.

Example:

enableTableOfContentsButton = false to hide the Table of contents button.

enableTableOfContentsButton = true to show the Table of contents button for PDF with table of contents. Default value is true when this parameter is not configured.

JavaScript API getPDFTableOfContents() to fetch table of contents of documents in json format.


CSDV-83 Qualify Windows Server 2022 for IBM Daeja ViewONE Virtual

Starting with this release, we have qualified IBM Daeja ViewONE Virtual on Windows Server 2022.


CSDV-90 Ability to draw sticky annotations on iPad

With this release, users can create sticky annotations on documents using iPad.

To enable sticky annotation, use the html parameter annotationsSticky and set the value to true.

Note: The default value of the parameter annotationsSticky is false


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

Fixes

IBM Daeja ViewONE Virtual, Version 5.0.15, includes all fixes and features up to and including IBM Daeja ViewONE Virtual Version 5.0.14 iFix 10.

It provides the following additional fixes:


DT419622 Microsoft word document (.doc) fails to open with parsing exception

Certain word document with table content fails to open, eventually causing hung threads while parsing the document.

Affected users: IBM Daeja ViewONE Virtual users


DT420439 A particular EML file fails to open due to a parsing error

Specific EML file with an invalid style attribute value fails to open, showing the error message: "Unable to parse HTML email content".

Affected users: IBM Daeja ViewONE Virtual users


DT435372 The checkbox in the PDF form do not render with borders

When viewing certain PDF document with form fields in the viewer, the checkboxes appear without borders, making it difficult to identify them.

Affected users: IBM Daeja ViewONE Virtual users



Additional Release Notes

Daeja ViewONE as an integrated solution

When running Daeja ViewONE 5.0.15 as a component inside IBM Content Navigator, the minimum supported version of ICN is 3.2.0, 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:

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 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 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 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 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 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:

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:

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:

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 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

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: