"Modernize" is one of those words that ends meetings early. Everyone agrees with it, nobody defines it, and three months later the project turns out to mean a new server and the same experience.
For an estate running ApplicationXtender or an early AppEnhancer release, modernization can be pinned down, because OpenText has published what changed release by release. Below is that public record turned into a checklist. Go through it against your current version and mark each line Have, Need or Doesn't apply. The "Need" column is your modernization scope. Anything that isn't on it is a slogan.
1. The web client and the desktop
Fully web. AppEnhancer became a fully web offering in the 24 series. OpenText says that lowers cost of ownership and improves security. If your users still depend on an installed desktop client to do their jobs, this is line one.
Plug-in-free browser access. The product page describes an interface that runs in most HTML5-compliant browsers without plug-ins, plus web-based administration "to eliminate the need for a desktop client."
The new UI. 25.2 introduced a UI built on OpenText's JATO framework, with Classic mode kept for existing users. 26.2 brings JATO UI Phase III. Our companion post on Classic to JATO covers the transition.
Single sign-on. The product page lists broadened support for SSO technologies and authentication engines. Worth checking if your AX logins still live apart from your identity provider.
2. Retention, brought into the same place
Retention management on the web. In 23.4 OpenText brought retention management components to the web for the first time. The policy engine stayed the same; configuration and management moved into the browser.
A rebuilt retention service. 24.4 moved the retention service from C++ to .NET, which OpenText describes as resolving technical debt. It's invisible to users and matters to whoever patches the server.
Event-driven retention. OpenText's 2024 recap said the goal was to enable dynamic and event-driven retention rules in 2025, with 2024 laying the foundation. Confirm with OpenText what your target release actually supports before you design rules around it.
If retention in your estate is still a spreadsheet and an annual purge script, this section may matter more than the UI.
3. Getting documents in without living in the UI
Virtual printer (24.2). Users send a document to AppEnhancer from the print option in their native application.
Desktop connector (24.4, extended in 25.x). A rebuilt connector for indexing and classifying documents locally. OpenText says moving it from SOAP to REST took indexing "from minutes to seconds." The 25.2 release added better search and retrieval and an integrated viewer.
Web scanning and capture. The solution overview describes integrated web scanning with full OCR and metadata extraction from any scanner, plus client-side capture.
Microsoft 365. The solution overview lists a connector for Office Online Server so users can edit and save Office documents in place. 24.4 added a read-only Microsoft 365 integration, demonstrated with OneDrive, that OpenText describes as a first step toward read/write.
4. Retrieval from the line-of-business app
This is the part that makes AppEnhancer different from a stand-alone repository. Users in finance, HR or other core systems shouldn't need to open a second application to see the document behind a record.
REST services. The product page describes "a highly efficient and resource-centric API" for web, mobile and other connected platforms, and retrieval "without leaving line-of-business applications."
A current API layer. OpenText's 2025 recap mentions a new REST API service as part of cloud readiness, and 24.4 added Admin API enhancements.
Lightweight workflow. 24.4 added a one-way Flowable integration for simple document routing, with two-way integration on the 25.2 roadmap. 26.2 lists "unified workflow capabilities."
Richer process automation. The two-way connector to OpenText AppWorks goes back to the 2021 re-introduction. The solution overview lists AppWorks as an additional-cost module.
Report and print streams. Output Transformation Server replaced the old Reports Manager module and is also listed as an additional-cost module.
5. The engine room
IDOL search. 24.2 replaced Xplore with IDOL for full-text indexing, viewing and rendering. A companion post covers what that means for search.
Multi-tenant identity and process services. 24.4 notes OTDS and Process Automation multi-tenant support.
A deployment model you'd choose today. Windows Server, Microsoft Azure, containers and AWS are all on the public record now. A companion post walks through those options.
How to read your score
Count the "Need" marks. A handful, mostly in sections 1 and 3, usually means a straightforward version upgrade plus a training plan. A long list across sections 2 and 4 means the project is really about retention design and integrations, and that's where the time goes. Plan for it.
Two cautions. First, the additional-cost modules (AppWorks, Output Transformation) are packaging questions for OpenText, not assumptions for a project plan. Second, roadmap language in a recap post is not a feature in your release. Check the release notes for the exact version you're targeting.
Modernization, done properly, is an upgrade path you can operate afterward. This checklist is how you find out what yours includes.
