OpenText Extended ECM - Business Workspaces - Adobe Experience Manager Sites Integration and Automation

Common Integration Use Cases Between OpenText Extended ECM - Business Workspaces and Adobe Experience Manager Sites

1. Publish approved workspace content to AEM Sites for customer-facing pages

Data flow: OpenText Extended ECM - Business Workspaces → Adobe Experience Manager Sites

Business teams manage source documents, product sheets, policies, or service descriptions inside OpenText business workspaces, where content is tied to the relevant customer, project, or case. Once approved, selected content is automatically pushed to AEM Sites for use on public websites, portals, or microsites.

• Reduces manual copy and paste between internal content repositories and web publishing teams
• Ensures only governed, approved content is exposed externally
• Speeds up updates to web pages when business information changes

2. Sync customer-specific documents from AEM Sites into account workspaces

Data flow: Adobe Experience Manager Sites → OpenText Extended ECM - Business Workspaces

Customer portals built in AEM Sites can generate or collect documents such as onboarding forms, service confirmations, warranty information, or personalized statements. These documents are then stored in the corresponding OpenText workspace linked to the customer account or case for long-term governance and operational use.

• Creates a single governed record for customer-related content
• Improves service team access to documents generated through digital channels
• Supports auditability and retention requirements

3. Manage web content approvals through business workspace workflows

Data flow: Bi-directional

Marketing teams create or request content changes in AEM Sites, while legal, compliance, product, or regional stakeholders review and approve the content in OpenText business workspaces. Approval status is then synchronized back to AEM Sites so only authorized content is published.

• Aligns web publishing with formal business approval processes
• Reduces compliance risk for regulated industries
• Provides visibility into who approved what and when

4. Reuse governed source documents from Extended ECM in AEM Sites content components

Data flow: OpenText Extended ECM - Business Workspaces → Adobe Experience Manager Sites

Frequently used business assets such as brochures, technical specifications, service terms, or investor documents are stored once in OpenText and reused in AEM Sites components. AEM references the approved source version rather than maintaining separate copies.

• Prevents version drift across channels
• Improves content consistency across web pages and landing pages
• Reduces duplication and content maintenance effort

5. Capture campaign assets and final web deliverables in project workspaces

Data flow: Adobe Experience Manager Sites → OpenText Extended ECM - Business Workspaces

When AEM Sites is used to produce campaign pages, landing pages, or localized web assets, final approved deliverables and supporting files are archived into the related project workspace in OpenText. This gives project teams a complete record of the campaign, including content versions, approvals, and published outputs.

• Improves project traceability and post-launch review
• Supports reuse of campaign materials for future initiatives
• Helps teams maintain a complete business record beyond the CMS

6. Link case or customer workspace data to personalized web experiences

Data flow: OpenText Extended ECM - Business Workspaces → Adobe Experience Manager Sites

OpenText workspace metadata such as customer segment, case status, contract type, or project phase can be used to drive personalized content delivery in AEM Sites. This enables tailored web experiences, such as showing relevant support content, next-step guidance, or account-specific resources.

• Improves customer self-service and relevance of digital experiences
• Uses trusted business data to personalize content delivery
• Supports more targeted communication without duplicating master data

7. Store web governance records and content lineage for compliance

Data flow: Adobe Experience Manager Sites → OpenText Extended ECM - Business Workspaces

AEM Sites publishing events, content revisions, and page approvals can be captured in OpenText workspaces associated with the relevant business object. This creates a compliance-ready record of what was published, who approved it, and which source documents were used.

• Supports regulatory audits and internal governance reviews
• Provides content lineage from source document to published page
• Helps organizations in regulated sectors manage digital risk

8. Coordinate multilingual and regional content updates across business and web teams

Data flow: Bi-directional

Regional teams manage localized source content, legal disclaimers, and market-specific documents in OpenText workspaces, while AEM Sites handles the delivery of localized web pages. Translation status, approval status, and final published versions are synchronized between both platforms to keep global and regional teams aligned.

• Improves control over localized content variations
• Reduces delays in regional web publishing
• Ensures consistent governance across markets and languages