IBM Daeja ViewONE, 5.0.12 iFix 1 Readme

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

Readme for: IBM Daeja ViewONE

Product or component release: Version 5.0.12

Update name: iFix 1

Prerequisites before installing IBM Daeja ViewONE, Version 5.0.12 iFix 1

You must have IBM Daeja ViewONE, Version 5.0.12 installed.

Before you install IBM Daeja ViewONE, Version 5.0.12 iFix 1:

Installing IBM Daeja ViewONE, 5.0.12 iFix 1

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

To install this package:

  1. Unzip the compressed file into the directory where IBM Daeja ViewONE, Version 5.0.12 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.12 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.12 iFix 1 is listed at the bottom of the About Box.

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

Removing IBM Daeja ViewONE, 5.0.12 iFix 1

If you want to remove the iFix 1 from your installation and revert back to the original 5.0.12 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.12 uninstallation program to remove IBM Daeja ViewONE 5.0.12 and the iFix 1 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.12 Virtual Developer's Guide

Fixes in IBM Daeja ViewONE, 5.0.12 iFix 1

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


IO28741 LAYOUT CHANGES WHEN THE CONTENT LENGTH IS LONG IN XLSX, XLS FORMAT

If an excel document has too many columns in a sheet, the content of 1 sheet is rendered as 2 or more pages.

To resolve this problem, new server side parameter oneExcelSheetPerPage should be set to true. By default this parameter is set to false.

Note: Server restart is required after setting a server side parameter.

Affected users: IBM Daeja ViewONE Virtual users


IO29023 NIMBUS SANS BOLD FONT DOES NOT RENDER IN PDF DOCUMENTS

PDF documents with text in Nimbus Sans bold fail to render. By setting the disableFontFace parameter to true, these texts are now rendered correctly.

Affected users: IBM Daeja ViewONE Virtual users


IO29031 MS WORD DOCUMENT CONTAINING HEBREW IN TABLE RENDERED INCORRECTLY

Text is aligned to the left instead of right for MS Word document with Hebrew in table.

Affected users: IBM Daeja ViewONE Virtual users


IO29041 EMAIL DOCUMENTS CONTAINING INVALID STYLE ATTRIBUTE FAIL TO RENDER

Opening email documents containing invalid style attribute like px and percentage fail to render and following error message is displayed 'Unable to display document: Failed to load document.' Error populated as unable to parse HTML email content.

Affected users: IBM Daeja ViewONE Virtual users


IO29049 POWERPOINT DOCUMENT THAT CONTAINS HEBREW IN A TABLE NOT OPENING CORRECTLY

When opening a Powerpoint document that contains Hebrew in a table, a part of the document is cut off and the table is shifted to the left.

Affected users: IBM Daeja ViewONE Virtual users


IO29053 EMAIL DOCUMENT IS RENDERED INCORRECTLY WITH OVERLAPPING WORDS

When opening an email document, some text content of the document is overlapping and unreadable.

Affected users: IBM Daeja ViewONE Virtual users


IO29054 A WORD DOCUMENT IS RENDERED INCORRECTLY WITH OVERLAPPING WORDS

When opening a word document, some text content of the document is overlapping and unreadable.

Affected users: IBM Daeja ViewONE Virtual users


IO29058 EMAIL DOCUMENTS CONTAINING INVALID FONT-SIZE VALUE FAIL TO RENDER

Opening email documents containing invalid font-size value fail to render and following error message is displayed 'Unable to display document: Failed to load document'. Error populated as unable to parse HTML email content.

Affected users: IBM Daeja ViewONE Virtual users


IO29076 CACHE DIRECTORY IS REMOVED INTERMITTENTLY WHEN APP SERVER STOPS

Cache directory disappears when restarting the application server. In other words, if the cache directory is configured (i.e. /docstore folder) as <<DIRECTORY>>\dir_cache
The entire "dir_cache" directory is removed when the application server is stopped. This issue can occur when the application is not serving any user request and idle for more than the cacheAgeLimit time.

Affected users: IBM Daeja ViewONE Virtual users



Fixes and Features released in previous iFixes and Fix Packs

IBM Daeja ViewONE 5.0.12

IBM Daeja ViewONE, Version 5.0.12, provides the following new features:


CSDV-52 Javascript api to search and highlight a text in pdf document

JS method that searches and highlights a text passed in the method parameter, in a pdf document

searchAndHighlightText(String searchText)

Searches and highlights the text occurrences that is specified by the searchText parameter, in a pdf document.

Example

ViewONE.searchAndHighlightText('March')

ViewONE.searchAndHighlightText('and other')

ViewONE.searchAndHighlightText('235')

The method has no effect when empty string or null is passed as parameter.


CSDV-46 Support for linearized PDF by adding range requests and configurable HTML attribute for different fetch combinations

Support for linearized/streamed PDF is enabled from Daeja ViewONE 5.0.12 onwards in order to avoid having to retrieve the entire document to the browser prior to rendering the initial pages.

You can render PDF file document by configuring the HTML parameter pdfFetchType. This parameter is applicable for non-linearized pdf files also.

You have three modes to fetch and render the PDF documents. You can configure them by setting the new HTML parameter pdfFetchType. The parameter has three following possible values:

Note:This is applicable only for PDF Documents


CSDV-54 Support for Tablet with Daeja ViewONE

From this release, Daeja ViewONE is supported on tablet.

Following two HTML Parameters are required for viewer to load in tablet browser:

<param name="tabletMode" value="true"/>
<param name="deviceInterface" value="desktop"/>

Some features which are supported in PC/desktops will not be supported in Tablet view. Also Page view is set by default in Tablets.

Note :


CSDV-11 Support for text document rendering with carriage return

Daeja ViewONE now supports rendering of text document.

User can specify custom font to display the text document using the server parameter enhancedTextFont= < fontname >

Example:

 enhancedTextFont=Arial 

If the custom font is unavailable, then Daeja relies on availability of fallback fonts, either Courier or Arial Unicode MS to render the document.

Font specified should be available in the server.

To turn off this feature, set the server parameter enhancedTextSupport=false

Note: Document builder and PageN are not supported for text documents.


CSDV-62 Optimization to support both legacy and latest browsers simultaneously for PDF documents.

Through this feature, we have optimized the rendering of PDF documents both on legacy and latest browsers when used simultaneously.


CSDV-44 Support for Watermark

Watermark is supported on all pages in a document while rendering, printing and on redaction.

User has the flexibility to choose the position, size, and rotation of the watermark.

Users can add watermarks on any page of the document. Watermark can also be deleted/edited and is always transparent.

The default color is light gray. However, the color of the watermark can be customized.

User can use following JavaScript APIs for adding and deleting watermark:

1. addWatermark(String annotationProperties) adds a new watermark on all pages.

Syntax

    ViewONE.addWatermark()

Example:

    ViewONE.addWatermark('[TEXT]<P>X = 482<P>Y = 390<P>WIDTH = 579<P>HEIGHT = 269<P>FONTTYPE = Arial<P>FONTHEIGHT = 122.4<P>FONTSIZEORIGINAL = 24<P>SEMITRANSPARENT = 1<P>TEXT = test<P>WATERMARK = 1<P>TRANSPARENT = 1<P>LABEL = Text1');

2. deleteWatermark() deletes all the watermarks added to the document.

Syntax

    ViewONE.deleteWatermark();

Limitations:

1. User need to refresh the viewer to see saved watermarks on all the thumbnails

2. User may notice minor difference in the color/transparency of the watermark in print and redaction



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

IBM Daeja ViewONE 5.0.11 iFix 5

IO29003 UPDATING THE TEXT OF AN ANNOTATION USING JAVASCRIPT API MODIFIES THE FONT SIZE

Updating the text annotation using modifyAnnotation() Javascript method updates the font size in FileNet mode.

Affected users: IBM Daeja ViewONE Virtual users


IO29004 EMAIL DOCUMENTS CONTAINING UNSUPPORTED TABLE WIDTH ATTRIBUTE FAIL TO RENDER

Opening email documents containing unsupported width attribute in table 'width:-webkit-cal' are not rendering.

Affected users: IBM Daeja ViewONE Virtual users


IO29017 EML DOCUMENTS CONTAINING INVALID UNICODE CHARACTERS FAIL TO RENDER

Opening email document containing invalid Unicode characters fail to render. Following error is thrown

Unable to display document: Failed to load document.

Affected users: IBM Daeja ViewONE Virtual users


IO29028 EMAIL DOCUMENTS CONTAINING INVALID IMG TAGS FAIL TO RENDER

Opening email documents containing invalid img tags fail to render. Following error is thrown

Unable to load documents while retrieving the request page.

Affected users: IBM Daeja ViewONE Virtual users


IO29030 ROTATE LEFT FUNCTIONALITY ISN'T WORKING PROPERLY WITH ROTATECOUNTERCLOCKWISE AS IT IS CASESENSITIVE

Javascript methods are case sensitive so without the camel casing method rotateCounterclockwise() is not working as expected in rotateLeft().

Affected users: IBM Daeja ViewONE Virtual users


IBM Daeja ViewONE 5.0.11 iFix 4

IO28907 VIEWING AN EMAIL DOCUMENT WITH LENGTHY SUBJECT, EMAIL IS RENDERED BUT SUBJECT GETS TRUNCATED

Opening an email document with a long subject, email is rendered but subject gets truncated and does not render completely.

Affected users: IBM Daeja ViewONE Virtual users


IO28933 EML DOCUMENT NOT RENDERED COMPLETELY, SOME CONTENTS IN THE DOCUMENT ARE MISSING

While rendering an email document, some contents are missed and email is not rendered completely.

Affected users: IBM Daeja ViewONE Virtual users


IO28951 UNABLE TO SAVE ANNOTATION AFTER VIEWING A STICKY NOTE ANNOTATION CREATED BY DIFFERENT USER

If user 1 had added a sticky note and user 2 views the read-only sticky note, the user2 is unable to add and save any new annotations it fails with the following error "Annotation cannot be saved".

Affected users: IBM Daeja ViewONE Virtual users


IO29005 MS OFFICE DOCUMENT NOT RENDERED PROPERLY WHEN ARABIC TEXT AND JUSTIFY OPTIONS ARE USED

While rendering MS office document with Arabic text and Justify options, the paragraph text rendered from left to right instead of right to left.

Affected users: IBM Daeja ViewONE Virtual users


IBM Daeja ViewONE 5.0.11 iFix 3

IO28627 COMBINATION OF 90% ROTATION AND ZOOM ARE NOT WORKING PROPERLY

Combination of 90 rotation and zoom are not working. After rotation if user tries zoom area operation, a different part of the page is zoomed-in.

Affected users: IBM Daeja ViewONE Virtual users


IO28206 SPACES BETWEEN WORDS AND CARRIAGE RETURN IS MISSING FROM COPIED TEXT IN SOME SPECIFIC PDF DOCUMENTS

In some specific PDF documents, spaces between words and carriage return not honored and missed from the copied text.

Affected users: IBM Daeja ViewONE Virtual users


IO28563 SEARCH FUNCTION DOES NOT WORK ON WORDS SPREAD ACROSS DIFFERENT SPANS IN A PDF DOCUMENT

In a PDF document, if a single word or series of word are spread across different span elements and if the same word is used as keyword for search, then the search action does not give any result.
With this fix, users will now be able to search words that are spread across different span elements.

Limitations:

  • If a word is split across different span elements and if the user selects Whole word search, then the search action does not give any result.
  • If user enters search keywords that are spread across lines in continuation, then the search action does not give any result.
  • Affected users: IBM Daeja ViewONE Virtual users


    IO28822 EML DOCUMENTS CONVERTED FROM IBM NOTES TO EML FAIL TO RENDER

    Opening email document converted from IBM Notes to EML fail to render, following error is thrown "Unable to display document: Failed to load document, status: Unrecognized file type message/rfc822".

    Affected users: IBM Daeja ViewONE Virtual users


    IO28833 IN CONTAINERIZED ENVIRONMENTS,PRINTING MULTIPLE PDF DOCUMENTS RESULTS IN GARBAGE CHARACTERS AS PRINT PREVIEW OUTPUT

    In containerized ICN environment, with client side printing enabled, multiple PDF document print displays garbage characters as print preview output.

    Affected users: IBM Daeja ViewONE Virtual users


    IO28959 NUMBER ASSIGNED TO A NEW STICKY NOTE ANNOTATION AFTER VIEWING AN EXISTING STICKY NOTE IS INACCURATE

    Number assigned to a new sticky note annotation after viewing an existing sticky note is inaccurate. The counter starts decreasing from the last count instead of incrementing.

    Affected users: IBM Daeja ViewONE Virtual users


    IO28970 EMAIL DOCUMENTS WITH INVALID CHARACTERS FAIL TO RENDER AND THROW FOLLOWING ERROR MESSAGE "UNABLE TO PARSE HTML EMAIL CONTENT ERROR OCCURRED"

    Opening email document with invalid characters fail to render and following error message is displayed "Unable to display document: Failed to load document. Error populated as unable to parse HTML email content".

    Affected users: IBM Daeja ViewONE Virtual users


    IBM Daeja ViewONE 5.0.11 iFix 2

    IO28811 EMAIL DOCUMENT WITH TABLES DOES NOT RENDER THE TABLE CONTENT COMPLETELY

    MSG documents having tables in their content, when rendered in viewer only half of the table contents are visible.

    Affected users: IBM Daeja ViewONE Virtual users


    IO28911 FORMATTING ISSUE IN WORD DOCUMENT AND A SUPERSCRIPT IS REPLACED BY A WORD 'ERROR'

    A word document is showing formatting issue and a word 'Error' is replacing a superscript letter on rendered document.

    Affected users: IBM Daeja ViewONE Virtual users


    IO28923 EMAIL DOCUMENT WITH ATTACHMENT FAILS TO RENDER WHEN ATTACHMENT HAS MISSING FILENAME

    Attachment in Email document with missing filename attribute in header fails to render when opened.

    Affected users: IBM Daeja ViewONE Virtual users


    IBM Daeja ViewONE 5.0.11 iFix 1

    IO27983 PRINTING PDF DOCUMENTS WITH SPECIAL CHARACTERS IN TEXT ANNOTATIONS CAUSES SERVER SIDE PRINT PROCESS TO OCCUR

    Pdf with text annotations containing special characters will go to the server-side print process which consumes more time and the resultant file size is larger.

    Affected users: IBM Daeja ViewONE Virtual users


    IO28398 QR CODE PRESENT IN THE PDF FILE IS NOT CLEARLY VISIBLE (BLURRED) WHEN OPENED

    QR code present in the PDF file is not clear. So scanning the QR code did not work properly.

    Affected users: IBM Daeja ViewONE Virtual users


    IO28472 MS WORD DOCUMENT MISSING SOME SECTION OF DATA WHILE IT IS RENDERED

    Opening certain MS word document does not rendered all the pages, some pages are missing. For example, page 1 and 2 would be displayed but page 3 and 4 are not displayed.

    Affected users: IBM Daeja ViewONE Virtual users


    IO28691 SOME PDF PAGES WHICH HAVE DATA IN TABULAR FORMAT DO NOT RENDER CONTENT

    Some PDF documents display only table outlines where as contents of table are missing when rendered.

    Affected users: IBM Daeja ViewONE Virtual users


    IO28748 CONTENT OF SOME PDF DOCUMENTS ARE BLACKED OUT IN REDUCED SIZE LIKE THUMBNAILS

    Content of some PDF documents like form fields are redacted when viewed in thumbnails. Also same effect is observed when main page is zoomed out for more than 5 times.

    Affected users: IBM Daeja ViewONE Virtual users


    IO28752 CHINESE CHARACTERS ARE GARBLED WHILE RENDERING IN SOME PPT, PPTX, MSG AND EML FILES WHEN RENDERED

    Some chinese characters are not getting rendered properly, rendered as square boxes in some PPT, PPTX, MSG and EML files when rendered.

    Affected users: IBM Daeja ViewONE Virtual users


    IO28794 SOME TIF DOCUMENT PAGES RENDER PARTIAL CONTENT WITH HORIZONTAL GREY STRIPES

    Some pages of the TIF files are not rendered properly, original content of those pages appear as horizontal grey stripes.

    Affected users: IBM Daeja ViewONE Virtual users


    IO28808 SOME SECURITY ENABLED PDF DOCUMENTS FAIL TO RENDER IN CHROME AND EDGE

    Some PDF documents with document security enabled are not rendered with Chrome and edge browser.

    Affected users: IBM Daeja ViewONE Virtual users


    IO28820 IN WORD DOCUMENTS TIME FIELD SHOULD BE UPDATED AS CURRENT TIME

    Opening word documents with time field should always display current time and date mentioned in the time field.

    Affected users: IBM Daeja ViewONE Virtual users


    IO28874 TEXT SELECTION IS SHIFTED ON SOME PDF DOCUMENTS

    For some PDF documents, when the user opens a document and search for a text, the selected text is shifted and not centered.

    Affected users: IBM Daeja ViewONE Virtual users


    IO28902 RIGHT-CLICK ON ROTATE ACTIONS DOES NOT ROTATE ALL PAGES

    Right-click on the rotate buttons should rotate all the pages in a multipage document. Below JS methods are added that affects a multipage document.

    rotateAllClockwise It rotates all the pages in a multipage document in clock wise direction.

    rotateAllCounterClockwise It rotates all the pages in a multipage document in counter clock wise direction.

    roatetAll180 It rotates all the pages in a multipage document in 180 degrees direction.

    Affected users: IBM Daeja ViewONE Virtual users


    IO28909 SOME PDF DOCUMENTS ARE NOT RENDERED PROPERLY WHEN TEXT SELECTION TOOL IS ENABLED

    When user clicks on the text selection tool, if the pdf document has multiple pages with different dimensions,
    then for pages that have smaller dimensions than the first page, the bottom part of those page are not displayed completely.

    Affected users: IBM Daeja ViewONE Virtual users


    IO28918 SINGLE CUSTOM STAMP MENU SHOWS ONLY HALF OF THE LABEL

    When custom stamp menu has a single item, there is a horizontal scrollbar shown that hides the menu label display.

    Affected users: IBM Daeja ViewONE Virtual users


    IO28922 SOME MS WORD DOCUMENTS FAIL TO RENDER AND THROW FOLLOWING ERROR MESSAGE "DOCUMENT HAS BEEN TRUNCATED"

    Some MS Word documents fail to render and throw following error message :

    This document has been truncated because the of an error that occurred while retrieving the requested page.

    Affected users: IBM Daeja ViewONE Virtual users


    IO28927 SOME WORD DOCUMENTS ARE NOT RENDERED COMPLETELY

    Some Word documents are rendered with only part of the content and not complete document.

    Affected users: IBM Daeja ViewONE Virtual users


    IO28949 CERTAIN SEARCH KEYWORDS ESPECIALLY WITH A SPACE DOES NOT RETURN ANY RESULTS

    Search functionality does not return any results when specific keywords that have spaces were searched in a pdf document.

    Affected users: IBM Daeja ViewONE Virtual users


    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.12 as a component inside IBM Content Navigator, the minimum supported version of ICN is 3.0.13, 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: