Extended ECM CE 23.1 Release Notes
Extended ECM CE 23.1 Release Notes
Release Notes
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 for any patches or documentation updates
that may have been posted after the initial release of this product.
5.6 SAP Business Suite Added differentiation for SAP customers and
2023-07-10 and SAP S/4HANA support for SAP S/4HANA 2022.
compatibility
Corrected limitation for the support of SAP
S/4HANA Cloud Public Edition.
The product family of Extended ECM is a leading Enterprise Content Management (ECM) system,
managing the information lifecycle across the enterprise, from capture to archiving and disposition.
It can be integrated into various business applications such as SAP S/4HANA, SAP SuccessFactors,
or Salesforce, has deep integration into the Microsoft 365 collaboration suite and supports many
different business processes with out-of-the-box Business Scenarios as well as tailor-made
applications that can be developed or customized with Extended ECM.
Extended ECM offers different deployment options, ranging from installation directly on physical
hardware, virtual machines to modern, cloud-native deployments using Docker images and Helm
charts on Kubernetes platforms such as Microsoft Azure, Google Cloud Platform, and AWS.
OpenText Extended ECM (Private Cloud) is the equivalent private cloud service offering which can be
considered as an alternative to customer-managed deployments.
The release notes cover the entire family of Extended ECM products including:
Kubernetes deployment is not available for SAP customers. OpenText™ Extended ECM for
Salesforce® is not available for SAP customers, unless the customer purchases separate Extended
ECM for Salesforce® subscription from OpenText.
Content Server combines related products, modules, and components in one installable software
package. There is no need to identify, check compatibility, check availability, and install modules
individually.
By consolidating and simplifying our Content Server delivery, we will provide a clearer view of all the
capabilities and opportunities Extended ECM can bring to you and your business.
You will find these capabilities as structural elements in this Release Notes document, as well as in
the documentation. For more information, see Documentation
What has changed for you? After installing Extended ECM – or upgrading your system to CE 23.1 –
your installation is a complete Extended ECM system. For a complete list of components see
Packaging and downloads
Your license agreements and license keys will determine the allowed use of the software. Additional
functionality may be accessible to you. However, your license agreement with OpenText remains
Upgrading from a legacy license model to the Extended ECM X-Plans requires a new contract and
therefore cannot be carried out automatically. It requires manual steps after the license has been
changed.
The Extended ECM X-Plan license enforcement prevents compliance issues like overuse or
unentitled use. Because Extended ECM checks the license of every use upon sign in, it is not
possible to sign in to the system without at least an X1 license.
The Extended ECM X-Plans license key clearly shows the type of X-Plan and the number of
purchased named users. Users in groups or partitions need to be allocated to a license type. Upon
first sign in, each named user is counted against the purchased number of licenses. If that number is
used up, no additional new users can sign in. The license counters and their usage can be monitored
in OTDS.
Note
SAP customers: Kubernetes deployment is not available for SAP customers.
OpenText™ Extended ECM for Salesforce® is not available for SAP customers.
Extended ECM 23.1 includes new features for the following capabilities:
For more information, see Extended ECM Smart View User Guide.
• System Messages: Introduced system messages in Smart View. Multiple system messages are
displayed at sign-in time and are configured by administrators.
• Language Settings: Enabled users to set or switch their language and metadata language
settings from their user profile, which is accessible from Smart View.
For more information, see Extended ECM Smart View User Guide.
• Responsive Browse: Extended ECM containers can automatically reload content when other
users interact with the system, ensuring that the latest data is always available to users.
• Value String Matching: Searching against Categories is supported in the UI. Users no longer
need to write complex queries to apply entire value match to Category Attributes.
• Search Pattern Matching: Users no longer need to manually switch to complex query. Detection
of pattern in the full text field will automatically trigger the switch to the complex query mode.
• Search Pattern Matching: Added an administration page to configure search pattern matching.
Previously this had to be done through editing a configuration file on disk. For more information,
see Search Pattern Matching.
Business Workspaces
• Improved Business Workspace visual design: For a better user experience, the Workspace
Perspective in the Smart View Web UX and in integration scenarios will use the full width and
height.
• Improved handling for reference Attributes: Regenerate reference Attributes when multiple
Categories with text reference Attributes are added to the Business Workspace in Classic View.
For more information, see Business Workspaces Configuration Guide.
• Workspace name based on user information: Use username instead of user ID, first name and
last name when creating a Business Workspace from a User Field Attribute.
For more information, see Business Workspaces Configuration Guide.
• Improved auditing for changed roles: Audit for roles shows which user was added or removed
from a Business Workspace role.
For more information, see Content Server Administration: OpenText Content Server.
• Improved transport for custom columns: Transport Business Workspace Perspectives with
two custom columns used in one field of the Related Workspaces tile. To make use of this feature,
the Business Workspace Perspective must be repackaged in a transport.
For more information, see Widget Configuration Guide: OpenText Content Server.
• Annotation Indicator: An indicator will be displayed on the Workspace to alert users that an
annotation exists on a Document.
• Searchable Annotations: Annotation content can be found using Extended ECM Search.
For more information, see Intelligent Viewing User Guide: OpenText Extended ECM.
• Multi-File View with Business Workspaces: Business Workspace containers can be selected
for viewing child-content in a single viewing session.
For more information, see Intelligent Viewing User Guide: OpenText Extended ECM.
Document generation
• Event Bots for Document generation: Business administrators can configure Event Bots that
automatically create documents based on various triggers, for example when a Business
Workspace has been created. This enables users to better automate processes and document
generation requirements.
For more information, see Extended ECM Platform Integration Guide: Mapping Business
Properties to Category attributes.
• Fonts: Customers can provide their own fonts if they chose to use them in document designs. If
fonts are not provided, during PDF generation Extended ECM will automatically choose from a
set of fonts available to the system. The Extended ECM container includes the Google Noto
library and fonts used during document design are replaced with a similar font during PDF
generation.
• Security Enhancements: For increased security, Extended ECM PowerDocs Tomcat database
credentials can be encrypted on file level.
For more information, see OpenText Extended ECM PowerDocs: Server Installation Guide.
• Workspace integration – Dynamic Tables: Document designs often include tables with a
dynamic number of line items. Line items are filled with data from Business Workspaces set
attributes to, for example, generate invoices or contracts with meaningful data.
For more information, see Extended ECM Platform Integration Guide.
• Name Conflict in Teams Integration: Improved name handling when conflict occurs during
synchronization of content between Teams and Extended ECM.
• Support Office Editor with Edge in SAP GUI: Support editing of documents using Office Editor
from embedded Extended ECM in SAP GUI 7.7 for Windows when the SAP GUI is configured to
use Edge (based on Chromium) browser controls. For information on how to enable Office Editor
with Edge in SAP GUI, see Knowledge Base article KB0783668.
• Preview Button: Administrators can hide the Preview button in Enterprise Connect for all users
by default. For more information, see the Enterprise Connect Installation Guide.
• Progress dialog box: Disable the Cancel button in the Progress dialog box when only one item
or the last item from a set of documents is being processed during a drag and drop operation in
Enterprise Connect.
• Recent Business Workspaces node: Added a Recent Business Workspaces node in Enterprise
Connect to display a list of recently created or updated Business Workspaces by the user for easy
• Physical Objects table maintenance codes: The following Physical Object table maintenance
codes can be created in Smart View from their various fields:
• Location code from the Physical Item's Add\Properties page and from the Physical Item's
Circulation - Borrow & Return.
• Reference Rate code from the Physical Item's Add\Properties page.
• Locator Type code from the Physical Item's Add\Properties page.
• Improve support for authentication with assertion tickets (level 3): Introduced a way to
distribute the WSDLs without any additional manual editing by a developer.
For more information, see OpenText Extended ECM for SAP Solutions: Installation and Upgrade
Guide.
• Support document-based approval processes in SAP S/4HANA: Users can view documents
of Business Workspaces in corresponding items in the SAP Fiori My Inbox as described in the
knowledge-based article.
For more information, see KB0594776.
• Migration utility in Extended ECM for SAP: As part of the discontinuation of Imaging Reviews
and Notes module, added a utility that migrates notes and annotations to be directly accessible
using Extended ECM Imaging Viewers configurations.
For more information, see the Integrating Viewers section in OpenText Extended ECM for SAP
Solutions: Customizing Guide.
2.3.8.3 Salesforce
• Customer Feedback: Added a button in the Extended ECM for Salesforce Admin Center which
guides users to the location on AppExchange where they can share their experiences working
with Extended ECM for Salesforce with the community. This customer feedback function is
currently only available for Extended ECM for Salesforce administrators.
• Added a Content Synchronization Rule Mismatch Queue: The mismatch queue assists the
administrator to set up complex rules to identify any attachment not matching an active rule and
are therefore not migrated to Extended ECM. The queue also allows the administrator to select
individual attachments or the entire queue of attachments for reprocessing. For more information,
see OpenText Extended ECM for Salesforce: Customization Guide.
• Single Sign-on Authentication with Extended ECM: Extended ECM administrators can enable
authentication of Core Share with Extended ECM using Single Sign On using additional
parameters in the Authentication Endpoint URL for connecting Extended ECM to Core Share.
For more information on setting up Authentication Endpoint URL, see Content Sharing
Administrative Guide.
Developer
• Code Coverage: CSIDE 23.1 introduces a feature to help developers see which functions do not
have associated unit tests. Full details of this feature can be found in the product documentation
(in the "The Unit Test Coverage Report" section of the "Unit Testing for OScript" page). For more
details refer to ContentServerSDK Offline documentation
• Eclipse Version upgrade: CSIDE 23.1 requires Eclipse 2022-03 (or higher).
• Content Server SDK Documentation is included in the CSIDE plug-in (via the help menu).
• CSIDE’s “OScript Search” functionality has changed in this release. The documentation has been
updated to include a description of search functionality (in the “Learning the CSIDE Interface”
section).
For more details refer to ContentServerSDK Offline documentation
• Kubernetes Secrets: The Helm charts uses an existing Kubernetes Secret file by default. If you
have an existing secrets file in your deployment, replace the otxecm-default-secrets value
in the <platform>.yaml file with the existing secret name. If you do not have a secret file, a
default secret with the name otxecm-default-secret will be created based on the value from
the “masterPassword” parameter.
• Content Server Memcached: The Memcached servers can be manually specified across
Content Server instances. By default, it maintains a minimum of three Memcached servers with
256 MB of memory each, auto-balanced across Admin Servers.
• Content Server Syndication: The Helm charts and automation is capable of enabling and
performing basic configuration for the Content Server Syndication feature. For more information,
see Content Server Syndication.
Add-On Engineering
• Maintain Document Distribution Matrix: Simplified maintenance of the existing Document
Distribution Matrices through newly added actions - Duplicate, Edit, Activate, Deactivate and
Purge.
• Support Greenfield Project: Allow documents to be controlled from within Project Workspaces in
addition to Master document Workspaces.
• Enhanced Project Revision Segment: Enhanced the Project Revision Segment to
accommodate the Numeric Revision Scheme.
Add-On Government
• Integration of Intelligent Viewing: Added support for printing eFiles and eCases using
Intelligent Viewing. See Extended ECM for Government guide.
• Add to eCase: File content from Inboxes to eCases, and now also to eFiles, and Folders. See
Extended ECM for Government guide.
• Inbox: Added support for dragging and dropping content into the Inbox (tab documents). See
Extended ECM for Government guide.
• XDOMEA: As part of compliance with XDOMEA specification, added support for messages 0504,
0505, and 0506. See Extended ECM for Government guide.
• Proxy users and Dynamic Workflows: Proxy users cannot see privately marked tasks in the
Inbox.
• Dynamic Workflows and attached content: New attachment widget improves usability and
focuses on relevant functionality. Users with sufficient privileges can change document roles, add
documents, view documents, view properties, download documents, and add new versions to
existing documents.
• Tasks: Shows completed dynamic workflow tasks in My Contributions.
• Dynamic Workflow and email notifications: AppWorks Platform supports email notifications.
Email notifications can be configure based on workflow metadata.
• Dynamic Workflow and sharing: The Workflow Template can be shared with users and groups.
When the Dynamic Workflow is started, only users with privileges are able to select the Workflow
Template.
• Dynamic workflow and inactive users: Administrators can search for inactive users and
reassign the Workflow initiator and tasks.
In a first step, features are marked as deprecated to make customers aware of upcoming changes.
Deprecated features should not be used in new implementations. The functionality is yet not removed
from the software, but customers are encouraged to consider alternatives to prepare for a future
change. Deprecated features remain in this state for several updates, providing the opportunity to
plan and adapt.
After a certain period, functionality is officially discontinued. It is removed from the product and certain
cross-product compatibility is no longer maintained. OpenText offers either automatic conversion to
newer functionality, or if not possible for technical or commercial reasons, gives advance notice by
announcing the deprecation of the feature in the Release Notes.
Discontinued
• Legacy Print controls with Internet Explorer: Starting with version 22.4, Enterprise Connect
and Office Editor no longer use Internet Explorer for any of its functionality. Therefore, legacy print
control or printing using Office Editor with Internet Explorer has been removed from the Office
Editor administration setting.
• Binders and Cases object types: Have been discontinued starting with version 22.4. They have
been replaced by Business Workspaces and were no longer recommended for new
implementations since 2017 (release 16.2.0). Customers need to convert existing Binders and
Cases into Business Workspaces using the migration utilities available with Extended ECM. For
more information, see Knowledge Base Article.
• Engineering Workspace rule has been dropped from the Perspective Manager. OpenText
recommends that you use the Workspace Template rule while creating Perspectives.
• Imaging Reviews and Notes: Has been discontinued as of CE 23.1. It should not be used for
any new deployments. As part of the discontinuation, added a utility that migrates notes and
annotations to be directly accessible using Extended ECM Imaging Viewers configurations for the
ArchiveLink documents, which can be used for existing deployments.
• Smart View light theme CSS file: Smart View light theme CSS file (/img/csui/themes/
light/overrides.css), which provides the CSS styles for light theme, is discontinued in Extended
ECM 23.1.
Deprecated
The following features are deprecated and will be discontinued in the future:
• Remote Cache: Is deprecated and should not be used for new installations. Syndication should
be explored as a replacement.
• Server platforms and databases:
• Windows Server: Windows 2012 support is deprecated as of 22.1.
• Windows Server: Windows 2016 will be deprecated as of 23.2.
• Web Server: Tomcat 8.5 will be deprecated as of 23.2.
• Application Server: Tomcat 8.5 will be deprecated as of 23.2.
• Apache HTTP Server 2.4x is deprecated.
• SQL Server Clients prior to version 17 are deprecated as of 22.2.
• Oracle Enterprise Database 12.2.0.1 is deprecated as of 22.4.
• SQL Server 2016 is deprecated as of 22.4.
• SQL Server Clients prior to version 18 will be deprecated as of 22.4.
• PostgreSQL 11 will be deprecated as of 23.3.
• Azure Database for PostgreSQL Single Server is deprecated as of 22.4, and it is replaced by
Azure Database for PostgreSQL - Flexible Server.
• Tomcat 9 support will be discontinued and replaced with Tomcat 10. This transition is
expected in the 23.2 update, but Archive Center will continue to support Tomcat 9 and will
move to Tomcat in the future.
• Linux 7 support will be deprecated from 23.4.
• Project and Community object types have been replaced by Business Workspaces and are no
longer recommended for new implementations. OpenText is planning to discontinue these object
types in the fourth quarter of 2023 (release CE 23.4) and is recommending converting existing
Projects and Communities into Business Workspaces using the migration utilities available with
Extended ECM.
• My Mailbox: This feature has been deprecated. The feature can be enabled but it will be
removed from Extended ECM in a future release.
• Content Web Services: This feature has been deprecated as of CE 22.4. Content Web Services
is no longer recommended for new implementations and existing implementations should
leverage the REST API infrastructure.
• Tempo Box support: CE 22.4 is the last update that will have the ability to support Tempo Box
integration.
• Business Object Browser: Starting with CE 22.4, OpenText Business Object Browser is
deprecated and should not be used for new installations. Instead, you can create SAP Fiori
element apps based on metadata and annotations of OData services and place the Fiori UI
component for Business Workspaces or Business Documents inside these generated Fiori
element apps.
As announced in previous release notes, the Salesforce Federated Search (SFFS) application has
been removed from the product. During the provided transition period limited product support is
available until the fourth quarter of 2023 (release 23.4). Customers who wish to continue using
Salesforce Federated Search are advised to consult the respective product documentation and
should make the necessary arrangements to update their configuration.
OpenText Extended ECM applications running in the Salesforce Classic user interface have been
retired as of October 31, 2022 and will no longer be supported. Additional capabilities and feature
configuration will only be available in the Extended ECM by OpenText Lightning application going
forward. If you are using Salesforce Classic, you will need to switch to Salesforce Lightning mode to
make configuration changes in the new Extended ECM by OpenText Lightning application. For more
information about making the switch to Salesforce Lightning, please visit
https://help.salesforce.com/s/articleView?id=000317946&type=1.
Document Self Service widget/Upload widget: Starting with release CE 22.2, this widget is
deprecated and is replaced by the File Upload widget in the platform. To avoid confusion the Upload
widget has been renamed to the Self Service widget.
SAP SuccessFactors Workspace Creation/Update (starting with CE 22.1): The previous job for
creating/updating Workspaces provided by versions CE 21.4 and earlier is deprecated and is no
Document Generation for Candidates (starting with CE 22.1): Document Generation for
candidates using the Employee Workspaces widget is no longer recommended. It is recommended
that you use the new Document Generation action from the Documents tab. For more information,
see User Guide: Creating documents in the Documents tab.
SAP SuccessFactors authentication change: By November 2023, SAP is going to enforce the use
of OAuth for integrations. Customers can only use the Central Workspace Update/Creation Job after
this date. In case the previous job for creating/updating Workspaces has been used, the migration
needs to be completed by this date. Extended ECM CE 21.4 or earlier will stop functioning in this
scenario.
Tomcat: Tomcat 9 support will be discontinued and replaced with Tomcat 10. This transition is
expected in the 23.2 update.
2.4.2.5 Developer
OSX Export: Functionality is deprecated and will be removed in a future release of CSIDE.
Old auto format feature: With CSIDE 16.2.8 a new implementation of the OScript Auto Format
feature was introduced while retaining the possibility to switch to the old implementation using a
Preferences switch. With the 23.2 update the "old" auto format implementation will be removed from
the CSIDE code base along with the Preference switch. Starting with CSIDE 23.2 the "new" auto
format implementation will be the only OScript auto format option.
Freeze functionality deprecated: Freeze is covered by Closure (Z.d.A.) and for that reason will be
deprecated. Freeze will no longer be available on Documents or Workspaces.
Interactive Correspondence for Content Server (ICCS), the Content Server module which provides
document generation with Exstream, is now deprecated. As the alternative, use Extended ECM
PowerDocs, which is the fully integrated method for document generation. OpenText intends to
discontinue ICCS by early 2025.
Note
SAP customers: Note that the deployment using Docker images on Kubernetes
is not available for SAP customers.
The Extended ECM Helm charts are available in the OpenText Helm charts registry and can be
obtained by running the following commands in the terminal:
In addition, the Helm charts are available for download at OpenText My Support, where you will also
find the OpenText Extended ECM – Cloud Deployment Guide, which describes how to use
Kubernetes and Helm to deploy Extended ECM Docker images on the supported Kubernetes
platforms.
The required Docker images used by the Extended ECM Helm charts are published at the OpenText
Docker container registry: registry.opentext.com. The Helm charts are already configured to use this
registry address by default.
In addition, the following Docker images are used by the AppWorks Gateway Helm charts.
For more information about System Center, see the product page at OpenText My Support.
Add-On for Office Online Broker Office Online Broker This will require the
Microsoft Office Downloads Documentation installation and
Online Server deployment of the
(Broker) Microsoft Office
Online Server on
your premises.
Contact your
account executive if
you want to
integrate your
Extended ECM with
Microsoft Office
Online Service.
SAP Add-On SAP Add-On
Packages Packages Downloads
Engineering Engineering Connect Engineering Connect
Connect Downloads Documentation
Imaging Windows
Viewer Downloads
Imaging OutlookLink
Downloads
Note
License agreements and license keys will determine the permitted use of the
software. Some components such as various Extended ECM variants, Intelligent
Viewing, OpenText™ Email Cloud Archiving, CMIS Document Pipeline for
Archive Center, Document Pipeline for File Archiving, OpenText™ Document
Pipeline for SAP® Solutions, Document Pipeline for DocuLink, Add-on for
Microsoft™ Office Online, integration with Core Share, and Interview module are
included in the components of Extended ECM but are licensed separately.
The following table lists all components of Extended ECM 23.1 without license consideration. For a
list of functions included with each component, see Licensed Functionality.
Capture Center Limited to 1 million pages per year and per contract **
Extended ECM for SAP Included in the SAP reseller product bundle only *
Solutions
Brava! CS Module Does not include CAD rendering *
Extended ECM Enabler for License is limited to the use of the Dynamic
AppWorks Workflow *
Extended ECM for SAP Included in the SAP reseller product bundle
Solutions only *
* Needs explicit activation or configuration. Feature is deployed, but not enabled or configured by
default. If your organization has licensed this feature, you are entitled to enable it.
General
3.5.3.1 Usage of XML Workflow Extensions
Using XML Workflow Extensions requires XML Workflow Extensions licenses, Regulated Documents
licenses, or Extended ECM X-Plan licenses.
Using Electronic Signatures requires Electronic Signature licenses, Regulated Documents licenses, or
Extended ECM X-Plan licenses.
Using Controlled Viewing and Printing requires Regulated Documents licenses or Extended ECM X-
Plan licenses.
Archive Center CMIS is not part of Content Suite Platform or Extended ECM licenses. Using Archive
Center CMIS requires additional licenses.
The Searchable PDF DocTool allows rendering of scanned documents to searchable PDF/A. The
DocTool usage is strictly restricted to scan pipelines together with Enterprise Scan, which means it is
only for documents manually scanned in with Enterprise Scan. Batch conversion of imported images
is expressively not a legitimate use of the software.
WebReports functionality is not included in Content Suite Platform licenses. Using WebReports
requires Extended ECM, WebReports, or Content Intelligence licenses.
WebReports is deployed but not enabled by default. If your organization has licensed Extended ECM,
WebReports, or Content Intelligence you are entitled to enable WebReports and confirm the number
of licensed seats for your organization.
3.5.4.2 Usage of Automatic Document Numbering and Table Key Lookup attributes
Automatic Document Numbering (ADN) and ADN Table Key Lookup attributes are not included in
Content Suite Platform licenses. Using Automatic Document Numbering and ADN Table Key Lookup
attributes require Extended ECM licenses.
Object Importer is not included in Content Suite Platform licenses. Using Object Importer requires
Extended ECM or Object Importer licenses.
Remote Cache and Syndication are not included in Content Suite Platform licenses. Using Remote
Cache and Syndication require Extended ECM, Remote Cache, or Syndication licenses.
Content Server SDK is not included in Content Suite Platform licenses. Using Content Server SDK
requires Extended ECM or Content Server SDK licenses.
SAP S/4HANA
3.5.5.1 Usage of OpenText™ Fiori Business Object Browser for SAP Solutions
OpenText Fiori Business Object Browser for SAP Solutions includes two add-ons of OpenText Vendor
Invoice Management for SAP Solutions to implement custom Business Object Browser Fiori apps to
show SAP Business Objects and its data, browse Business Objects, and bring content into context by
integrating the Business Documents Fiori App and Business Workspace Fiori App of Extended ECM.
You are allowed to use the customizing options and enhancements described in the OpenText Vendor
Invoice Management for SAP Solutions Customizing Guide for Foundation. The following usages
need extra licenses for OpenText Vendor Invoice Management for SAP:
• Solutions specifically designed for preconfigured processes such as incoming sales orders,
purchase order/purchase requisition dashboard, or incoming delivery.
• OpenText Vendor Invoice Management for SAP Solutions for:
o Import
o Capture
o Dispatch
o Process
Note
In case of doubt, the license audit report of Vendor Invoice Management can be
executed to find out if the framework is used in a way that needs extra licenses
for OpenText Vendor Invoice Management for SAP Solutions.
Add-On Government
License term for the AppWorks Platform Dynamic Workflow
The usage right of the AppWorks Platform with Extended ECM for Government is limited to the
Dynamic Workflow. The compliant use of the limited AppWorks Platform license can be checked by
verifying the deployed solutions. For this, the AppWorks solutions “OpenText Dynamic Workflow,
OpenTextEntityIdentifyComponents, OpenTextInboxTaskManagement” must be deployed. Other
Workflows except the deployed solutions require a full-use AppWorks license.
The use of external REST API from AppWorks (for example, to integrate third-party applications)
requires a full-use AppWorks license. Customers are licensed to use the internal REST API from the
AppWorks Integration Bridge (AIB) within Extended ECM for Government (for example, to create
WebReports).
Unlimited Citizen access is allowed as long as the minimum number of full users have been licensed
(for SAP reseller customers and since 21.2 for OpenText direct customers with perpetual license). The
Software Product may be used by citizens or residents of an End User that qualifies as a Public
Sector body but use by a citizen or resident is restricted to use directly related to the governmental
use authorized. Use by a citizen or resident in any other capacity is excluded.
4 Documentation
You can access product documentation that supports this Extended ECM release from the following
locations:
• View the online help available in the Extended ECM Smart View and Classic View interfaces.
• Visit OpenText My Support (https://support.opentext.com) to view the Extended ECM product
documentation. All Extended ECM guides can be accessed quickly from the OpenText
Extended ECM Documentation List.
Caution
Note
For the latest compatibility information for OpenText products, refer to the
Compatibility Matrix (https://knowledge.opentext.com/go/matrix) on OpenText My
Support.
The following Extended ECM web user interface features require a specific version of Enterprise
Connect or Office Editor. These features are supported on Windows only as Enterprise Connect and
Office Editor are Windows-based applications.
Send to mail as
attachment
Send to my working
documents list
Content Server 22.x, 21.x, 20.x, 16.2.x Review KB article KB0777292 for
more details and compatibility
requirements.
Microsoft Office Suite 2016 32-bit and 64-bit Word, Excel, PowerPoint,
2013 SP1 32-bit and 64-bit Project, Visio, Outlook, Long
term Service Channel (LTSC).
Important
Due to some security fixes introduced in the Extended ECM Mobile App
22.3, devices running the app must have their Gateway URL
reconfigured.
To resolve the issue of Extended ECM Mobile CE having no connectivity,
each device running Content Server Mobile must connect to the
AppWorks Gateway for security updates. Perform the following steps:
1. In Extended ECM Mobile CE, tap Settings.
2. The Server setting has the network address of your AppWorks
Gateway server. Tap Server.
3. On the Server page, tap the check mark icon to re-initialize your
Server setting.
After you do this, Extended ECM Mobile CE can connect to the AppWorks
Gateway server.
Office 365 Integration Service 2016, 2019 and SharePoint Support for App-Only
23.1 Online Authentication requires
SharePoint 2019.
Component Client OS
Feature Client browser
Name
Engineering Edit CAD Windows 10 Firefox ESR / Quantum
Connect documents Update 1709 Google Chrome
Microsoft Chromium Edge
5.2.3.1 Windows
On Windows 2016 x x x x
On Windows 2019 x x x x x
On Windows 2022 x x x
On Oracle Linux 7 x x x x
On Linux RHEL 7 x x x x x
On Linux 8 x
* For Extended ECM Containers, the following managed database services are supported:
5.2.4.2 Oracle
• Oracle support includes Standard, Enterprise, and RAC as well as deployment on Oracle
Exadata Database Machine, Oracle Data Guard, and Oracle SuperCluster as supported by
Oracle.
5.2.4.3 PostgreSQL
Java
Component OpenJDK
distributed by the Adopt
OpenJDK organization
11 17
System Center CE 22.4 Java not required
Note
SAP customers: Note that the deployment using Docker images on Kubernetes
is not available for SAP customers.
Important
Customers deploying Extended ECM images 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 for CE
23.1 until September 2023.
Customers who expect to remain on CE 23.1 past this date should consider
creating and managing their own containers or use traditional methods of
installation and patching.
Customers who choose to use a virtual environment are encouraged to select a virtualization platform
intended for production systems and known to be fully supported by the server operating system
vendor.
Microsoft Azure, Google Cloud, and AWS are supported virtualization environments.
Extended ECM 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 a physical environment.
Static or committed resources within a Virtual Environment are typically needed for
performance-sensitive scenarios.
All file types are supported on Windows and Linux except where indicated.
MIME type extraction is supported for all file types except CDR.
On Linux operating systems, only Western languages are supported for View as Web Page and
Thumbnails.
Document Formats PDF, XLSX, XLSM, PPT, PPTX, PPTM, DOC, DOCX, DOCM, MSG
Image Formats JPG, JP2, PCX, PNG, TIF, TIFF, BMP, GIF, PS/EPS
The formats listed in the previous table represent the most used formats. For a complete list of
formats supported by Intelligent Viewing see Intelligent Viewing - Supported Formats. Please take
note that this document does not indicate if a format is part of the complimentary or premium offering.
Engineering Connect
Engineering Connect supports CAD drawings created using Auto CAD and MicroStation with the
DWG and DGN extensions only.
SAP NetWeaver > 7.0 All SAP systems running on the required SAP_BASIS
version, for instance:
EhP 1 - 2 for SAP NetWeaver 7.0
EhP 1 for SAP NetWeaver 7.3 • EhP 4-8 for ERP 6.0
SAP NetWeaver 7.40 • CRM 7.0
SAP NetWeaver 7.50, 7.51, 7.52 • EhP 1-4 for CRM 7.0
• SRM 7.0
• EhP 1-4 for SRM 7.0
SAP S/4HANA Applications on-premises 1610, 1709, 1809, 1909, 2020, 2021, 2022, 20231
and single tenant
All FPS are supported.
• SAP S/4HANA on-premises SAP S/4HANA for Customer Management 1.0, 2.0
• SAP S/4HANA Cloud, private edition
• SAP S/4HANA Cloud, extended edition
1
Before converting or upgrading to SAP S/4HANA 2023, please consider the following:
• Customers not using OpenText Business Object Browser and OpenText Vendor Invoice
Management must uninstall the OTBCBAS, OTBCWUI, and OTEXBASB add-on packages to
continue with Extended ECM CE 22.4 on SAP S/4HANA 2023.
• Customers using OpenText Business Object Browser or OpenText Vendor Invoice
Management must upgrade Vendor Invoice Management to 23.4 as part of the conversion or
upgrade process.
2
SAP S/4HANA Cloud is limited to sales, procurement, finance, and partly plant maintenance
processes; documents stored via Extended ECM UI are accessible for SAP users within SAP Fiori apps
depending on the Fiori technology of each individual Fiori app
SAP Version SAP GUI for SAP GUI for SAP SAP GUI for
Software Windows HTML NetWeaver Java
Component Business
Client
(NWBC)
1) Only the Microsoft Edge (based on Chromium) Browser Control option is supported.
SAP GUI for Windows and NWBC versions, for which SAP support has ended, are no longer listed
here. See also SAP Notes 147519 Maintenance strategy / deadlines for SAP GUI for Windows / SAP
GUI for Java and 2302074 - Maintenance strategy and deadlines for SAP Business Client / NWBC.
The CMIS attribute type Document Category is treated as an external document type. For this
release, the following table lists supported entities, Workspaces, and corresponding SAP
SuccessFactors Document Categories. Business administrators can create corresponding Extended
ECM document types (Classification) to control the storage logic of SAP SuccessFactors’s Document
Categories. Documents which are uploaded for SuccessFactors entities that do not have
corresponding Workspace definitions will be stored in the technical repository (CMIS volume) and can
only be accessed by Extended ECM System Administrators. Employees or HR Business partners can
only access these documents from the SAP SuccessFactors user interface. Please note that the
Document Categories might vary from SAP SuccessFactors tenant to tenant. The following table only
lists standard SuccessFactors Document Categories.
Employee BUS1065
OpenText Content Services for Salesforce 23.1 Salesforce Sales, Service and Marketing
Cloud
OpenText Extended ECM for Salesforce 23.1
(Spring ’23)
The Extended ECM for Salesforce App advances quickly and it is important to match the OpenText
Extended ECM Platform versions with the matching Extended ECM for Salesforce App Packages. For
example, Extended ECM for Salesforce 23.1 is tested and certified to work with Extended ECM 23.1.
Note
SAP customers: OpenText™ Extended ECM for Salesforce® is not available for
SAP customers.
Salesforce limitations
• Salesforce Console:
o The Extended ECM for Salesforce workspace widget is currently not supported if
used in combination with Salesforce Console apps.
Yes
Arabic AR No
(except Government, PowerDocs)
Yes
Catalan CA (except Office 365, Salesforce, Government, No
PowerDocs)
Yes
Chinese (Simplified) ZH No
(except Government)
Yes
Chinese (Traditional) ZF (except Office 365, Salesforce,Government, No
PowerDocs)
Yes
Czech CZ No
(except Intelligent Viewing)
Yes
Danish DA No
(except Intelligent Viewing, PowerDocs)
Yes
Dutch NL No
(except Office 365, Government, PowerDocs)
Yes
Finnish FI No
(except Office 365, Salesforce, Government)
Yes
Hebrew IW (except PowerDocs, Imaging Viewers, No
Intelligent Viewing)
Yes
Japanese JA Yes
(except Government)
Yes
Kazakh KK No
(except Office 365, Government, PowerDocs)
Yes
Korean KO (except Office 365, Salesforce,Government, No
PowerDocs)
Yes
Norwegian NO No
(except Intelligent Viewing)
Yes
Polish PO No
(except Intelligent Viewing)
Yes
Swedish SV (except Office 365, Salesforce, Engineering, No
Government)
Yes
Ukrainian UK No
(except Office 365, Engineering, PowerDocs)
Note
SAP customers: OpenText™ Extended ECM for Salesforce® is not available for
SAP customers.
3. When prompted, select Install for Admins Only (default) and click Install.
4. When the installation is completed, click Done.
If your Salesforce organization is using the user licenses model (and not the Salesforce Site License
model) for Extended ECM for Salesforce application, you will need move user licenses to the new
managed package application. You will need to move the user licenses from the Extended ECM
Content Services for Salesforce package component in the Installed Packages section in the
Note
Extended ECM 23.1 is a rewrite of the existing Extended ECM for Engineering
16.3.x solution. Updates to this new software are released in parallel to the
updates of the existing Extended ECM 16.3.x. Both versions can co-exist in the
same Content Server instance. The existing instances of Extended ECM 16.3.x
cannot directly upgrade to Extended ECM 23.1 or subsequent Extended ECM CE
versions because the architecture and design differs from that of Extended ECM
16.3.x. However, the new projects can be configured to start using Extended ECM
23.1 capabilities.
The XENG module folder in <OTHOME>/module is not deleted during the upgrade because the JAR
files in the folder are in use. To avoid issues with these JAR files, stop Content Server and delete
these folders manually after the upgrade.
Extended ECM for Engineering CE has been enhanced to support version-specific relationships to
retain the relationships on older versions of the documents for auditing purposes.
A new relationship model with the following relationship types is implemented in the Extended ECM
for Engineering – CAD Manager module:
• Dynamic
• Static
• Node Specific
1. Navigate to Content Server Administration > Database Administration > Test or Repair
Known Database Issues > Convert RM Cross References to CAD References.
Note: Records Management cross-references relationships stored in the KIni table are
considered for conversion. OpenText recommends validating the entries in the KIni table
before initiating the conversion.
2. Run the following SQL Query to fetch the existing Records Management cross-reference
types from the database:
SELECT * FROM KIni WHERE IniSection = 'xengcrt' AND IniKeyword IN ('Dynamic',
'Static', 'Node Specific')
3. Modify the entries in the KIni table to add or drop any Records Management cross-
reference type from the conversion process.
7 Patches
7.1 Migration utility in Extended ECM for SAP
Apply the patches before running the migration utility. The Migration utility patches are cumulative,
and you need to apply them in the documented sequence.
Fix: Apply the below patch to have the migration utility appear under the job type for Extended ECM
for SAP Solutions product.
pat162005506_CS64_WIN.zip
pat162005506_CS64_LNX.tar.gz
Fix: Apply the below patch to run the migration job without script crash error.
pat162005499_CS64_WIN.zip
pat162005499_CS64_LNX.tar.gz
pat162005499_CS64_LNX8.tar.gz
9 Known issues
The following known issues exist in this release.
Business Workspaces
ESOC-12768 When editing a Wiki page in Smart View, it is not possible to use the Shift key,
for example to capitalize a letter. For a workaround, users may switch to
Classic View.
LLWR-17046 Perspective Manager Shortcut Group shortcut items cannot be edited. This will
be possible in future releases.
LPAD-35560, Records Management: When RM metadata fields are required on the Add Item
LPU-5344 page and the items are dragged and dropped in Content Server Classic View,
the user is not prompted to fill in the RM required fields. The content will be
uploaded and the next time the user accesses the Records Detail tab the user
will be prompted to fill in the required fields.
LPJ-3870 When you create a new Workflow Map for use with Electronic Signatures, if
you select the "Initiate from Document" check box the option is not retained
when you save the Workflow Map.
Workaround: Create the Workflow Map and then open the Properties page for
the Workflow Map. Click the “Specific” tab, then select the “Initiate from
Document” check box and click Update.
SAPGV-7322
Dynamic Workflow: With release 23.1, the dynamic workflow is not supported.
The dynamic workflow uses an incorrect attachments widget and for that
reason content in context of the workflow is not displayed. Patch 23.1 HF1 will
fix this problem.
XECMPF-12127;
Dynamic workflow: Can be started without main doc and main doc can be
XECMPF-11865;
deleted.
SAPGV-8116
XECMPF-11072
Dynamic workflow: When changing the document role for a document, a
PostgreSQL is coming-up.
SAPGV-8132
Dynamic workflow: When starting a predefined dynamic workflow, the iframe
stays open.
BOP-166817
Dynamic workflow: Templates cannot be saved by normal users (without
workflow manager right)
XECMPF-11839;
Dynamic workflow: When creating an inquiry from an assigned task, it fails.
BOP-16631;
BOP-166642
BOP-165902;
Dynamic workflow: For assigned tasks, the forward to groups fails.
XECMPF-
11839
BOP-163845 Dynamic workflow: Reject dialog box shows an option that is not enabled.
SAPGV-7896 Inbox and Intelligent Viewing: When viewing forwarded content in the Inbox,
the content cannot be viewed with Intelligent Viewing.
BOP-162904 Inbox and Dynamic Workflow: Delegate task is not shown in the Inbox.
SAPGV-7950 Add-to-eCase for forwarded item causes "The item could not be accessed”
error message.
XENG-2690 Extended ECM for Engineering functionality is not available in Content Server
Mobile.
SAPRM-20801 Business Scenarios 22.4 does not include the Enterprise Asset Management
business scenario. KB0783083 is the post-release delivery of this business
scenario.