Opentext Release Notes: ™ Content Suite Platform
Opentext Release Notes: ™ Content Suite Platform
Opentext Release Notes: ™ Content Suite Platform
Release Notes
CE 22.1
1 Introduction .................................................................................................................................... 4
1.1 Release Notes revision history .................................................................................................. 4
9 Documentation Errata.................................................................................................................. 38
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.
Off cloud
OpenText Content Suite Platform – with a perpetual license model, deployed in a customer or
partner data center, managed by customers, partners or OpenText Professional Services.
Public cloud
OpenText Content Suite Platform – with a perpetual license model, deployed on a hyperscaler
cloud infrastructure, and managed by customers, partners, or OpenText Professional Services.
Managed services
OpenText Content Suite Platform Cloud – A single tenant Software-as-a-Service (SaaS) offering
with subscription pricing and a single SLA covering application and infrastructure, deployed and
managed by OpenText.
For OpenText Enterprise Information Management (EIM) offerings, and a broad range of OpenText
products that extend Content Services to business processes, including:
o OpenText Extended ECM Platform
o OpenText Extended ECM for SAP® Solutions
o OpenText Extended ECM for SAP® SuccessFactors
o OpenText Extended ECM for Salesforce®
o OpenText Extended ECM for Microsoft® Office® 365
o OpenText Extended ECM for Oracle® E-Business Suite
o OpenText Extended ECM for Engineering
o OpenText Extended ECM for Government
o OpenText Extended ECM for AppWorks
o OpenText Office Online Broker
Important: The change in the numbering scheme from 16.2.x, 20+ to 21.X does NOT indicate an
elevated level of change, risk, or complexity for applying an update. Content Server follows a
Continuous Improvement delivery model, and each update represents a few months of improvement.
The release number is determined by marketing objectives and does not indicate any technology
changes.
Content
Scheduled Date 16.2+
Suite
2018 March 16.2.4 16 EP4
2018 June 16.2.5 16 EP4
2018 September 16.2.6 16 EP5
2018 December 16.2.7 16 EP5
2019 March 16.2.8 16 EP6
2019 June 16.2.9 16 EP6
2019 September 16.2.10 16 EP7
2019 December 16.2.11 16 EP7
2020 April 20.2 CE 20.2
2020 July 20.3 CE 20.3
2020 October 20.4 CE 20.4
2021 January 21.1 CE 21.1
2021 April 21.2 CE 21.2
2021 July 21.3 CE 21.3
2021 October 21.4 CE 21.4
2022 January 22.1 CE 22.1
Important
Content Server Security Fixes, Fixes of Note and New Features can be
reviewed in the Content Server Documentation in OpenText My Support.
For more information, please see “Basic keyword search” section in OpenText Content Server - Smart
View User Help: Search
For more information, see “Versions page” under "Item properties and metadata" section in OpenText
Content Server - Smart View User Help: Get Started
For more information please see, View Insights messages in the Notification Center.
Refer to the manual to learn how to set up DocuSign integration in Content Server
Existing DocuSign customers with already running integrations updating to Content Server 22.1 are
required to adjust their configuration in Content Server. Refer to the “Upgrade notes” section in this
document for further details.
General Administration
Business administrator has been granted the permission to purge items in Recycle Bin by default.
Additional MSSQL information is added to the system report for advanced diagnostics and
troubleshooting purposes.
Search
Search performance is improved when searching on a low-memory metadata region with a right-
truncation or left-truncation search phrase of two or more terms.
Turn on AND queries performance optimization by default. In 21.4 we introduced a new setting to
improve the performance when search queries contain several AND operators and the setting was off
by default.
In Classic and Smart View a user will require modify permissions on Hold Management / Maintenance
and modify permissions on the Hold Groups in order to move Holds in and out of groups.
• A new ellipsis icon that shows a ‘Chart options’ tool tip to replace the Configure icon.
• For single-width pie charts radial labels replace the previous legend.
• A new SETATTR argument to the WFACTION sub-tag to support setting attribute values for
any workflow instance from a standalone WebReport.
LL_REPTAG_<subworkid> WFACTION:SETATTR:<attribute name>:<value>
• A new Manage Secure Constants Administration page helps improve security by managing
the Secure Constants, for example passwords, used in WebReport applications. You can use
this page to specify an optional allow list of WebReports that can use each Constant. You can
reference each Constant using the RESTCLIENT tag. For more information see Manage
Secure Constants in the WebReports Administration Help.
OpenText Viewing
Complimentary Basic Annotation: Annotations are now included as part of the complimentary
viewing experience for OpenText Viewing users. This offering allows for viewing and application of
annotations only. Printing or publishing documents with the annotation content applied requires a user
to have an Intelligent Viewing for Content Suite premium license seat.
• Include External Reference Files when Viewing CAD Content: Users will now have
associated external reference files (xref) included when viewing a supported CAD document.
The association of xref files to parent files is handled by the Extended Engineering module.
• In-Viewer Compare Mode Toggle: When users launch a compare session with Intelligent
Viewing for Content Suite it will open by default with either “Graphical Compare” or “Text
Compare” depending on what format types are being compared. The default compare mode
is configured using the administration settings. Users will now be able to easily change to the
desired compare mode on-demand from within the viewer with a new button.
• The Business Workspaces tool 'Import Configuration' to import configuration for workspace
types, unique names, and business object types with an XML file is deprecated beginning
with CE 21.4. As alternative, please use the Transport Warehouse.
• Imaging Review and Notes has been deprecated as of CE 21.3. It should not be used for any
new deployments while it continues to be supported for existing deployments.
• Enterprise Library including Enterprise Library CMIS is deprecated.
• Enterprise Library Data Sources are deprecated. They should not be used for new
installations and existing usage should be converted to Enterprise Data Sources. There are
search features that do not work with Enterprise Library Data Sources and search queries are
generally slower when Enterprise Library Data Sources are configured. The feature will be
discontinued in a future update.
• Binders and Cases object types have been replaced by Business Workspaces and are no
longer recommended for new implementation since 2017 (release 16.2.0). OpenText is
planning to discontinue Binders and Cases in the fourth quarter of 2022 (release CE 22.4).
Customers need to convert existing Binders and Cases into Business Workspaces using the
migration utilities available with Content Suite.
• jQuery update: Starting with 21.1, only the jQuery 3 plug-in is available.
• Owner ID: The Owner ID setting on the Security Settings page is deprecated as of CE 20.4.
• Windows Server: Windows 2012r2 is not recommended. Windows 2012r2 support is
expected to be deprecated sometime in 2021.
• My Mailbox: The My Mailbox feature has been added to the list of deprecated features. The
feature can be enabled however it will be removed from Content Server in the near future.
The following features have been discontinued and are no longer available:
Note
Certain use cases accessible from Enterprise Connect and Office Editor
22.1 still require Internet Explorer 11.
Content Suite Platform offers freely definable data containers called Business Workspaces. A
Business Workspace is a type of folder to manage content. Content could be, for example, Word,
Excel, or PDF documents. Business Workspaces are enriched with context-related metadata and
relations.
Users in Content Suite Platform have a user profile with personal data like name, communication
data, or personal data.
Software solutions like Content Suite Platform can neither be considered as GDPR compliant nor
GDPR non-compliant. Every customer using Content Suite Platform is responsible for ensuring GDPR
compliance in their organization.
Content Suite Platform provides different means to help organizations be GDPR compliant:
Note
Some components such as OpenText™ Object Importer, WebReports,
WebReports Extensions for Workflow, Email Cloud Archiving, CMIS
Document Pipeline for Archive Center, Document Pipeline for File
Archiving, OpenText™ Document Pipeline for SAP® Solutions,
DocumentPipeline for DocuLink, Add-on for Microsoft™ Office Online,
Content Sharing module, and Interview module are included in the
downloads but are licensed separately.
System Center: Provides capabilities to install solutions and automate the deployment process using
the Execution Plans feature. System Center is an all-in-one solution where you can find information
about products, download, install, or automate the deployment process and maintain the application,
and apply patches and updates. System Center is available for download.
Docker Images: Content Suite Platform Docker images that are packaged with this release should be
deployed using the Kubernetes engine. The Docker images are available for download at OpenText
My Support (Content Suite Platform Download area).
For detailed information about individual components of Content Suite Platform, please have a look at
the respective release notes.
1. Installation Overview
2. Documentation List – a single web page with links to documentation on the components in
the Content Suite Platform
Caution
Operating systems, databases, browsers, and other platforms
advance on independent schedules. OpenText identifies the
version tested where applicable and if a version is not identified,
testing is typically performed on the platform software available
approximately one month before the release date of Content
Server.
iPad or iPad Mini capable iOS, latest Safari, latest Only supported with Content
of running the latest iOS version version Server Smart View which is
version tested with the latest iOS
version. If you run into a
problem that exists only in a
previous iOS version please
upgrade to the latest version.
Edit / Open using • Firefox ESR / Quantum Requires Office Editor 16.x.x to
Office Editor • Google Chrome be installed on the desktop
• Microsoft Edge
• IE11
• Microsoft Chromium Edge Requires Office Editor 20.2 to be
installed on the desktop
Tomcat 8.5.73 OpenJDK 11.0.12 Validated with Tomcat 8.5.73 and earlier.
Tomcat 9.0.55 Validated with Tomcat 9.0.55 and earlier.
Apache HTTP Server 2.4.x Validated with 2.4.29 and earlier on Windows.
Note
Please review the specific support notes in the sections immediately
following this chart.
Azure SQL †
Red Hat 7.4 - 7.54 Oracle 12c 12.2.0.1 Linux 7.5 support
added with 16.2.6
Oracle Linux 7.4 - 7.5 3,4
Oracle 12.2
support added
with 16.2.4
Red Hat Linux 7.4 – 7.54 HANA 2.0 SPS 05 † Hana 2.0 support
added with 16.2.7
Linux 7.6 support
added with 16.2.8
Red Hat Linux 7.6-7.94 Oracle 12c 12.2.0.1 Linux 7.8 support
added with 20.4
Oracle Linux 7.6-7.93,4 Oracle 19c 19.x
Oracle 19.x added
PostgreSQL 11.14
with 16.2.10
PostGreSQL
added with 20.4
Linux 7.9 support
added with 21.2
1
Windows 2012 R2 support includes Standard, Datacenter, and Hyper-V.
2
Standard and Datacenter.
3
Covers both Unbreakable Enterprise Kernel (UEK) and Red Hat compatible Kernel.
4
Linux is supported on x86_64 architecture.
Note
S3 standard is the recommended storage class for AWS, whereas S3 Glacier is not
supported.
Content Suite Platform can leverage multiple storage platforms, including cloud object storages like
AWS S3. For details, see the Archive Center Storage Platforms documentation at
https://knowledge.opentext.com/knowledge/llisapi.dll/Open/77670019.
Databases are supported on any Operating System platform supported by the database vendor. It is
not required that the database be on the same platform as Content Server. Databases that have a
client component must have that client supported on an operating system supported by Content
Server.
Please ensure that you follow the recommended practices for Database installation and configuration
as indicated in the Best Practices documents on My Support.
• Compatibility Mode. Due to the known issue CSARC-861 you must set the compatibility
level to SQL 2012 (110).
• Adding and Connecting to an Azure SQL DB. You must create the Content Server
database in Azure SQL and then use Content Server to create the tables. Please refer to the
Content Server Installation Guide for additional details.
• Database Maintenance. If your Content Server database is a SQL Server database
deployed on Microsoft Azure, you cannot use any of the tasks on the Microsoft SQL Server
Maintenance page. Use other tools (for example, SQL Server Management Studio) to
perform these tasks.
• Oracle support includes Standard, Enterprise, and RAC as well as deployment on Oracle
Exadata Database Machine, Oracle DataGuard, and Oracle SuperCluster.
• Oracle Multitenant. The Oracle Multitenant option for Oracle Database 12c allows a
multitenant container database to hold pluggable databases. To use the pluggable database
from Content Server you must reference the pluggable database in your TNSNAMES file and
you must connect to the pluggable database from Content Server.
• Content Server Oracle support includes Oracle Client and Server interoperability support as
certified by Oracle where the minimum supported Database version for Content Server is
11.2.0.4.
4.8.2.7 Oracle 19c
• Oracle support includes Standard, Enterprise, and RAC as well as deployment on Oracle
Exadata Database Machine, Oracle DataGuard, and Oracle SuperCluster as supported by
Oracle.
• Content Server Oracle support includes Oracle Client and Server interoperability support as
certified by Oracle.
Azure PostgreSQL 11
SQL Server
versions as
Azure SQL
listed in section
5.8
Microsoft Azure, Google Cloud, and AWS are supported virtualization environments †.
Note that Content Suite is a resource intensive application and will require at least the same amount
of resources in a virtual environment as it would in a physical environment. Therefore, additional
resource scaling may be required to maintain the same level of performance in a virtual environment
as observed in physical environment. Static or committed resources within a Virtual Environment are
typically needed for performance-sensitive scenarios.
4.10 Kubernetes
Content Suite is available as Docker Containers to be deployed in Kubernetes, a container-
orchestration system.
Important
Customers deploying Content Suite containers provided by
OpenText are expected to stay relatively current with updates,
following best practices for cloud technology and continuous
deployment. Patched containers with fixes will be provided until
September 2022.
Office 95 Word, Microsoft Project, and Excel Only text indexing and hit highlighting
95 are supported with Microsoft Project.
Office 97 Word, Excel, Microsoft Project, and Only text indexing and hit highlighting
PowerPoint 97 are supported with Microsoft Project.
Office 2000 Word, Excel, Microsoft Project, and Only text indexing and hit highlighting
PowerPoint 2000 are supported with Microsoft Project.
Office 2003 Word, Excel, Microsoft Project, and Only text indexing and hit highlighting
PowerPoint 2003 are supported with Microsoft Project.
Office 2007 Word, Excel, Microsoft Project, and Only text indexing and hit highlighting
PowerPoint 2007 are supported with Microsoft Project.
MIME type extraction is supported for all file types except CDR.
On Linux and Solaris operating systems, only Western languages are supported for View as Web
Page and Thumbnails.
For details about format support, please refer to section 28.5.11 OpenText Document Filters of the
Content Server: Admin Online Help.
Word 95-2019 ✓ ✓ ✓
Excel 95-2019
Email – MSG
WordPerfect
RTF
CALS
PowerPoint 97-2019 ✓ ✓ ✓
Visio 2013, 2016
PDF
Postscript
MS Project 95-2007 ✓
TAR, LZH, RDL, ZIP
Mail RFC822
IGES (Windows only)
Important
For the latest compatibility information for OpenText products, refer to the
Compatibility Matrix (https://knowledge.opentext.com/go/matrix) on
OpenText My Support.
Component Languages
EN FR DE JA ES RU KO TW AR CA ZH NL FI IT KK PT SV UK
Smart View X X X X X X X X X X X X X X X X X X
Smart View X X X X X X X
User Help
Classic View X X X X X X X X X X X X X X X X X X
Classic X X X X X X X
View User
Help
Administration X X X X X X X X X X X X X X X X X X
Administration X X X X
Help
The managed download and installation using System Center is launched using the following steps:
Perspective conversion
Perspectives control how users see the layout of a Business Workspace in Content Server Smart
View. You design and configure a Perspective in Perspective Manager, a tool that walks you through
the creation of a Perspective and translates it into ActiveView coding.
Perspectives for Business Workspaces, which were created with versions 16.2.9 or earlier, are
Container Perspectives and they determine their respective Workspace Type with a rule. Starting with
version 16.2.10, this behavior has changed. Perspectives can now be Workspace Perspectives. The
Workspace Type is set automatically when you start Perspective Manager from the Workspace Type
Configuration page.
Secrets management
For secrets that are managed inside Content Server, a new configuration file called secrets.ini is used
to manage local secrets. The existing secrets stored in opentext.ini file will be migrated to the
secrets.ini during the upgrade. A new database table is created for managing global secrets.
A new file named key.bin is created under OTHOME/config/secrets folder to store the Data Encryption
Key, which was stored in opentext.ini before release 21.3. Key.bin file must be manually replicated
across all the instances of a cluster during the installation process.
The Signature Agent responsible for handling DocuSign envelopes will only use OAuth 2.0 as the
authentication mechanism. This is a switch from the Basic Authentication that has been used before.
Existing customers with already configured DocuSign integrations are required to retrieve the initial
authentication tokens for the REST API account previously configured in the Administration pages for
the DocuSign configuration on Content Server.
It is required to perform the “Test Settings” functionality available on the DocuSign configuration page
and click “Save Changes” after a successful test. This process will open a new window and ask for
the credentials of the REST API user that has been used previously in the existing configuration. After
successful authentication the Signature Agent will store and use the authentication and refresh tokens
retrieved from DocuSign using the OAuth 2.0 mechanism. The Signature Agent will automatically
refresh outdated tokens and the Agent will be able to perform tasks as before.
Patches for each component of Content Suite Platform CE 22.1 are listed in their respective folders
on OpenText My Support. OpenText also recommends that you check OpenText My Support for any
patches or documentation updates that may have been posted after this release. Furthermore,
OpenText strongly recommends using OpenText™ Cluster Management Patch Deployment System to
keep your Content Server up-to-date with all applicable patches.
OpenText also recommends that you check the Content Suite Platform and Content Server area of
the OpenText My Support
(https://knowledge.opentext.com/knowledge/llisapi.dll/open/KCProduct?id=342) for any
documentation updates that may have been posted after release.
Search Configuration Files. New versions of search configuration files are not installed when
applying an update to an existing system because replacing these files would overwrite
customizations previously made. In this case the latest versions of the configuration files are placed
in a reference folder where you can review them and select specific edits for your configuration files:
<OTHOME>\config\config_reference.
If you are installing this update as a new installation you will find these configuration files in
<OTHOME>\config.
The following table shows the latest changes of the configuration files. If an update is being applied
to a new installation, these files should be copied to the <OTHOME>\config directory before
indexing any data.
File Change
22.1
Changed:
SecretsConfigurationValid=A<1,?,'alreadyReported'=true,'messag
e'='System preferences file: {/OTHOME/config/opentext.ini}
Secrets anchor folder: {/OTHOME/} Optional read-only secrets
base folder: {/OTHOME/secrets/ContentServer/ [does not exist] }
Read-write secrets base folder: {/OTHOME/config/secrets/ [exists]
} Read-write secrets preferences file:
{/OTHOME/config/secrets/secrets.ini [accessible]
}','timestamp'=D/2022/1/11:11:51:43>
Changed:
ospaces_distributedagent={'distributedagent'}
To:
ospaces_distributedagent={'distributedagent','distributedagenttask
s'}
Changed:
ospaces_storageprovider={'storageprovider','awsstorageprovider','
gcpstorageprovider'}
To:
ospaces_storageprovider={'storageprovider','awsstorageprovider','
gcpstorageprovider','azurestorageprovider'}
Changed:
SecKeyConfTS=2022-01-11T12:00:15 29169
To:
SecKeyConfTS=2022-01-11T12:29:30 29633
Added:
[OTDS]
MigrateLogFile=otds_migrate_2022.01.11.123210.log
MigrateSuccess=TRUE
\config Changes made for SRCH-6369- newer indic characters not
\config\tokenizers searchable if using TolerantSubstringTokenizer.txt
\config\config_reference The sample TolerantSubstringTokenizer.txt file is updated to
\config\config_reference\tokeniz support more languages of India.
ers
See the TolerantSubstringTokenizer.txt file for the complete list of
character changes.
6.4 Hotfixes
Hotfixes are small patches that address software issues. Typically, there is no new functionality in a
hotfix.
Please see the respective area on My Support for required hotfixes and patches.
This section provides information about past issues at the Content Suite Platform level that have been
fixed in this release. There are no fixed issues at this time.
The list of known issues is covered in the Release Notes for each component within the Content Suite
Platform.
This section provides information about known issues at the Content Suite Platform level that exist in
this release.
9 Documentation Errata
- None -
39