Information Archive 26.4 and Extended ECM: who decides a workspace is complete

OpenText Information Archive 26.4, released in October, adds a feature for clients who also run OpenText Content Management (Extended ECM). From the Content Management interface you can start archiving, and send completed business workspaces straight into Information Archive. OpenText says the content goes with its business information, metadata and audit history included, for compliant long-term retention. It supports on-premises and private cloud environments, hosted by OpenText or in your own.

For an SAP shop on Extended ECM, the word to stop on is completed.

Why SAP shops should look. Extended ECM for SAP organizes content in business workspaces tied to SAP objects: a project, a plant asset, a supplier, a contract. Those objects finish. Projects close, assets retire, contracts expire. Their workspaces usually stay where they are, full and searchable, years after anyone last opened them. The blog names Content Management (Extended ECM) without a separate SAP line, so confirm in the 26.4 release notes on OpenText My Support that SAP-connected workspaces are in scope, and what happens to the link from the SAP object once a workspace moves. Users who open a closed project from SAP will ask.

Completed is a business state, not a date. The feature archives completed workspaces. It can't tell you when a workspace is complete. That's a rule your organization writes, per workspace type, and it usually comes from the SAP side:

• Project. A reasonable "completed" signal: Project technically closed in SAP, final invoice posted. Who should own the rule: Project controls lead.

• Supplier. A reasonable "completed" signal: Supplier blocked or marked for deletion, no open items. Who should own the rule: Procurement master data owner.

• Contract. A reasonable "completed" signal: End date passed, no renewal, no open claims. Who should own the rule: Legal or contract management.

• Plant asset. A reasonable "completed" signal: Asset retired, final maintenance order closed. Who should own the rule: Maintenance or engineering lead.

Those signals and owners are our suggestion. Use your own, but write them down before the first workspace moves. A workspace that leaves too early takes a working team's documents with it.

Retention starts somewhere. Long-term retention needs a start event. For most of these types it's the completion itself, so the completion date is also the date your retention clock starts. Agree that with records management, and decide what happens to a workspace under legal hold. Our view: it doesn't move until the hold is released, unless your records owner signs off on archiving it with the hold carried along.

Who works the archive later. Information Archive has added retention controls in recent releases. Since 25.3, retention managers can see records in retention sets, hold sets and purge lists even when the data is cached out to object storage. Since 25.4, they can manage jobs for their own applications without full administrator rights. Those are the people who'll own archived workspaces, so bring them in before the first batch, not after.

Mind your release. When we checked OpenText's lifecycle page on 10 October 2026, it listed 1 November 2026 as the date current maintenance ends for Extended ECM for SAP 21.4. The page now shows only product-level dates: current maintenance for Extended ECM for SAP Solutions ends 1 December 2027, for Extended ECM generally 1 July 2029, and for Information Archive 31 October 2031, with 26.4 as its latest release. There's no separate 21.4 row any more, so confirm your exact release with OpenText My Support. Patch level matters too. OpenText Support, KB0874468, reports a cross-site scripting vulnerability in Content Management (Content Server 20.3 to 25.2.0), fixed by a hotfix or an upgrade to 25.3 or later (sign-in required). Apply it before you open the archiving path. The release notes will say which Content Management releases the 26.4 integration needs. If you're still on 21.4, expect the upgrade to come first. We covered the 21.4 dates, who owns a business workspace and what Information Archive is for in an SAP shop earlier.

Start with one workspace type. Projects are usually the cleanest, because SAP already knows when one is closed.

Where does your landscape stand?

Take the free Assessment. It's about 10 questions, and you get a one-pager with suggested next steps and typical budget ranges, which aren't quotes.