Content Aviator in Content Management 26.4 can act on workflows: pick which ones first

OpenText's latest update to its Content Management release blog, posted 9 November 2026, describes 26.4 moving Content Aviator from answering questions to taking workflow actions. Users can initiate workflows, take actions such as Forward, Send On and Send for Review, select dispositions such as Accept or Reject, and search for workflows, all through Content Aviator. The release also adds a Configuration Agent that builds a standalone workspace configuration, Smart Document Type suggestions on upload, Global Aviator across Smart View, and reusable prompt templates.

The blog doesn't mention SAP. If you run Extended ECM for SAP, it still applies. OpenText's lifecycle page lists OpenText Content Management as the latest release for Extended ECM for SAP Solutions, and the Content Management 26.4 release notes (KB0871793, sign-in required) cover Content Server and SAP Extended ECM 26.4 together.

Accept and Reject are decisions. Asking Aviator to find a workflow is navigation. Asking it to forward a task is routing. Choosing Accept or Reject is a decision someone used to make by clicking a button on purpose. In 26.2, OpenText added records actions by conversation, such as placing a document on hold. 26.4 carries the same idea into workflow outcomes.

None of that is a problem in itself. It does mean the list of workflows Aviator may act on should be written down, not discovered.

Sort your workflows before your users do. In our view, three groups cover most Extended ECM for SAP landscapes:

  • Fine through Aviator. Review and acknowledgement steps, internal Send for Review, and routing a person could do from a task list without reading the document.
  • Aviator prepares, a person decides. Approvals tied to an SAP business object: a purchase contract on a vendor workspace, an engineering change on an equipment workspace, an HR document. The SAP side may act on the outcome.
  • Kept out for now. Anything that ends in a records disposition or a hold release, and any step your auditors sample.

Then check what the system records. Before the first conversational Accept in production, confirm in the 26.4 release notes and in a test system how the workflow audit shows an action taken through Aviator, and whether it can be told apart from a click.

The Configuration Agent builds standalone workspaces. OpenText's wording is specific: the agent creates a complete standalone workspace configuration, including classifications, categories, templates and workspace types. Extended ECM for SAP workspaces are usually connected to SAP business objects through business object declarations and property mappings. Don't assume the agent builds those. Use it where it fits, and keep SAP-connected workspace types under your normal transport and change process. Whoever owns the business workspace should own any agent-built configuration too.

Same release, other lifecycle work. 26.4 also adds Information Archive integration for business workspaces that have reached the end of their active life. We covered who decides a workspace is complete earlier this month.

Version context. On OpenText's lifecycle page, read 14 November 2026, current maintenance for Extended ECM for SAP Solutions 22.4 ends 1 December 2027, with OpenText Content Management as the latest release. If a move to 26.4 is already on your plan, put the Aviator workflow list in the same plan. If Content Aviator isn't enabled in your landscape yet, the list is still cheap to write now, and it's easier to agree before anyone has tried it.

Where does your landscape stand?

Take the free Assessment. It's about 10 questions, and you get a one-pager with your estimated level of effort and suggested next steps.

McCloy Data

Thought leadership on OpenText, SAP, and practical content and finance automation - from the McCloy Data team.

https://www.mccloydata.com
Previous
Previous

Purview data governance retires in November 2027. Your labels and retention don’t

Next
Next

When a VIM problem spans SAP and OpenText: write the ticket both sides can use