OpenText has released Content Manager 26.2, the first in the 26.2 program series. It’s a solid update for records and information management teams, built around three themes: Collaboration, Integrations, and the Modern Interface. Here’s a rundown of what’s new, and what to think about before you upgrade.
AI-Powered Semantic Search and Classification
The headline feature is a new semantic framework spanning semantic indexing, auto-classification training, semantic search, and classification execution. Document content is converted into vector embeddings – documents are segmented into optimised chunks for efficient processing – and the system integrates with an AI-based semantic model deployed on supported environments.
In practice, this means search results that understand meaning rather than just matching keywords, and an auto-classification option (alongside the existing “Classic” method) that can be trained using a dedicated Records for Training tab. A new System Options AI page lets administrators enable embedding for search and auto-classification and set a minimum relevance score for search results.
A Modernised Web Client
The Web Client’s navigation has had a genuine rework. The old top-positioned hamburger menu is gone, replaced by a vertical sidebar on the left that can be collapsed between a detailed view (icons with labels) and a compact view (icons only) — making much better use of screen space. The Properties and Action panels have also been refreshed for a cleaner layout.
Stronger Security and Compliance
- Document-level encryption – a new option encrypts each document individually, adding protection even within existing document stores.
- TLS 1.3 support – for both the thick client and Content Manager servers.
- Assignee change controls – a new setting governs how the system handles assignee changes on checked-out documents or containers, with options to ignore, warn, or prevent the action (enforcing “Prevent” requires Record Administration permission).
- Inactive group validation – a new option can hide records from members of inactive groups who hold View Metadata or View Document access, tightening up access control hygiene.
- Enhanced audit logging – audit events now cover the full lifecycle of reports (creation, modification, deletion), with both active and offline audit events captured for Print Report actions.
Mobile App Improvements
The mobile app now supports barcode scanning for Code 39 and Code 128, with up to 1,000 recently scanned records stored locally on-device and searchable by multiple criteria. Bulk actions have also been added, letting users update assignees and home locations across multiple records at once.
Search, Records Management and Admin Enhancements
- Records can now be searched by Retention Schedule Number from both Quick Search and Refined Search.
- The Enterprise Studio’s SQL Text Index reindexing now supports date-range filtering via new “From Date (Registered)” and “To Date (Registered)” options.
- A new Data Cleanup option lets administrators delete completed workflows older than a specified number of days.
- Support for IMDSv2 (Instance Metadata Service Version 2) for AWS EC2 instances.
- A new option allows external systems to notify Manage-in-Place to scan and include specifically identified records (access restricted to users with Document Stores permission).
Expanded Microsoft Teams integration
Teams integration continues to mature significantly in this release:
- Exchange Online RBAC support – Azure AD–registered applications can now access mailboxes and calendars via Microsoft Graph API using app-only permissions.
- Additional metadata columns – up to five extra record metadata fields can now be displayed directly within Teams chats and channels.
- Tenant-level MIP configuration – Manage-in-Place store settings can be applied centrally and enforced across all Teams channels.
- Audit and revision tracking for MIP records – updates from source documents now sync properly, with external changes captured via the Offline Document Revision event, and existing audit history imported during file transfers.
- Finalized MIP Records tab – a new tab gives users quick access to only completed and approved records without leaving Teams.
- Several other refinements: capturing private two-person chats with defined scope, advanced search as the default for record creation, control over which record types are visible in Teams, and the ability to enable or disable the Expose Records option centrally.
What to check before upgrading to Content Manager 26.2
A few changes are worth planning around:
- SharePoint integration – Microsoft is retiring Remote Event Receivers (RERs) in SharePoint Online. Metadata sync will still work via webhook notifications, but user permission synchronisation may not occur where Content Manager ACLs are implemented within SharePoint. After upgrading, all Lifetime Management Policies (LMPs) need to be reapplied through the Default Integration Settings page — documents added between the upgrade and reapplication won’t be processed by LMPs in the meantime. It’s also worth configuring a Preservation and Hold library with an appropriate retention policy, so deleted documents aren’t lost.
- Outlook integration – Microsoft has discontinued support for COM add-ins in the new Outlook. Content Manager’s traditional Microsoft Office and Thin Office integrations are COM add-in based, so users migrating to the new Outlook will need to move to the web-based ZFP (Zero Footprint) client instead. Classic Outlook users can continue as before, though there are some user-experience differences between the two integration types worth being aware of.
- Windows Server 2016 is no longer supported.
- 32-bit Annotation & Redaction is obsolete as of Content Manager 24.5 – the 64-bit client is required to continue using these features, including annotating existing draft versions.
- If you’ve set a TempDB size limit in SQL Server, it’s worth increasing it, since the Workgroup Server now makes greater use of temporary tables.
Also Included
Alongside the new features, this release rolls up all fixes and enhancements shipped in previous Content Manager releases, plus a substantial list of its own bug fixes – touching search accuracy, Teams integration, access control, document check-in/check-out behaviour, and more.
Planning an Upgrade?
As an OpenText Silver Partner, the Miktysh team is already across the detail of 26.2 and what it means in practice for existing Content Manager environments. If you’re weighing up an upgrade or just want to understand how these new features could benefit your organisation, we’re happy to help you plan the path forward.
Content Miktysh to talk through your upgrade options.
