IBM Daeja ViewONE 5.0.13 Release Notes

Daeja ViewONE as an integrated solution

When you run Daeja ViewONE 5.0.13 as a component inside IBM Content Navigator, the minimum-supported version of ICN is 3.0.14, 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 you print PDF documents with annotations, the annotations are embedded in the downloaded PDF document as native PDF annotations that reduces the time taken to print documents, especially large documents.

This process currently applies to printing PDF documents when 'Print Original Size' is selected in the print settings. If this option 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 by 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. Later, if this document is viewed by IBM Daeja ViewONE Virtual, any annotations are 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 through a tool that supports editing or through some PDF printers.

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

Line Width
The maximum line width of native annotations is 12pt and that is limited for print output.

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

Image Stamps
Image stamp annotations appear underneath any other annotation types regardless of the z-order. This is because 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. As of IBM Daeja ViewONE Virtual Version 5.0.6, the ability to switch the email module to the alternative value "1" is 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 stand-alone 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 you open emails that have annotations and saved by 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 by using the renderer specified in the viewer, which might cause the annotations to move. The user is notified that 'The annotations on this document were saved with a different version of the viewer. Annotation that might have moved and needs checking'. The annotation save button are enabled and user is prompted to save before they leave the document unless the 'annotationAutoPrompt' HTML parameter is set. The 'annotationAutoSave' HTML parameter does not work for this annotation change.
• Prompt: The user receives a prompt when annotations were created by using a different renderer, giving them the option to open by 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 clicks Yes, is notified that 'The annotations on this document were saved with a different version of the viewer. Annotation might have moved and will need checking'. The annotation save button is enabled and user is be prompted to save before they leave the document, unless the 'annotationAutoPrompt' HTML parameter is 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 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 are 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 must be locked or checked out when it is retrieved for document builder.

Note: Versioned documents cannot be affected by this issue. This issue affects situations where the document that a URL refers to change.

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 does not modify 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 contain annotations as seen in the viewer, which might 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 must be locked or checked out when it is retrieved for document builder.

Restore annotations are 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 or copy)
3. Paste the page into the new document location

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.13 known problems
• All IBM Daeja ViewONE, Version 5.0.13 documents on the IBM Support site

Supported File Formats in ViewONE Virtual

Refer for supported file formats in the technote, which 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 IE/Edge limitations, refer to the following technotes:

• 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. Be aware, as this behavior cannot be optimal for your user viewing experience.

Prompt to save redacted documents uses hexadecimal file name

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 unredacted document. For instance, mypresentation.ppt is default to mypresentation.tif. In this version, the user might be prompted with a file name 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 stays 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 with document builder mode. The combination of these features can result in unusual and, or unexpected behavior.

Document Builder supported file type limitations

Document builder is able to support TIFF and PDF files except 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 flag 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 indicated that the content cannot 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.

Annotations 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 that are not printed transparent for non-PDF documents. When you print 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.