This Readme document contains information about the installation of this package and about restrictions in support of IBM Daeja ViewONE, Version 5.0.10 iFix 2
Readme for: IBM Daeja ViewONE
Product or component release: Version 5.0.10
Update name: iFix 2
You must have IBM Daeja ViewONE, Version 5.0.10 installed.
Before you install IBM Daeja ViewONE, Version 5.0.10 iFix 2:
IBM Daeja ViewONE, 5.0.10 iFix 2 is provided as a compressed file containing the files that are needed to update Version 5.0.10 for all supported platforms.
To install this package:
As this package contains all the files required for all platforms, you can remove the files that are included for platforms that are not relevant to your environment. Change to the server/WEB-INF/lib directory under the Daeja ViewONE installation directory and delete the platform specific jars that are not relevant.
There are platform specific jar files:
Make a backup of the Daeja ViewONE 5.0.10 files in the relevant locations in your web application server. For the server files that will be the web application's WEB-INF/lib directory. For the client, it will be where the package client files were copied to. For example v1files directory in the web application.
Note: To upgrade to iFix 2, please ensure that both the client and the server are updated.
If you want to remove the iFix 2 from your installation and revert back to the original 5.0.10 version, you need to replace the files in you installation directories with the backed up files, then copy the files into the correct places in your web application server.
If you use the IBM Daeja ViewONE Version 5.0.10 uninstallation program to remove IBM Daeja ViewONE 5.0.10 and the iFix 2 from your system, then some of the files may be left on your file system and you will need to remove them manually.
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 5.0.10 Virtual Developer's Guide
The following APARs are fixed in this product release for customers who have direct entitlement to IBM Daeja ViewONE. If you are using IBM Daeja ViewONE made available to you as part of another IBM product, these fixes might not be available immediately. Contact IBM Support for information about IBM products that integrate IBM Daeja ViewONE.
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.10&platform=All&function=all
IO28599 CORRUPTED TEXT SEEN WHILE VIEWING MS WORD DOCUMENT CONTAINING MICROSOFT VISIO OBJECTS
Opening MS word document containing Microsoft Visio objects with Hebrew text, corrupted text is rendered in the visio objects.
Affected users: IBM Daeja ViewONE Virtual users
IO28614 MS WORD DOCUMENT NOT DISPLAYING TABLE CONTENT DATA PROPERLY WHEN RENDERED IN VIEWER
Opening MS word document containing multiple table data, table content is not rendered properly.
Affected users: IBM Daeja ViewONE Virtual users
IO28711 MS WORD DOCUMENT FAILS TO RENDER AND SHOWS DOCUMENT TRUNCATION ERROR
Opening MS Word document displays error message document has been truncated and fails to render.
Affected users: IBM Daeja ViewONE Virtual users
IO28742 MS WORD DOCUMENT IS NOT SHOWING THE AM/PM PART OF THE DATE TIME WHEN RENDERED IN THE VIEWER
Opening MS Word document containing date and timestamp, am/pm part of the time is missing and is not rendered.
Affected users: IBM Daeja ViewONE Virtual users
IO28746 CREATE DATE FIELD IS GETTING UPDATED OMITTING AM/PM INFORMATION FOR MICROSOFT WORD DOCUMENTS
Date is updating with the save date of the document but omitting the am/pm part of the date content for word document.
Affected users: IBM Daeja ViewONE Virtual users
IO28747 MS WORD DOCUMENT DATE IS GETTING CHANGED TO CURRENT DATE AND IS NOT SHOWING ORIGINAL DATE SAVED IN THE DOCUMENT
MS Word document containing date field is changing to today's date and is not showing document original date.
Affected users: IBM Daeja ViewONE Virtual users
IO28755 CERTAIN MICROSOFT OFFICE WORD DOCUMENTS THROW TRUNCATION ERROR AND FAIL TO RENDER
An error occurs when opening certain MS Word documents :
"This document has been truncated because the of an error that occurred while retrieving the requested page."
Affected users: IBM Daeja ViewONE Virtual users
IO28579 ADDRESSES ENTERED IN WORD DOCUMENTS ARE GETTING DUPLICATED
When viewing a word document containing address fields, some addresses are duplicated.
Affected users: IBM Daeja ViewONE Virtual users
IO28595 CHANGE IN LIST NUMBERING IN VIEWER WHEN COMPARED TO MS WORD NATIVE CLIENT
Change in list numbering when viewing MS Word document in viewer when compared to what is seen in the actual MS Word document.
Affected users: IBM Daeja ViewONE Virtual users
IO28596 TOTAL NUMBER OF PAGES RENDERED IN VIEWER FOR MS WORD FILE IS LESS THAN THE ACTUAL TOTAL NUMBER OF PAGES
When MS Word file is opened, it is not showing all the pages and the total number of pages shown is less than the actual total number of pages..
Affected users: IBM Daeja ViewONE Virtual users
IO28605 STICKY NOTE WITH LARGE TEXT WHEN HOVERED OVER, TOOL TIP OF STICKY NOTE BLOCKS USER FROM ACCESSING THE STICKY NOTE
Sticky note with large text when hovered over, tooltip of sticky note blocks user from accessing the sticky note. When a sticky note with a large text is added and hovered over it, tool tip content of the sticky note is blocking the option to access the sticky note itself. By setting showNoteTooltips parameter to false will resolve this issue. By default showNoteTooltips is set to true.
Affected users: IBM Daeja ViewONE Virtual users
IO28616 MSG FILE SOME PART OF THE CONTENT DATA SHOWING UNDERLINE FOR PARTICULAR EMAILS
Opening outlook MSG document some part of the content data is showing underline which is not part of the original MSG document.
Affected users: IBM Daeja ViewONE Virtual users
IO28650 SOME RTF DOCUMENTS CONTAINING HYPERLINKS ARE NOT RENDERED
Few RTF files with hyperlinks contents in it are not rendered in the viewer. By ensuring that the content of file is rendered even with any failure in reading hyperlink data, issue is resolved.
Affected users: IBM Daeja ViewONE Virtual users
IO28666 TURKISH CHARACTER PROBLEM WHEN DOWNLOADING FILES
Customer enabled the fileButtonSave parameter. When downloading files having Turkish characters in their file names, the downloaded file has a different file name. The Turkish characters are not honoured and strange characters can be seen as part of download file name.
Affected users: IBM Daeja ViewONE Virtual users
IO28683 STAMP ANNOTATION MENU ITEMS ARE PARTIALLY HIDDEN
When the stamp annotation is chosen, it displays a list of items to the bottom of the stamp menu icon, for the user to choose. These lists are partially hidden sometimes within the browser window and hence complete list is not seen. By ensuring the popup panel of the menu to display within viewone container boundary and show scroll within the panel when necessary, no menu item is hidden.
Affected users: IBM Daeja ViewONE Virtual users
Configuration setting to disable client side logging to prevent performance impact to production systems
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 behaviour, 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
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 has 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 button when its Bold.
By default text is Bold.
Selecting Italic button toggles the styling between regular
and Italic font, with highlight feature of button when its 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 has an additional UI
drop down list for changing the font size.
Text annotations now have font
size dropdown combined with an editable textbox that allows users to either choose
value from list or set custom size of x.x granularity. The increment / decrement
buttons also can be used to increase / decrease the font size respectively.
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.
The optimized PDF print does not occur in the following circumstances:
As of IBM Daeja ViewONE Virtual Version 5.0.6 the following annotation types are deprecated:
These annotation types will be removed in a future version of the product.
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.
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:
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.
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.
When in document builder mode, the option to restore annotations is not supported. The following scenario explains the effects of this behavior:
Scenario 1:
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:
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.
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:
Any restrictions and/or limitations of the base or fix pack release and any subsequent ifixes, still apply to this release unless stated otherwise.
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
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.
For additional information on IE/Edge limitations, refer to the following tech notes:
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.
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.
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:
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.
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 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.
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 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.
http://www.ibm.com/legal/copytrade.shtml
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.
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: