OpenText Imaging WebViewer CE 21.

Release Notes

Product Released: 2020-01-29

Release Notes Revised: 2022-04-22

Contents
1 Introduction .................................................................................................................................... 4
1.1 Release Notes revision history .................................................................................................. 4

2 About OpenText Imaging WebViewer .......................................................................................... 4

2.1 New features.............................................................................................................................. 5
2.1.1 Imaging PDFExtensions with Web Viewer ................................................................... 5
2.1.2 PDF Library upgrade .................................................................................................... 5
2.1.3 Introduced new config parameter 'XHRFormSubmission' ............................................ 5
2.2 Discontinued and deprecated features ...................................................................................... 5

3 Packaging and documentation ..................................................................................................... 5

3.1 Packaging and delivery information .......................................................................................... 5
WebViewer Docker Container ................................................................................................... 6
3.2 Related documentation .............................................................................................................. 6
3.3 Documentation errata ................................................................................................................ 6

4 Supported environments and compatibility ................................................................................ 8

4.1 Virtualization guidelines ............................................................................................................. 8
4.2 Supported systems .................................................................................................................... 9
4.2.1 System requirements .................................................................................................... 9
4.2.2 Supported operating systems and browsers ................................................................ 9
4.2.3 Supported SAP GUI versions ..................................................................................... 10
4.2.4 Supported OpenText Content Server version............................................................. 10
4.2.5 Protocols and security ................................................................................................ 12
4.2.6 Document formats ...................................................................................................... 12
4.3 OpenText product compatibility ............................................................................................... 14
4.4 Language support .................................................................................................................... 14

5 Installation and upgrade notes ................................................................................................... 15

5.1 Installation notes ...................................................................................................................... 15
5.1.1 Prerequisites to install WebViewer in OpenJDK ........................................................ 15
5.1.2 WebViewer Server on one workstation ...................................................................... 15
5.2 Upgrade notes ......................................................................................................................... 17

6 Patches ......................................................................................................................................... 18
6.1 Hotfixes .................................................................................................................................... 18
6.1.1 Hotfix installation ........................................................................................................ 18
6.1.2 Available hotfixes ........................................................................................................ 18

OpenText Imaging WebViewer 21.1 Release Notes 2

 6.1.3 Updates ...................................................................................................................... 19

7 Fixed issues .................................................................................................................................. 19

8 Known issues ............................................................................................................................... 21

9 Contact information ..................................................................................................................... 31

OpenText Imaging WebViewer 21.1 Release Notes 3

1 Introduction
These Release Notes provide an overview of OpenText Imaging WebViewerCE 21.1, including new
features, delivery information, and supported platforms.

OpenText recommends that you read these Release Notes in conjunction with the documentation
included with the software package. If any conflicts exist, the Release Notes supersede the other
documentation.

We also recommend that you check OpenText My Support (https://support.opentext.com) for any patches or
documentation updates that may have been posted after the initial release of this product.

1.1 Release Notes revision history

Revision date Sections revised Description of revisions

2021-01-12 First release. All new content.

Updated Document Errata

3.3
SAP GUI 7.7 support
4.2
Language pack support
2021-04-22 4.4
Hotfix details
5
Known issues
7

Adopt OpenJDK – OpenJ9 compatibility

4.2.2
Language pack support (AR, CA, ZH_TW, KK,
2021-11-18 4.4
SV, UK, KO, DA, PL, TR, NO)
7
Known issues

2022-02-07 6.1.3 Modified Section 5 and 6, made it inline with

Release Notes latest Template
8 Known issues
6.1.2 Hotfix for signed pdf documents

2022-04-22 8 Updated Known issues about encoding of

configuration parameters

2 About OpenText Imaging WebViewer

This section provides an overview of OpenText Imaging WebViewer CE 21.1.

OpenText Imaging WebViewer (WebViewer) is a web application for displaying and printing documents in
web-based scenarios and for appending comments to these documents. The documents may be stored in
OpenText Archive and Storage Services (formerly known as Livelink ECM – Archive Server) or any other
repository.
WebViewer is used with the following products, which provide the interface for the end-user:
• OpenText Archiving and Document Access for SAP Solutions

• OpenText DocuLink for SAP Solutions

• OpenText Extended ECM for SAP Solutions

• OpenText Core Archive

• OpenText Employee File Management for SAP Solutions

OpenText Imaging WebViewer 21.1 Release Notes 4

 • OpenText TCP – Transactional Content Processing
• OpenText Imaging Reviews and Notes module for OpenText Content Server

2.1 New features

OpenText Imaging WebViewer CE 21.1 includes the following new features.

2.1.1 Imaging PDFExtensions with Web Viewer

Elimination of PDF Extension as a stand-alone component and price list item
Included the ability to view PDF documents and add annotations for PDF documents in Imaging WebViewer
without any additional license configuration.

2.1.2 PDF Library upgrade

Datalogics Adobe PDF Library v10 to v18 upgrade for enhanced support.

2.1.3 Introduced new config parameter 'XHRFormSubmission'

XHRFormSubmission enables or disables the submission of forms using XMLHttpRequest. This enables
seamless add note, save, and print functionalities.

2.2 Discontinued and deprecated features

The following features have been discontinued in this release due to a technology upgrade:

• Removed the configuration “vu_focus_on_load” because it is no longer relevant.

• IBM WebSphere Application server and IBM AIX Operating System are no longer supported from
Imaging WebViewer 21.1 version onward.
• OpenText Imaging WebViewer is no longer delivered as a single ISO image and is replaced with an
individual executable.
Note: Manual deployment files will not be distributed from the next Imaging WebViewer version.

3 Packaging and documentation

Downloads and documentation for OpenText Imaging WebViewer are available on OpenText My Support
(https://support.opentext.com).

Note
Documentation that is installed with the product or packaged with the
product download is current at the time of release. Documentation
updates made after a release are available for download on OpenText
My Support (https://support.opentext.com).

3.1 Packaging and delivery information

Imaging WebViewer 21.1 is delivered as an individual executable for Windows and Linux platforms. It is
available on OpenText My Support (https://support.opentext.com).

Web Viewer is distributed in three ways:

• As an MSI for the Windows platform
• As a tar.gz file for Linux platforms

OpenText Imaging WebViewer 21.1 Release Notes 5

 • As a manual deployment file, that is a ZIP file for both the Windows and non-Windows platform

WebViewer Docker Container

As a part of the 21.1 release, the WebViewer Docker Container is available for users for rapid deployment.
A container is a standard unit of software that packages the code and its dependencies, so the application
runs quickly and reliably from one computing environment to another. The WebViewer container image is a
lightweight, standalone, executable package of software that includes Tomcat, OpenJDK, and WebViewer.

3.2 Related documentation

For additional information about OpenText Imaging WebViewer, or for supplemental information about
related products, refer to the following documents, which are available on OpenText My Support
(https://support.opentext.com).

• OpenText Imaging WebViewer User Guide

• OpenText Imaging WebViewer Installation and Administration Guide

The Release Notes are updated continually. The latest version and further technical information are
available on OpenText My Support (https://support.opentext.com).

3.3 Documentation errata

a) Revised steps for upgrading Imaging WebViewer in Windows and non-Windows System (Chapter 5 –
Upgrading Web Viewer of Installation guide)

Upgrade is not supported directly, and can be achieved by following below steps

The current version of WebViewer must be uninstalled before installing a new version, follow the below
steps

1. OpenText recommends taking back-up the following files (if exists):

o <WebViewer>\WEB-INF\wevconfig
o <WebViewer>\WEB-INF\cred
o <WebViewer>\WEB-INF\csauth
o <WebViewer>\UI\component\menubar\menu.xml
o <WebViewer>\UI\component\toolbar\toolbar.xml
o In non-windows platforms, make a note of the configurations added in
<TOMCAT_HOME>\bin\setenv.sh
2. Uninstallation of existing WebViewer
o In Windows platform, Uninstall WebViewer from Add or Remove Programs section of
Control Panel.
o In non-windows platforms,
 Stop Tomcat and delete the below files/folders
 <TOMCAT_HOME>\webapps\WebViewer
 <TOMCAT_HOME>\webapps\WebViewer.war
 PDF Libs, Office Libs, and OS libs directories

3. Install WebViewer latest version

o In windows platforms, execute the Imaging_Web_Viewer_<version>.msi(Refer 3.1.2 for
more details)
o In non-windows platforms, execute the WebViewer-<version>-<platform>.sh (Refer 3.1.3
for more details)
4. Restoring the backup copied in Step 1
o Stop Tomcat
OpenText Imaging WebViewer 21.1 Release Notes 6
 o Replace the files in respective directories with the above copied files
o In non-windows platforms, append the configurations to setenv.sh (if required).
o Restart Tomcat.

Steps to uninstall Imaging WebViewer in Linux systems:

In Chapter 4: "For other operating systems you must remove the Web Viewer bits manually." manual
steps are given below:

• In non-windows platforms,
o Stop Tomcat and delete the below files/folders
o <TOMCAT_HOME>\webapps\WebViewer
o <TOMCAT_HOME>\webapps\WebViewer.war
o PDF Libs, Office Libs, and OS libs directories

b) Description for vu_WatermarkText in the Installation and Configuration Guide

7.2.23 vu_WatermarkText
• Default value: <empty>
• Description: Specifies watermark text.
Use the following control characters to lay out the text:

\\n Line break

\\t Add 4 spaces
\\\\ Add a backslash

Use the following placeholders to modify the text dynamically:

%[USERNAME] or %[SAPUSER] User name (case sensitive)

%{*docId} ID of the document
%{*arcId} ID of the logical archive
%{*title} Title of the document
%{*page} Current page
%{*pages} Total number of pages
%a Weekday (abbreviated)
%A Weekday (full name)
%b Month (abbreviated)
%B Month (full name)
%c Date in the format mm/dd/yy
%D Day (abbreviated)
%h Hour in the format hh

OpenText Imaging WebViewer 21.1 Release Notes 7

 %I Hour (abbreviated)
%m Minute in the format mm
%M Minute (abbreviated)
%s Second in the format ss
%p Half-day
%Y Year
%x Time in the format hh:mm:ss
%z Time zone (abbreviated)
%Z Time zone (full name)

You can configure different watermark texts for different logical archives. To do so, add
"vu_WatermarkText_<ArchiveID>= ..." in wevconfig file which is located at "..\webapps\WebViewer\WEB-
INF\wevconfig"
Note: The above wevconfig file is only created if there are any changes made in administrative console. For
example, change vu_WatermarkText = "text" in WebViewer administrative console.

4 Supported environments and compatibility

This section provides details about supported platforms, systems, and versions.

4.1 Virtualization guidelines

WebViewer 21.1 can be generally deployed in a virtualized environment. The following prerequisites must
be fulfilled to achieve results identical to those known from dedicated hardware:

• Only type 1 full virtualization (see http://en.wikipedia.org/wiki/Hypervisor) is supported.

OpenText does not support type 2 virtualization, partial virtualization strategies, or para-
virtualization. The full virtualization strategy is known as bare-metal embedded hypervisor
(type 1 hypervisor).
• Emulated virtualization, entry level or desktop virtualization technologies including the
technologies harnessing the type 2 hypervisor technology (hosted hypervisor mentioned in
the previous point) from full virtualization domain are not supported. The required
virtualization tool must be designed for low overhead and near-native performance.
• The WebViewer solution works intensively with file systems. The product uses multi-level
cache mechanism, and the second level cache is located on a hard drive unit. It is essential
that WebViewer has non-emulated access to a fast HDD unit. OpenText recommends that
every logical system on a virtualized HW host will receive a dedicated HDD unit. For
example, if a virtualization server hosts three logical servers, and each server hosts a single
copy of WebViewer, three physical HDD units shall be available on the virtualization server
and each copy of WebViewer shall receive a dedicate copy.
• By selecting a virtualization strategy other than the ones described above, OpenText
cannot guarantee functionality or performance data. The sizing guide delivered together
with the product starting in version 10.0.0 onward does not apply for installations using
other virtualization strategies than the one recommended above.

OpenText Imaging WebViewer 21.1 Release Notes 8

4.2 Supported systems
4.2.1 System requirements
OpenText recommends planning the deployment, sizing, and installation of your WebViewer system. For
more information, see the chapter “Planning the WebViewer System” in the Installation and Configuration
Guide on My Support.

WebViewer should preferably be installed on a dedicated server or virtualized environment. A load-

balanced scenario should be considered for larger installations. The number of servers depends on the
number of active users who are working with WebViewer at the same time.

Note: On Linux systems, if the setenv.sh file is unavailable, the WebViewer installer creates a
new setenv.sh file along with its entries. If the setenv.sh file exists, the WebViewer installer appends the
configuration entries to it. To enable Archive Center to work with WebViewer, OpenText recommends that
you review the setenv.sh file after the installation and remove any duplicate or conflicting entries.

WebViewer is a zero-footprint solution and does not require a strong client computer. The client must have
one of the supported browsers installed.

4.2.2 Supported operating systems and browsers

WebViewer CE 21.1 supports the following operating systems, application servers, JDK versions, and
browsers:

Operating Systems
• Microsoft Windows Server 2012 R2 64-bit
• Microsoft Windows Server 2016 64-bit
• Windows Server 2019 64-bit
• RedHat Enterprise Server 8 64-bit
• SUSE Linux Enterprise Server 12
Application Servers
• Apache Tomcat 8.5.51 or higher
• Apache Tomcat 9.0.31 or higher

Caution: Versions lower than Tomcat 8.5.51 and Tomcat 9.0.31 may have
vulnerability issues.

JDK Version
• Adopt OpenJDK 11.0.8 (WebViewer certifies with OpenJDK11 as it is LTS)
• Adopt OpenJDK – OpenJ9

Client
The following browsers and operating systems are supported.

OpenText Imaging WebViewer 21.1 Release Notes 9

 Browser Operating system Support level

Windows 10 64-bit versions C

Internet Explorer 11.0
Internet Explorer 11.0 64-bit
Microsoft Edge Chromium
Chrome 87 and higher
Firefox 78.x ESR

Internet Explorer 11.0 Windows 8.1 64-bit C

Internet Explorer 11.0 64-bit
Microsoft Edge Chromium
Chrome 87 and higher
Firefox 78.x ESR
MAC OS 10.x C
Safari 12

C = Certified

This platform was used for full regression testing with this release of WebViewer by OpenText. Customer use
is fully supported by OpenText Customer Support.

S = Supported

This platform received limited testing for this release of WebViewer by OpenText. Customer use is fully
supported by OpenText Customer Support.

Note:

Edge (based on Chromium) is alternative browser control for use in the SAP GUI 7.7 HTML Control – for
becoming independent of the Internet Explorer Control.Imaging WebViewer 21.1 is compatible with SAP GUI 7.7
Microsoft Edge chromium in place view.

4.2.3 Supported SAP GUI versions

For supported SAP server and SAP GUI versions, see the OpenText Archiving and Document Access for
SAP Solutions Release Notes.

4.2.4 Supported OpenText Content Server version

WebViewer CE 21.1 supports Content Server 16.0.x /16.2.x/ 20.x. As a prerequisite, the OpenText Imaging
Reviews and Notes 16.2.0 module must be installed on Content Server.
You can download the OpenText Imaging Reviews and Notes 16.2.0 module at
https://knowledge.opentext.com/knowledge/llisapi.dll/Properties/71831329 .

To view Content Server documents using WebViewer, the Content Server administrator needs to store the
credentials of WebViewer using the WebViewer Administration Console. For more information, see section
“Configuring Secure Parameters” in the WebViewer Installation Guide. The integration of WebViewer with
Content Server shares the authenticated session created between WebViewer and Content Server. To

OpenText Imaging WebViewer 21.1 Release Notes 10

establish a session, you must store the Content Server credentials (Host Name, Username, and Password)
in the WebViewer Administration Console. The credentials are used to open a session between WebViewer
and Content Server, but the impersonate call will follow to switch the context to the user that is viewing the
document. In case the Content Server administrator credentials are not stored in the WebViewer
Administration Console, the cookies mechanism can be used to share the session context.

OpenText Imaging WebViewer 21.1 Release Notes 11

4.2.5 Protocols and security
Communication protocol
WebViewer uses HTTP/ HTTPS protocol for communication with Archive Center and SAP GUI. OLE,
RFC, or HA protocols are not supported.
SSL (Secure Socket Layer) communication
SSL is not supported by SAP R/3 version 4.6.
4.2.6 Document formats
Depending on the file format of the open document, the following functions are available:
Microsoft Word, Excel
Rotating pages, displaying annotations, editing annotations, editing notes, changing character set in
notes, checking authenticity, and copying image data.

Note:

OpenText Imagenation libraries require the availability of X windows

binaries on RHEL to access the MS-Office documents. In non-Windows
systems, run createlinks_imscore_linux.sh.sh to generate the softlink files
for the .so version files IMSCORE_HOME and set the IMSCORE_HOME
path to libraries.

Plain text (ASCII)

Free search, rotating pages, forms overlay, displaying annotations, editing annotations, editing notes,
changing character set in notes, checking authenticity, copying text, and copying image data.
PDF
Free search, rotating pages, forms overlay, displaying annotations, editing annotations, editing notes,
changing character set in notes, checking authenticity, digital signature, hyperlinks, copying text, and
copying image data.

Note:

WebViewer cannot correctly display documents that are based on PDF format with
interactive technologies, such as Online Forms. WebViewer parses static PDF content only
and discards the interactive part of information.
OTF
Free search, rotating pages, forms overlay, displaying annotations, editing annotations, editing notes,
changing character set in notes, checking authenticity, copying text, and copying image data.
ALF
Free search, attribute search, rotating pages, forms overlay, displaying annotations, editing
annotations, editing notes, changing character set in notes, checking authenticity, hyperlinks, copying
text, and copying image data.
Compound Documents

Free search, rotating pages, forms overlay, displaying annotations, editing annotations, editing notes,
changing character set in notes, checking authenticity, digital signature, hyperlinks, copying text, and
copying image data

OpenText Imaging WebViewer 21.1 Release Notes 12

 Note:

• For single documents contained in compound documents, the same functions are available
as for the same format outside of compound documents.
Exception: Attribute search is not available for ALF documents contained in a compound
document.
• Free search and copying text are available only for plain text (ASCII), PDF, OTF, and
ALF documents inside a compound document.
• Digital signature is available only for PDF documents inside a compound document.
• Hyperlinks are available only for PDF and ALF documents inside a compound document.
• The printing functionality of WebViewer is achieved by rendering the document or choosing the
pages as PDF. The file is then downloaded to the client location and passed on to the PDF software
program present in the client location. This document can then be printed using the configured
printer. This functionality behaves differently depending on the combination of browser and PDF
software program used. OpenText strongly recommends testing your scenario carefully. The best
user experience is achieved with Internet Explorer 11 and Adobe Reader 11 or higher.
When displaying existing PDF format files from the archive, there is an option 'print as original' in
WebViewer, which avoids the additional rendering step. This enables good quality considering that the
whole document must be printed without any additional form and annotation features.
.

OpenText Imaging WebViewer 21.1 Release Notes 13

 TIFF/FAX
Rotating pages, forms overlay, displaying annotations, editing annotations, editing notes, changing character set in
notes, checking authenticity, and copying image data.
PNG/JPEG
Rotating pages, forms overlay, displaying annotations, editing annotations, editing notes, changing character set in
notes, checking authenticity, and copying image data.
GIF
Rotating pages, displaying annotations, editing annotations, editing notes, changing character set in notes, checking
authenticity, and copying image data.

4.3 OpenText product compatibility

The section provides details about which versions of other OpenText products are compatible with this release of
WebViewer CE 21.1.

Note: For the latest compatibility information for OpenText products, refer to the Compatibility Matrix
(https://knowledge.opentext.com/go/matrix) on OpenText Knowledge Center.

Product name Version Notes

16.0

Archive Center 16.2.0

20.2

Archiving and Document Access 16.0/20.4

Core Archive 20.2/20.4

Transactional Content Processing 16.1

16.0

Content Server 16.2.x

20.2/20.4

Imaging Reviews and Notes 16.2 Content Server module

4.4 Language support

OpenText Imaging WebViewer is currently localized in the following languages. Additional languages may be available
in future releases.

OpenText Imaging WebViewer 21.1 Release Notes 14

 Component Languages

EN DE JA FR ES RU ZH PT IT FI NL AR CA ZH_TW

Imaging B B B B B B B B B UI UI UI UI UI
WebViewer

Component Languages

KK SV UK KO DA PL TR NO

Imaging UI UI UI UI UI UI UI UI
WebViewer

UI = user interface only

B = both user interface and online help

5 Installation and upgrade notes

This section provides additional installation and upgrade information, including related or third-party product
information and any required critical patches.

5.1 Installation notes

Before you install WebViewer, review these additional installation notes and verify related product or third-party
product requirements.
Extracted Tomcat:

T for the
is

5.1.1 Prerequisites to install WebViewer in OpenJDK

The following prerequisites must be fulfilled by the client to install WebViewer in OpenJDK.

1. Install OpenJDK.
2. Configure JAVA_HOME to point to OpenJDK.
3. Install Tomcat.
4. During the Tomcat installation, ensure that the JDK version points to "folder/path/to/OpenJDK" because
OpenJDK installation does not create any registry key.

5.1.2 WebViewer Server on one workstation

The user must be logged in as an administrator or root to install the WebViewer base version and patches. Ensure
that all OpenText Imaging components are of the same version.
OpenJDK Installation

OpenJDK must be installed prior to starting the WebViewer installation. JDK installation is a prerequisite.

Important
OpenText Imaging WebViewer 21.1 Release Notes 15
 Installation fails when using JRE instead of JDK. The environment must contain JDK. JRE is not
sufficient.
Configuration to support Umlaut characters

If the document Title contains umlaut characters, such umlauts will not display properly. Setting connector
parameters in Apache Tomcat Server Configuration, for example, (URIEncoding="UTF-8" and
tomcatAuthentication="false”) will display the Title characters properly.
Memory settings

OpenText recommends the following memory setting for the Application Server 64-bit JVM options: Set
JAVA_OPTS=-Xms2g -Xmx2g -XX:GCTimeRatio=2 -XX:ParallelGCThreads=8 -XX:MaxGCPauseMillis=2000 -
XX:+DisableExplicitGC

OpenText recommends the following optimal settings for the garbage collector: Set JAVA_OPTS=-
XX:GCTimeRatio=2 -XX:ParallelGCThreads=8 -XX:MaxGCPauseMillis=2000 -XX:+DisableExplicitGC

Installation on UNIX Servers

To enable PDF document support, export LD_LIBRARY_PATH/SHLIB_PATH/LIBPATH to point to the Imaging PDF
resources directory. This environment variable is different for different platforms as mentioned in the table below.

Platform Library path variable

Linux LD_LIBRARY_PATH

The Imaging PDF resources directory is the folder where the binaries of the PDF Library and the Resource files
(CMap, Font, Unicode) are located, for example, /usr/local/lib/PDFL.
Setup for Imagenation libraries

OpenText Imaging WebViewer integrates internally another OpenText product called Imagenation for rendering the
Microsoft Office documents. Imagenation is active and licensed by default. The 16.2.12 version of Imagenation is
integrated with WebViewer CE 21.1.

Note: The Linux (Red Head) version of OpenText Imagenation 16.2.12 or higher depends on the Virtual
Frame Buffer (Xvfb) and on the Glib package. Ensure that you install these packages before running the
Office format conversion in WebViewer.

Note: Executing ‘verify_prerequisites.sh’ at IMAGENATION_HOME path will check for all prerequisites if
anything is missing from the environment.

Configuration to avoid information disclosure

Information leakage is an application weakness where an application reveals sensitive data, such as technical
details of the web application, environment, or user-specific data. Sensitive data may be used by an attacker to
exploit the target web application, its hosting network, or its users.
To avoid information leakage or disclosure using Tomcat, the configuration below is required.
1. Change oradd the value of "server.info" to "Apache Tomcat Version X" in
\catalina.jar\org\apache\catalina\util\ServerInfo.properties.
2. Replace the default error page (default is stacktrace) by adding the following into
CATALINA_HOME/conf/web.xml. within </web-app>
<error-page> <exception-type>java.lang.Throwable</exception-type>
<location>/error.jsp</location> </error-page>
OpenText Imaging WebViewer 21.1 Release Notes 16
5.2 Upgrade notes
The application does not provide an upgrade feature. A new installation will override the old version of the
application.
OpenText recommends saving the following files (if they exist) before the installation in the
<WebViewer>\WEB-INF folder:
• wevconfig
• cred
• csauth
To restore configuration of the 16.2.8/16.0.0 version:
1. Remove version 16.0.0/16.2.8.
2. Install WebViewer 21.1, and then start the application server (if the “Start Tomcat” option is
unchecked during installation).
3. Stop the application server.
4. Replace wevconfig, and the cred, csauth files with the corresponding files in the <tomcat-
5. home>/webapps/WebViewer/WEB-INF folder of WebViewer 21.1.
6. Start the application server, and then navigate to the WebViewer Administration Console, section
Configuration Parameters to check the configuration.

Important
When you upgrade WebViewer from a lower version and want to keep the configuration, you must back
up the configuration files wevconfig, menu.xml (UI/component/menubar/menu.xml), and toolbar.xml
(UI/component/toolbar/toolbar.xml), in case of changes to keyboard shortcut key mappings before installing
the new version. After the installation, set the configuration values according to the previous values of the
wevconfig file (steps described above) and replace menu.xml and toolbar.xml files with the corresponding
backup files.

In case of applying the patch, you need to back up only menu.xml and toolbar.xml (in case
of changes to keyboard shortcut key mappings) and replace menu.xml and toolbar.xml files
with the corresponding backup files.

Important
The upgrading binary should not contain any updates in the configuration files. Any additional
information section in the patch description will indicate any changes in the configuration files.

Hotfix Installation Instructions:

The current version of WebViewer must be uninstalled before installing 21.1 version, follow the below steps
1. OpenText recommends taking back-up of the following files (if exists):
<WebViewer>\WEB-INF\wevconfig
<WebViewer>\WEB-INF\cred
<WebViewer>\WEB-INF\csauth
<WebViewer>\UI\component\menubar\menu.xml
<WebViewer>\UI\component\toolbar\toolbar.xml
<TOMCAT_HOME>\bin\setenv.sh

2. Uninstallation of existing WebViewer

Stop Tomcat and delete the below files/folders
<TOMCAT_HOME>\webapps\WebViewer
OpenText Imaging WebViewer 21.1 Release Notes 17
 <TOMCAT_HOME>\webapps\WebViewer.war
PDF Libs, Office Libs and PDF Resources files

3. Install WebViewer 21.1 version

Execute the WebViewer-<version>-<platform>.sh (Refer section 3.1.3 of Installation and Configuration Guide -
https://knowledge.opentext.com/knowledge/piroot/clwebv/v210100/clwebv-igd/en/clwebv-igd-en.pdf )

4. Restoring the backup copied in Step 1

Stop Tomcat
Replace the files in respective directories except setenv.sh
For setenv.sh, Append/update catalina and java specific related settings as per the requirement (if required).

5. Applying hotfix
Extract the WebViewer.war from WebViewer.zip to <TOMCAT_HOME>/webapps folders
Start Tomcat

6 Patches
A patch is a piece of software that is designed to fix or improve a computer program or its supporting data. These may
include repairs to security vulnerabilities or resolution of bugs and may also improve usability or performance. The
following patches/hotfixes must be applied to OpenText Imaging WebViewer 21.1. OpenText recommends that you
check OpenText My Support (https://support.opentext.com) for any patches or documentation updates that may have
been posted after this release.

6.1 Hotfixes
6.1.1 Hotfix installation
Refer the ReadMe file shared along with each Hotfix for installation/deployment steps.

6.1.2 Available hotfixes

The following table lists and describes the hotfixes available for this release.

OpenText Imaging WebViewer 21.1 Release Notes 18

 Hotfix name Additional information Downloads

OTCS_4765170.tar You must download the

Fixes
following to install this hotfix
- Slight performance optimization in case
of heavy load on the application. OTCS_4765170.tar
- Introduced new parameter 'DisableForm'
to give an option to disable form overlay
hence improving performance.
- Display sec key expiration UI message in
case the document signature gets expired.
- Improved logging mechanism
- Heart Beat Monitor to know the status of
pdf renderer (OK/Fail)

Refer section 8.2.2 of Installation and

Configuration Guide for more details of
Heartbeat monitor

Jira Reference: DOCVW-9135

OTCS_4903512.zip OTCS_4903512.zip
When PDF documents with digital
signatures are accessed using
WebViewer, a red X mark shown at the
place of digital signature
WebViewer reports “XML configuration is
malformed” error for some signed PDF
documents
Jira Reference: DOCVW-9813

6.1.3 Updates

7 Fixed issues
This section provides information about past issues that have been fixed in this release.

OpenText Imaging WebViewer 21.1 Release Notes 19

 Issue number Issue description

DOCVW-8529 Problem with document preview in iFrame in Chrome.

The following solution is provided:

1. Deploy WebViewer in Tomcat 9.0.38 or above.
2. Ensure that Tomcat is running in HTTPS mode only.
3. After deploying WebViewer, shut down the Tomcat server.
4. Navigate to the following folder:
${TOMCAT_HOME}/webapps/WebViewer/META-INF
5. Edit context.xml and append the following line before '</Context>':
<CookieProcessor sameSiteCookies="none"
className="org.apache.tomcat.util.http.Rfc6265CookieProcessor"/>
6. Navigate to the following folder:
${TOMCAT_HOME}/conf
7. Edit web.xml and search for the '<session-config>' element and
modify as follows:
<session-config>
<session-timeout>30</session-timeout>
<cookie-config>
<http-only>true</http-only>
<secure>true</secure>
</cookie-config>
</session-config>
8. Start Tomcat.
9. In the iframe code, ensure that the WebViewer URL points to the
HTTPS URL.

DOCVW-8788 PDF Display Issue

OTCS Ticket 4645629 - WEV 20.3 PDF display problems

DOCVW-8284 OTCS Ticket 4368704 SAP Ticket : OpenText Web viewer not working
correctly for doc and zip mimetype.Enabled WebViewer to download
application/doc and application/zip to client system

DOCVW-8253 OTCS Ticket 4505456 - menu.xml was not working was expected

DOCVW-8150 OTCS Ticket 4465043 WebViewer 16.2.8 - Unable to add notes

Introduced new config parameter 'XHRFormSubmission' for
XMLHttpRequest for forms.

XHRFormSubmission
Description: Enables or disables the submission of forms using
XMLHttpRequest. To enable XMLHttpRequest for forms, set to
TRUE. Default is FALSE.

OpenText Imaging WebViewer 21.1 Release Notes 20

8 Known issues
The following known issues exist in this release.

Issue name Issue description

Document display is gray in When document is opened in inplace view, it is showed in

inplace view gray color.
To solve this, configure vu_max_on_load=false

Specific Microsoft Office When JVM heap size is not enough, either Apache Tomcat
documents conversion failed crashes or blank pages are rendered.
due to JVM heap size. Increasing the JVM heap size resolves the issue.

SSL and the Send by E-mail If you use SSL and the “Send by E-mail” feature, WebViewer
feature lets Apache Tomcat act as an HTTP server and an HTTP client
at the same time. The client checks the certificate sent by the
server by trying to find this certificate (or a superior one) in the
truststore. The problem is that Apache Tomcat, when acting as
an SSL server, uses a certificate that is not known to the Java
Virtual Machine (JVM).

To solve the problem, you must mark the certificate of the

Apache Tomcat known to the JVM as trustworthy. There are
two ways of doing this:
• You can import the certificate into the default
truststore of the JVM using the Java tool keytool.
For more information on keytool, see
http://java.sun.com/javase/6/docs/technotes/tools/
windows/keytool.html.
• You can specify the truststore in the Apache Tomcat
start script. This method has the advantage
that you do not touch the default truststore of the
JVM, which might be used by other applications.

To import the certificate into 1. In a command prompt window, go to <JDK root>\bin.

the default truststore of the 2. Run the following command:
JVM
keytool -import -alias <keystore entry name> -
keystore <JDK root>\jre\lib\security\cacerts
-trustcacerts -file<path of the certificate file> - storepass
<password>

To specify the truststore in

1. Create a truststore file that is a keystore,
the Tomcat start script
for example on basis of the <JDK
root>\jre\lib\- security\cacerts file.
2. Add the following line to the Apache Tomcat
start script <tomcat root>\bin\catalina.bat:

3. set JAVA_OPTS=-
Djavax.net.ssl.trustStore=<path of the truststore file>
4. Alternatively, you can set JAVA_OPTS in the
environment appropriately.

Reference: DOCVW-814

OpenText Imaging WebViewer 21.1 Release Notes 21

 Issue name Issue description

Keyboard shortcuts In some browsers, especially in Moziilla Firefox, some

triggering browser actions WebViewer's keyboard shortcuts may trigger browser actions
instead of the expected WebViewer actions. To change this
behavior, configure different keys for the affected shortcuts in
the menu.xml file. See section “Customizing command menu
and keyboard shortcuts" in the Installation and Configuration
Guide.

History of documents does For each document called from SAP R/3, WebViewer starts a
not work for documents from new browser session. Therefore, the history of documents
SAP R/3 feature does not work for documents from SAP R/3.

Reference: DOCVW-922

Behavior if document format If WebViewer is called to show a document of

is not supported unsupported format, for example, PowerPoint, the
browser is redirected to load the document. The
result of this action depends on the browser´s
capabilities and its installed plug-ins. For example,
the browser might offer the user a dialog with the
options Open, Save, and Cancel even if the browser
can render the document; that is, a corresponding
plug-in is installed.
There are different techniques to load a document in the
browser. Under certain circumstances, it may be necessary
to use a different technique than the one used by default. In
this case, the <Tomcat
home>/webapps/WebViewer/UI/main.jsp file must be
customized. For more information, see the comments in this
file.

Reference: DOCVW-452

Partial support of Remote WebViewer supports Remote Standby Server only partially.
Standby Server The following limitations apply:
• If the original server was once available when the
WebViewer server ran, WebViewer can use
Remote Standby Servers.
• If the original server is not running when the
WebViewer server is started, no Remote
Standby Server is contacted, and the
configuration entries are ignored.
Reference: DOCVW-794

Host names must not Host names must not contain an underscore. For example,
contain an underscore “host_name” is not allowed. The Apache HTTP library does not
allow underscores in host names because this violates some
RFC concerning URLs.

Reference: DOCVW-784
Incorrect total number of In OTF and ALF documents, the WebViewer search finds hits
search hits in OTF and ALF in control commands that are not displayed. Thus, the total
documents number of search hits might be higher than the actual
highlighted hits in the document.

Reference: DOCVW-756
OpenText Imaging WebViewer 21.1 Release Notes 22
 Issue name Issue description

Text documents with Lines in text documents with the prescribed page size can be cut
prescribed page size off at some scaling factors. Since fonts are usually not
continuously scalable, the character width of a scaled font may
not match the overall scale factor. If a page size is prescribed
(FORM.INFO), the scaled page size may be too small for the
text at some scale factors, for example 150%.

Reference: DOCVW-683

Saving annotations Sometimes, annotations cannot be saved to the repository

and the message “Post too large” is displayed. To solve the
problem, increase the maximum post size of Apache Tomcat:
In the conf directory of the Apache Tomcat installation, open
the server.xml file with an editor. Search for <Connector
port="8080", and then enter a new value for the maxPostSize
parameter.

Reference: DOCVW-411
Example:
<Connector port="8080" maxPostSize="10485760"
maxHttpHeaderSize="8192" maxThreads="150"
minSpareThreads="25" maxSpareThreads="75"
enableLookups="false" redirectPort="8443" acceptCount="100"
connectionTimeout="20000" disableUploadTimeout="true" />

Maximum lines per page is Using very long lines (number of characters greater than 1000)
not respected when creating with line wrapping in ASCII documents might lead to an
the ASCII page list incomplete display of characters.

Reference: 43156

Documents with fonts other To correctly render documents that cannot be displayed with
than “extended-Latin” “extended-Latin” fonts (for example Chinese, Japanese), the
Java font.properties files must be configured. For example,
specify a Unicode font for all non-European languages.

Reference: DOCVW-278

Printing notes with Unicode If you want to print notes with Unicode characters, you must
characters configure the viewer accordingly through the administrator
console. For more information, see section "Printing" in the
Installation and Configuration Guide.
Reference: DOCVW-278

Annotations outside of If annotations created with Windows Viewer stretch beyond the
document's limit original document's limits, the part outside is not shown by
WebViewer.

Reference: DOCVW-109

OpenText Imaging WebViewer 21.1 Release Notes 23

 Issue name Issue description

Misalignment of text when When zooming a document, images and text may show slight
zooming misalignments.

Reference: DOCVW-412

Usage of BACKSPACE Especially with Firefox, pressing the BACKSPACE key or

clicking the browser's Back button may lead to unwanted
effects (disappearing dialog box panel without resizing of
the document). Users should always use the Hide button.

Reference: DOCVW-585

Rotation of checkmarks Checkmarks that were rotated using Windows Viewer do not
appear rotated in WebViewer. Hence, they are also saved
without rotation.

Reference: DOCVW-606

Exact content of text is not For certain text documents (except PDF), selecting and
copied copying text might not copy the exact portion of the selected
text. OpenText recommends selecting a bigger chunk of text
or using the select page option.

Reference: DOCVW-2030

Screen flickers in Firefox When using Mozilla Firefox and compound documents, screen
when working with flickering can occur when the “Send by Email” dialog box is
compound documents open and the selection is changed in the documents pane.
Flickering also occurs when in the Edit Annotations mode and
selection is changed in the documents pane.
Reference: DOCVW-2153

Text overlaid on an image in Text portions that are overlaid on an image in a PDF document
a PDF document cannot be cannot be copied.
copied
Reference: DOCVW-1977

Unlocking locked Documents that remain locked due to a session timeout or in the
event of an unresponsive server will be unlocked based on the
documents in case of
duration set by the parameter DS_LOCK_MAX_TIME of Archive
session timeouts or Center configuration parameters. This entry states the number of
unresponsive server minutes after which a document lock becomes invalid. After this
period has expired, it is assumed that the program that set the
lock has become unresponsive or terminated without releasing
the lock. The default value for this entry is 900 minutes.
Alternatively, you can use the following URL, which can be
typed into any browser to do a forced unlock:

http://<server>:<port>;/archive?unlock&pVersion=0046&contRe
p=<contRep>&docId=<docid>force=yes

The above URL works only in scenarios where the archive is

not configured for seckey authentication.
Reference: DOCVW-2581

OpenText Imaging WebViewer 21.1 Release Notes 24

 Issue name Issue description

PDF additional fonts If a document does not embed the required fonts or have it in
the PDF resource, the user can create a symbolic link for the
required fonts from where those are available.

Browser window resize Minimal width of the browser window that WebViewer supports
to show footer bar icons is 450px. Beyond the limit,
pagination icons may not show properly.

Document printing is not Document printing is not supported in Internet Explorer 64-
supported in Internet bit version due to the Adobe Reader X restriction.
Explorer 64-bit
Reference: http://answers.microsoft.com/en- us/ie/forum/ie9-
windows_7/ie9-and-adobe-reader-x- compatibility/2a710fe9-
c065-e011-8dfc-68b599b31bf5

Toolbar configuration If any item is removed from toolbar.xml, the corresponding

configuration values do not work.

Save as Original Format If a document has multiple main components, save as original
format is not available.

Apache Tomcat selection In the Apache Tomcat selection wizard, the Add button is
during installation enabled by default. Select the listed Apache Tomcat instance,
and then click Add.

Content Server usability When opening a document in Content Server using

“View Document” link, browsers must enable the
pop-up blocker to open the documents in a new
window.
Note: The Chrome browser will open the document in the
current window only.

Password Protected PDF The WebViewer application cannot show password- protected
documents PDF documents.

Encrypted PDF documents The Adobe’s PDF library allows encrypting the content in the
recent versions. This version of WebViewer cannot display
encrypted documents.

PDF server process manual If the application server is not shut down or becomes
shutdown required if the unresponsive, then sometimes, the Java process created for
Application Server becomes PDF rendering will not be shut down. This will cause PDF
cache issues. If any PDF cache issue occurs, ensure that the
unresponsive or does not
Java process is aborted (manually) and restart the
shut down properly. application server.

Mouse-click events delayed When users draw an annotation, they must wait for some time
while drawing annotations after drawing the first annotation and then draw the next
annotation. This limitation is due to clicking the mouse while
moving the cursor, that is the mouse-click event is delayed.

OpenText Imaging WebViewer 21.1 Release Notes 25

 Issue name Issue description

OLE annotations are not OLE annotations can be created in Windows Viewer. However,
supported in WebViewer when viewed in WebViewer, these OLE annotations are not
displayed because WebViewer does not support OLE
annotations.

Annotations may fail due to Adding or editing annotations may fail if the browser’s back or
back or forward browser forward button is clicked in annotation mode because these
actions in annotation mode. actions leave the user interface in an inconsistent state.

Reference: DOCVW-6040

Problem with Adobe Reader An error message appears when trying to print a document,
when a document is printed stating that there is a problem with Adobe Acrobat Reader. This
issue occurs because of Adobe Acrobat Reader version
#2018.011.20040. To resolve the issue, configure Adobe
Acrobat Reader as follows:
1. Navigate to Edit > Preferences > Security (Enhanced)
and clear the Enable Protected Mode at startup check
box.
2. Run a repair and check if the issue is resolved by
performing the following steps.
a. Go to Control Panel > Programs > Programs and
Features.
b. Select Adobe Acrobat Reader > Change > Repair.
3. Start the application.

Reference: DOCVW-7080

Favicon is not displayed When menu items are selected in the Edge browser, the
when menu items are special character '#' is attached to the end of the URL. Due to
this action, the favicon is replaced with the Tomcat favicon.
selected in the Edge
browser
Reference: DOCVW-6991

Action required when saving When a user attempts to save or email a document, sometimes
or emailing a document fails the action is not completed because of backend errors. As a
result, the following issues could be observed:
• When saving the document, the user receives a
corrupted document.
• When emailing the document, the user receives a
corrupted attachment.
• A 404 error can be displayed.
For a workaround, in the first two scenarios, if the user
receives a corrupted file, the save or email operation must be
attempted again.

Reference: DOCVW-6955

PDF fails to open When the rendering fails for a PDF document, it will be
exceptions downloaded to the client.

OpenText Imaging WebViewer 21.1 Release Notes 26

 Issue name Issue description

Japanese characters are not For certain Archive Link Format documents with East Asian
displayed in printed (Japanese) characters, the printed output is appearing as blank.
To view the output, the administrator needs to configure
documents
vu_MaxCharsPerLine to a smaller number, such as 200.

Reference: DOCVW-7114

Archive Link Format (ALF) Rendering of some specific documents that include East Asian
performance is slow characters will take more time when JDK 11 is used. For more
details, refer to https://bugs.openjdk.java.net/browse/JDK-
8179209.

Reference: DOCVW-7174

Wait until existing operation An interruption might occur if a new operation is started by a user
while an existing operation, such as printing, saving, or sending
is finished
email is in progress. Therefore, you must wait until the current
operation is finished before starting a new operation.

Reference: DOCVW-7087

Watermark not displayed Watermark does not appear on the print output for a document
when Black and White print when the Black and White output option is selected in the Print
dialog box.
output is selected
Reference: DOCVW-7106

Error message appears When a user clicks the “Add Notes” button the second time in
when users click the "Add succession, the “Notes cannot be added since the document is
locked by another user” error message appears.
Notes" button multiple times
Reference: DOCVW-7181

Stamps.xml Backslash ("\") is a forbidden character to configure for stamps.

Browser sessions isolation When WebViewer is deployed as multiple Apache Tomcat

instances on the same host, browser sessions need to be
isolated when accessing the administration console of
individual instances.
Reference: DOCVW-6863

Adding annotations When a user tries to add multiple annotations too briskly, some
of the annotations might not be saved. Users are advised to
take an interval of at least 1 (one) second between adding two
annotations.

Reference: DOCVW-6860

Interrupting Print or Save Print/Save operation shall be interrupted or fails if any other
actions are performed during the course.

Reference: DOCVW-6977

No support in Content Documents uploaded to Content Server with a n Advanced

Server for Advanced Version are not possible to be viewed from WebViewer.
Version Control documents Reference: DOCVW-7438

OpenText Imaging WebViewer 21.1 Release Notes 27

 Issue name Issue description

OpenJDK11 Resource An illegal reflective access operation has occurred (Warning

Extractor Issue message is traced in logs) when WebViewer is deployed on
OpenJDK 11. This issue is due to groovy and a fix needs to be
given in the OpenJDK package. Users can ignore this warning.

Reference: DOCVW-7279 KB12501297

Select Page Clipboard Page selected using the “Select Page” option cannot be copied
Functionality because Java Applet is deprecated in all the browsers.

Reference: DOCVW-7373

AutoSave Auto save refreshes any unsaved user behavior, such as the
selection of annotation using the annotation summary panel.
Reference: DOCVW-8086

Current user annotations are displayed even when the user is

not selected to display the annotation.
Reference: DOCVW-8221

AutoSaveOnClose • Autosaveonclose parameter will not have an effect on

configuration parameter the Google Chrome browser 80+ version.
browser limitation
Reference: DOCVW-8114

• AutoSave doesn’t work on edge chromium browser

Reference: DOCVW-8835

Checkmark annotation PDF-size of the check mark annotation is different in the “edit
annotation” mode from the “toggle annotation” mode.

Reference: DOCVW-8199

Hyperlinks WebViewer cannot detect Text type URL's if the PDF document
has the combination of text type and hyperlink type URLs.

Annotation- Cover Sheet Addition annotation on the compound document coversheet is

not working.

Printing and Saving Large Using Print and Save functionality, the user should be advised to
Documents limit the maximum number of pages to print to 100 pages.
If the user wants to print and save the complete document, "Save
As Original Format" can be used.

Reference: DOCVW-7097

OpenText Imaging WebViewer 21.1 Release Notes 28

 Issue name Issue description

Limitation for bulk

documents (Parallel) open Opening bulk documents at a time (Parallel requests) from
support leading application is not supported. This is due to browsers
behavior of cookie-based session sharing across tabs and
windows. Opening bulk documents causes parallel requests from
browser and from server-side different sessions will be created as
those are individual requests but when response is sent back,
browser overwrites previous sessions with last rendered response
session, as browser allows only one cookie-based session for the
same domain. This results session conflicts with Web Viewer and
some documents fail to render.”vu_AllowSessionSharing”
parameter doesn’t work in such scenario.

Reference: DOCVW-9261

Work around
Suggest opening one document at a time.

Localization There are few strings in WebViewer which are not localized in all
the languages either due to technical complexity or the strings are
used as images in the application. All non-localized strings will be
displayed in English to the user. Below mentioned epic includes
all such issues and also other localization issues which will be
catered in upcoming versions.
Reference: DOCVW-9174

Localization The alert message shown when save/print/send email actions are
triggered for a huge range document (range can be configured) is
not shown when Catalan language is applied.
Reference: DOCVW-9404

PDF Documents with digital WebViewer CE 21 has Datalogics v18.0.3 which does not support
signature having digital signatures having ETSI.CAdES.detached certificates.
ETSI.CAdES.detached When such signatures are accessed, WebViewer shows a
certificates message saying Document may have corrupted signatures, may
have invalid certificates.
Reference: DOCVW-9380

PDF Documents with digital The Datalogics version used in WebViewer v21.1 doesn’t support
signatures not loading certain type of signatures, and WebViewer is not rendering the
document.
Reference: DOVW-9268, DOCVW-9373, KB17857377
Note – An hotfix is provided for v21.4 with Datalogics which can
exclude the unsupported certificates and load the document.

OpenText Imaging WebViewer 21.1 Release Notes 29

 Issue name Issue description

Image is not getting When a document is opened from SAP Fiori in the Embedded
displayed with WebViewer mode then the document is not getting opened. This is because
with the integrated VIM Fiori of the security update both Chrome and Chromium have
Apps received. Firefox is soon to get these security updates.
Due to security updates for Browsers like Chrome and Chromium
Third-Party cookies are blocked due to changes in SameSite
settings in the response header. Due to this change By default
SameSite=LAX is being set due to which third-party cookies are
being blocked.
The same is in this case wherein WebViewer JSESSIONID is
blocked as SameSite is not set to NONE.
TO avoid this it is mandatory that:
1) SSL needs to be configured to the tomcat.
2) When SSL is enabled then the Secure attribute should also be
enabled. (Automatically enabled now for HTTPS).
3) If the above two steps are done then we need to set
SameSite=NONE.
If all the above steps are met then SameSite is set to NONE. This
will fix the issues caused in iframes or in the Embedded view.
So, To configure these steps we need a Tomcat configured to
SSL and add these changes into the context.xml files inside
WebViewer\META-INF\context.xml.
Changes in the xml file: <CookieProcessor
className="org.apache.tomcat.util.http.LegacyCookieProcessor"
sameSiteCookies="None" />
Note: In Tomcat < 9.0.28 (or < 8.5.48 for the 8.5x branch), the
same-site attribute is not set if the value is NONE.
Reference: DOCVW-9867

Special characters given in To eliminate Cross-Site Scripting vulnerability in Configuration

some configuration parameters page, all the special characters are encoded and
parameters (like displayed in the parameters fields. They are rendered correctly in
vu_WatermarkText, the documents.
vu_email_from, help_tenant, Some special characters like @ are also getting encoded in
Help_URL_Root, etc.) are vu_email_from field and shown. But the Send email functionality
getting encoded after works as expected.
coming out of that filed,
rendered correctly on the
Reference: DOCVW-10430, DOCVW-10429
document.

OpenText Imaging WebViewer 21.1 Release Notes 30

9 Contact information
OpenText Corporation
275 Frank Tompa Drive
Waterloo, Ontario
Canada, N2L 0A1

OpenText My Support: https://support.opentext.com

For more information, visit www.opentext.com

Copyright © 2021 Open Text. All Rights Reserved.

Trademarks owned by Open Text. One or more patents may cover this product. For more information, please visit https://www.opentext.com/patents.
Disclaimer
No Warranties and Limitation of Liability
Every effort has been made to ensure the accuracy of the features and techniques presented in this publication. However, Open Text Corporation and its affiliates accept
no responsibility and offer no warranty whether expressed or implied, for the accuracy of this publication.

31