IBM Daeja ViewONE, 5.0.10 Release Notes

From this release, users have an option to disable uploading of client side logs to the server. This will ensure any extra calls that are being made for uploading the logs to server will be disabled.

The new parameter is added for enabling this feature - syncClientLogsToServer
- True: The default behavior, where the client logs will be uploaded to the server
- False: When set to false, the client logs will NOT be uploaded to the server.

Example: When set to false, users will not be able to download client side logs at a later time.

The Java package used by the specification APIs changed from javax to Jakarta. Apache Tomcat recommends using their migration tool to make it compatible with Apache Tomcat 10.0.x version. Users need to follow Migration steps documented in the below tech note to make Daeja ViewONE work on Tomcat 10.0.x versions.

How to make Daeja Virtual ViewONE work with Apache Tomcat 10.0.x?

From this release, users will now be able to dynamically update the server logging and tracing properties of IBM Daeja ViewONE in ICN without the need of a server restart. All the server tracing and logging properties can be updated from Daeja ViewONE settings tab on the main settings page of ICN.

It can be navigated from Administration -> Settings -> Daeja ViewONE -> Server -> Additional Settings. Create new parameter and add the logging property you want to enable and save the settings.

For example, server logging properties like traceCache, traceFilter, traceNet, traceOffice, traceStreamer can now be dynamically updated in ICN without the need of server restart.

Note: This will only work on ICN and not custom applications.

IBM Daeja ViewONE now supports opening of hyperlinks in the PDF document. If a document has hyperlinks which has external websites(URL) as targets, users can now click on the link and the targeted website will open in a new tab.

Note: Currently internal links in the document are not supported.

• Users will now be able to print the Hebrew text annotations from right to left if the locale/language is selected as Hebrew.
• The numeric characters within the Hebrew annotation will render left to right as expected.
• If the Hebrew text annotation needs wrapping, then it will wrap the text from right to left so that it is readable in Hebrew language. Also, the text will be right aligned.

Note: Mixture of Hebrew and other languages in the same annotation is not supported. If they want to add other language in the text, then they can select one more annotation.

IBM Daeja ViewONE now supports printing Multi byte characters in the Text annotation using the fallback font Arial unicode. User should have Arial unicode in their system.

If user does not want to use arial unicode as a fallback font, they can set their own fallback font by using newly introduced html parameter
<param name="defaultprintAnnotFont" value="value1"/>

Users can use the new HTML parameter in case of Text cut off issues at the bottom of Text annotation in the print output.
<param name="adjustAnnotTextSize" value="true"/>

Text and Solid Text annotation types in the carbon design have an additional UI button for adding/removing the Bold and Italic property.

Selecting Bold button toggles the styling between regular and Bold font, with highlight feature of a button when it is Bold. By default text is Bold.

Selecting Italic button toggles the styling between regular and Italic font, with the highlight feature of a button when it is Italic. By default text is non-Italic.

Users have an option to enable or disable the print original size option using the new HTML Parameter printOriginalSize

Example: <param name="printOriginalSize" value="true" />

Text and Solid Text annotation types in the carbon design have an additional UI drop-down list for changing the font size.

Text annotations now have a font size dropdown combined with an editable textbox that allows users to either choose a value from a list or set a custom size of x.x granularity. The increment/decrement buttons also can be used to increase/decrease the font size respectively.

For online documentation, see the IBM Daeja ViewONE.

Fixes

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

Additional Release Notes

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

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

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. The annotation may have moved and will need checking'. The annotation save button will be enabled and users 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. The annotation may have moved and will need checking'. The annotation save button will be enabled and users 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 from 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:

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.10 known problems
• IBM Daeja ViewONE, Version 5.0.10 known problems and documentation updates
• All IBM Daeja ViewONE, Version 5.0.10 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:

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.

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.