IBM Daeja ViewONE, 5.0.13 iFix 3 Readme

This Readme document contains information about the installation of this package and about restrictions in support of IBM Daeja ViewONE, Version 5.0.13 iFix 3

Readme for: IBM Daeja ViewONE

Product or component release: Version 5.0.13

Update name: iFix 3

Prerequisites before installing IBM Daeja ViewONE, Version 5.0.13 iFix 3

You must have IBM Daeja ViewONE, Version 5.0.13 installed.

Before you install IBM Daeja ViewONE, Version 5.0.13 iFix 3:

Installing IBM Daeja ViewONE, 5.0.13 iFix 3

IBM Daeja ViewONE, 5.0.13 iFix 3 is provided as a compressed file containing the files that are needed to update Version 5.0.13 for all supported platforms.

To install this package:

  1. Unzip the compressed file into the directory where IBM Daeja ViewONE, Version 5.0.13 was installed. This action overwrites all the files that need updates in the client/v1files directory and the server/WEB-INF/lib directory.
  2. 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:

  3. Make a backup of the Daeja ViewONE 5.0.13 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.

  4. Copy the client and server files into the relevant places in your web application and ensure that the application is deployed as per your web app server specific requirements.
  5. Verify that the correct version of IBM Daeja ViewONE is deployed to the web application server. This can be done by displaying the About Box in Daeja ViewONE Virtual by clicking on the ViewONE logo in the bottom right corner. Verify that the version number 5.0.13 iFix 3 is listed at the bottom of the About Box.

Note:

  1. To upgrade to iFix 3, please ensure that both the client and the server are updated.

  2. Ensure browser cache is deleted after IBM Daeja ViewONE is upgraded.

Removing IBM Daeja ViewONE, 5.0.13 iFix 3

If you want to remove the iFix 3 from your installation and revert back to the original 5.0.13 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.13 uninstallation program to remove IBM Daeja ViewONE 5.0.13 and the iFix 3 from your system, then some of the files may be left on your file system and you will need to remove them manually.

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 5.0.13 Virtual Developer's Guide

Fixes in IBM Daeja ViewONE, 5.0.13 iFix 3

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.13&platform=All&function=all


IO29227 A VERY LARGE LINEARIZED PDF TAKES A LONG TIME TO RENDER THE FIRST PAGE IN ONDEMAND MODE

Large Linearized PDF takes long time to render the first page when the parameter pdfFetchType is set to onDemand.

Note: When the parameter pdfFetchType is set to onDemand, Viewer will open documents in single page view mode for all document types. Search and Docbuilder operations are not supported in this mode.

Affected users: IBM Daeja ViewONE Virtual users


IO29298 SOME TIFF FILE WITH INCORRECT TYPE FOR OLD SUBFILE TAG DOES NOT RENDER

Some TIFF files with an incorrect type for the TIFFTAG_OSUBFILETYPE tag will not display in the viewer. The viewer will now ignore these tags and display the image.

Affected users: IBM Daeja ViewONE Virtual users


IO29300 RIGHT CLICK ON CUSTOM STAMP ANNOTATION PREVENTS ANNOTATION TOOLBAR SHOWUP

Right-clicking a custom stamp annotation results in a JavaScript error, thus hindering the ability to edit said custom stamp annotation.

Affected users: IBM Daeja ViewONE Virtual users


IO29302 MULTIPLE WATERMARKS DO NOT RENDER PROPERLY ON RELOAD IN FILENET MODE

Watermarks are not consistently displayed upon reloading the document, and adding new watermarks causes the previous ones to disappear.

Affected users: IBM Daeja ViewONE Virtual users


IO29320 SOME SPECIFIC WORD FILES ARE RENDERED WITH OVERLAPPING TEXT

Some MS Word documents exhibit multi-page content that condenses onto a few pages, leading to overlapping text.

Affected users: IBM Daeja ViewONE Virtual users



Fixes and Features released in previous iFixes and Fix Packs

IBM Daeja ViewONE 5.0.13 iFix 2

IO28841 SOME PAGES IN A PDF DOCUMENT COME UP AS BLANK WHEN VIEWED IN VIEWER

Pages containing high resolution scanned images from PDF document does not display in viewer.

Affected users: IBM Daeja ViewONE Virtual users


IO28891 SPECIFIC PDF DOCUMENT ENCOUNTERED PROLONGED PROCESSING AND FAILED TO OPEN

The PDF Cerfa document took over a minute to process in the viewer, leading to a failed opening attempt.

Affected users: IBM Daeja ViewONE Virtual users


IO28931 INCORRECT RENDERING OF ARABIC AND ENGLISH TEXT ALIGNMENT FROM MS WORD DOCUMENT

MS Word document containing Arabic text is overlapped while rendering and the English characters with numbers are also shuffled randomly.

Affected users: IBM Daeja ViewONE Virtual users


IO28953 CONTENT LOSS IN PDF PAGES SEEN WHILE ZOOMING OUT OR CHANGING SCALE

Some pages in PDF documents suffer from complete content loss when users attempts to rescale viewing mode or zoom out operation.

Affected users: IBM Daeja ViewONE Virtual users


IO29108 STICKY NOTE NUMBERING IS NOT CONSISTENT BEFORE AND AFTER SAVING THEM

Sticky note numbering is not consistent as the number assigned to it changes on reloading the document.

Affected users: IBM Daeja ViewONE Virtual users


IO29130 ADDING A STICKY SKIPS THE COUNTER IF THERE IS A STAMP ANNOTATION WHEN VIEWING A DOCUMENT

When there is a stamp annotation in the document, adding a sticky note skips the counter affecting the numbering on them.

Affected users: IBM Daeja ViewONE Virtual users


IO29172 NEXT/PREVIOUS NAVIGATION IS BLOCKED FOR PASSWORD PROTECTED PDFS.

Next/Previous navigation in ICN is blocked for passord protected pdfs. The spinning icon continues indefinitely and user cannot continue to navigate other documents in the list.

Affected users: IBM Daeja ViewONE Virtual users


IO29177 SPECIFIC MS WORD DOCUMENT CONTENT DISAPPEAR WHEN VIEWED

Some MS Word documents do not render the complete page content, except the header and footer.

Affected users: IBM Daeja ViewONE Virtual users


IO29179 SOME PAGES IN EXCEL FILES RENDER BLURRY

Contents of excel sheet appear blurry when loaded in Viewer.

The issue occurs when,

  • A single excel sheet have large contents that are spread across multiple print pages.
  • Merged cells have large contents that are horizontally spread to adjacent print pages.
  • The excel sheet has a custom scaling factor.
  • As part of the resolution, a new server parameter is introduced that will allow user to control the scaling factor of the excel sheet to view the contents properly.

    The parameter is excelSheetScalingFactor. Users can set any value between 10 to 400. Recommended value is 100.

    The above parameter value will be ignored when the server parameter oneExcelSheetPerPage is set to true.

    Affected users: IBM Daeja ViewONE Virtual users


    IO29203 ERROR WHILE RENDERING EMAIL (*.EML) DOCUMENT IN VIEWER

    When opening an email document, an error message is displayed because the alt attribute value is invalid.

    Affected users: IBM Daeja ViewONE Virtual users


    IO29212 UNABLE TO DOWNLOAD OR PRINT DOCUMENTS

    Users were unable to download or print documents, when Daeja ViewONE was embedded with Content Navigator version 3.0.13 onwards

    Print functionality was not working on IE and IE on Edge.

    Save/Download functionality was not working on any browser. When user clicks on download button and selects either one of the option to download, the document was not downloaded.

    The functionality for print and download were missing security information in the request header (i.e. security_token) as required by ICN to authorized the requests.

    Affected users: IBM Daeja ViewONE Virtual users


    IO29244 MS WORD DOCUMENT DISPLAYING INCONSISTENT POSITIONING OF CHECKBOX AND TEXT

    Certain MS Word documents display discrepancies in showing checkbox statuses and aligning text within text areas.

    Affected users: IBM Daeja ViewONE Virtual users


    IO29269 SOME OF PDF DOCUMENT GENERATED CACHE NOT CLEARED

    The cache created by the viewer while accessing PDF files remains valid indefinitely, leading to continuous accumulation without any automatic deletion. Consequently, the server storage capacity gets depleted over time.

    Affected users: IBM Daeja ViewONE Virtual users


    IO29272 SPECIFIC MS EXCEL FILES FAILS TO RENDER WITH UNRECOGNIZED FILE FORMAT ERROR.

    Some Excel files were experiencing rendering failures, with the majority of sample files containing Hebrew content. The error message displayed was Unrecognized file format.

    Affected users: IBM Daeja ViewONE Virtual users


    IO29274 SINGLE-PAGE MS WORD DOCUMENT DISPLAYS ACROSS MULTIPLE PAGES

    When opening the single page MS Word document in the viewer, it is displaying more than one page. Which is not the expected behavior, as the document should have only one page.

    Affected users: IBM Daeja ViewONE Virtual users


    IO29294 COMBINATION OF 90° ROTATION AND ZOOM ARE NOT WORKING PROPERLY

    When rotating a PDF document by 90 degrees, the zoom area does not properly focus on the intended area.

    Affected users: IBM Daeja ViewONE Virtual users


    IBM Daeja ViewONE 5.0.13 iFix 1

    IO29044 CUSTOM ANNOTATION IS NOT BEING SAVED WHEN ADDED USING JS API

    In filenet, when using 'addAnnotation' function to create annotations using the JavaScript API, the viewer does not prompt the user to save the annotations before exiting the window.

    Affected users: IBM Daeja ViewONE Virtual users


    IO29062 ANNOTATION TOOLTIPS ARE DISABLED WHEN 'TOOLTIP' STYLE CLASS FROM BOOTSTRAP.CSS IS BEING USED IN A CUSTOM APPLICATION

    Annotation tooltips are disabled since the css class name used is 'tooltip', which is the same name used in bootstrap.css for tooltip styling in a custom application.

    Affected users: IBM Daeja ViewONE Virtual users


    IO29106 EMAIL DOCUMENT EMBEDDED WITH HEIC IMAGE FAILED TO RENDER AND JVM CRASHED

    The attempt to open an email document containing heic images resulted in an unsuccessful outcome, ultimately leading to a JVM crash caused by threads becoming unresponsive on the server.

    Affected users: IBM Daeja ViewONE Virtual users


    IO29148 MS WORD DOCUMENT DOES NOT RENDER CONTENT OF TABLE DATA

    Microsoft Word document does not display the table data correctly, Some contents are truncating from table when it is rendered.

    Affected users: IBM Daeja ViewONE Virtual users


    IO29181 MS WORD DOCUMENT DOES NOT RENDER AS NATIVE MS OFFICE APPLICATION

    Microsoft Word document is not displaying all of its content. Some text appears as a black bar and the table content data is not formatted correctly, resulting in an incorrect display format.

    Affected users: IBM Daeja ViewONE Virtual users


    IO29194 ALIGNMENT IS NOT PROPER WITH TEXT DOCUMENTS

    Rendering of text files has misalignment and is not properly showing the format.

    Affected users: IBM Daeja ViewONE Virtual users


    IO29197 THE RESTORE BUTTON OF FILLED RECTANGLE TRIGGERS NO RESPONSE.

    For a rectangle, oval, or polygon annotations with a filled color, clicking the 'restore' button in the toolbar does not bring back the previously selected color.

    Affected users: IBM Daeja ViewONE Virtual users


    IO29198 LOTS OF UNWANTED TEMP FILES PRESENT IN THE SERVER TEMP DIRECTORY

    Lots of unwanted temporary files (*.tmp) were created in the server temp directory and they were not cleaned up during the cleanup process.

    These files were generated while performing functionalities like Zoom Up/Down, Zoom Area, etc. on high resolution images.

    The files were deleted only when the server was restarted.

    As part of the resolution, the temp files will be deleted as soon as the activity is completed.

    Affected users: IBM Daeja ViewONE Virtual users


    IO29204 WHEN VIEWING A WORD DOCUMENT SOME IMAGES OF THE DOCUMENTS ARE DISPLAYED AS RED X

    Microsoft Word document is not displaying embedded word document correctly. It appears as a 'X' character image in red colour.

    Affected users: IBM Daeja ViewONE Virtual users


    IO29214 TEXT RENDERED IN REVERSE FOR MICROSOFT POWERPOINT FILES

    Microsoft powerpoint documents with text boxes are not displayed properly. It reverses the text in text box while rendering.

    Affected users: IBM Daeja ViewONE Virtual users


    IO29235 USERS SHOULD NOT BE ABLE TO ADD EXECUTABLE CODE IN VIEWONE.JS

    User can change the URL to add executable javascript code in viewone.js. This executable code can also be an alert message showing the sensitive information which is a security issue.

    Affected users: IBM Daeja ViewONE Virtual users


    IO29236 FALSE MESSAGE 'ANNOTATION SUCCESSFULLY SAVED' ON SOME ENVIRONMENTS WITH INCORRECT CONFIGURATION

    Viewer provides inaccurate confirmation messages regarding the saving of annotations. This situation arises when the annotation service fails to save the annotations, yet still returns a successful status code. Additionally, the error message is included in the header labeled X-error.

    Affected users: IBM Daeja ViewONE Virtual users


    IO29242 HUNG THREADS WHEN VIEWING EMAIL ATTACHMENT(*.EML) WITH FAULTY IMAGES

    When attempting to open email documents (.eml files) with large unsupported embedded images, the loading icon keeps spinning indefinitely in the viewer without rendering the document.

    With this release, a new image processing mechanism is introduced that will no longer process unsupported image formats.

    Instead, it will display a message as Image format not recognized! wherever it encounters such images.

    The behaviour can be controlled by the html parameter optimizedProcessingForLargeEmail. The default value is true.

    When set to false ViewONE will fallback to older image processing mechanism.

    Affected users: IBM Daeja ViewONE Virtual users


    IO29249 EML DOCUMENT WITH LARGE EMBEDDED IMAGES WILL CAUSE VIEWER TO HANG

    When user tries to open an Email with large embedded images, the viewer will hang and does not open the email document.

    Affected users: IBM Daeja ViewONE Virtual users


    IO29253 IMPROVE LOGGING TO ADD THREAD INFORMATION IN LOGS

    Daeja provides detailed information about the activities being performed through the logging service.

    However, certain processes does not log adequate information about the current thread in execution. Only child thread information are logged.

    This results into difficulty in finding the root cause whenever an error occurs as no mapping can be made between Daeja logs and Java core dump.

    As part of the resolution, thread name now includes parent thread information that will help to correlate between Java core jump and Daeja logs.

    Affected users: IBM Daeja ViewONE Virtual users


    IO29258 A TABLE IN A MS WORD DOCUMENT IS NOT RENDERED CORRECTLY

    Microsoft Word document which includes a table, does not render it. Any text that appears after the table is not displayed too.

    Affected users: IBM Daeja ViewONE Virtual users


    IO29265 STRIKETHROUGH FORMATTING IN MSG FILES ARE NOT RENDERED PROPERLY

    Email documents that contain strikethrough formatting will appear as regular text without preserving the formatting.

    Affected users: IBM Daeja ViewONE Virtual users


    IBM Daeja ViewONE 5.0.13

    IO28449 DOTTED LINES ARE SEEN IN CERTAIN FIELDS IN A PDF DOCUMENT

    Some PDF documents renders dotted lines in place of text in the text box field of dynamic forms.

    Affected users: IBM Daeja ViewONE Virtual users


    IO29188 INDENTED TEXT NOT APPEARING IN EMAIL DOCUMENTS

    Opening an email document with indented text content is not rendered.

    Affected users: IBM Daeja ViewONE Virtual users


    IO29189 ASSISTIVE TOOLS LIKE SCREEN READER READS 'DOWNLOAD DOCUMENT BUTTON' AS 'SAVE DOCUMENT'

    Screen reader reads download document button as save document.

    Affected users: IBM Daeja ViewONE Virtual users


    IO29193 ANNOTATION WITH SEMITRANSPARENT FILL COLOR BECOMES OPAQUE ON RELOAD IN FILENET

    Rectangle, oval and polygon annotations created with color filled and transparent enabled, lose transparency on reload in filenet.

    Affected users: IBM Daeja ViewONE Virtual users


    IO29206 IBM DAEJA VIEWONE REDIRECTED TO A LOGIN PAGE.

    DocN request was redirecting to single sign on page because of security header changes.

    To fix the same, we have made code changes to run the security header changes only for ICN since this change was done for custom header implementation only on ICN.

    Affected users: IBM Daeja ViewONE Virtual users


    IO29216 BOUNCY CASTLE 1.47 VULNERABILITY IN CLIENT RESOURCE

    Client folder that contained older version of Bouncy Castle was vulnerable. So it is modified to contain the appropriate version of Bouncy Castle.

    Affected users: IBM Daeja ViewONE Virtual users


    CSDV-41 Add configuration option for avoiding field updates of MS Word documents

    When MS Word documents are generated from MS Word templates and use the field function Date, the date automatically updates with the current date

    The decision to update the Date field to the current date or to maintain it to the last computed date is now upto the discretion of the customer.

    We have introduced a server side param to handle the same. The default value of the param is false, any change to the param needs a server restart for changes to take effect

    Note: A new server side param called isProtectedDateFlag is introduced, which has the below behavior:

    If true: In this scenario irrespective of protected or un-protected word document current date and time will be the last computed field value stored in the document.

    If false: In this scenario irrespective of protected or un-protected word document current date and time will always be the current date and time.

    Note: savedate, createdate, printdate do not depend on above parameter.


    CSDV-64 Add support of native PDF annotation elements to PDF file rendering

    IBM Daeja ViewONE now supports native PDF annotations in the PDF documents. This enables users to interact with the native PDF annotations in the document.

    This includes text widgets, form elements, hightlight, line, polygon etc.


    Integrate cmaps within viewer to remove external dependency

    Compressed CMAP (.bcmap) are integrated and configured by default in ViewONE Virtual to view legacy PDF documents.

    User can customize their cmap location with the usage of HTML parameter cmapLocation to override this default configuration.

    Note: Ensure to set proper configuration (cmapLocation and cmapPacked) to override default CMAP configuration.


    Additional Release Notes

    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:

    Deprecation of Annotation Types

    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.

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

    Daeja ViewONE as an Integrated solution

    When running 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.

    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:

    Any restrictions and/or limitations of the base or fix pack release and any subsequent ifixes, still apply to this release unless stated otherwise.

    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: