OpenText Extended ECM - Business Workspaces - OpenText TeamSite Authoring Services Integration and Automation

Common Integration Use Cases Between OpenText Extended ECM - Business Workspaces and OpenText TeamSite Authoring Services

1. Product launch workspace linked to approved web content

Data flow: OpenText Extended ECM - Business Workspaces → OpenText TeamSite Authoring Services

Marketing teams can manage a product launch workspace in Extended ECM that contains launch briefs, legal approvals, pricing sheets, and regional requirements. Once content is approved, the final product descriptions, campaign copy, and supporting assets are published into TeamSite for website updates.

• Ensures web content is based on approved business documents
• Reduces rework between product, legal, and marketing teams
• Improves launch consistency across regions and channels

2. Policy and compliance content governance for corporate websites

Data flow: Bi-directional

Compliance, legal, and communications teams can maintain policy source documents, review records, and approval history in Extended ECM while TeamSite manages the public-facing policy pages. When a policy changes, the updated document in Extended ECM triggers a review and publishing workflow in TeamSite.

• Maintains a clear audit trail from source document to published page
• Supports regulated industries with controlled approvals
• Reduces the risk of publishing outdated or unapproved content

3. Customer portal content aligned with account or case workspaces

Data flow: OpenText Extended ECM - Business Workspaces → OpenText TeamSite Authoring Services

For customer-facing portals, account teams can store customer-specific documents, service updates, and case notes in Extended ECM business workspaces. Selected content such as service advisories, account announcements, or knowledge articles can then be published to TeamSite for portal delivery.

• Improves consistency between internal account records and external portal content
• Speeds up publication of customer communications
• Supports personalized content based on account or case context

4. Campaign asset approval and publishing workflow

Data flow: OpenText TeamSite Authoring Services → OpenText Extended ECM - Business Workspaces

Digital teams can create campaign pages, banners, and landing page copy in TeamSite. Approved versions, final assets, and publishing records are then stored in an Extended ECM campaign workspace for governance, retention, and cross-functional visibility.

• Provides a controlled record of what was published and when
• Helps legal and brand teams review final assets after publication
• Supports reuse of approved content in future campaigns

5. Project workspace for website redesign and content migration

Data flow: Bi-directional

During a website redesign, project managers can use Extended ECM as the central workspace for requirements, stakeholder feedback, vendor deliverables, and sign-offs. TeamSite holds the actual page content and templates. Status updates, review comments, and approved content versions can move between both systems throughout the project lifecycle.

• Creates a single operational view of the redesign effort
• Improves coordination between business, IT, and web teams
• Reduces delays caused by disconnected review cycles

6. Knowledge article publishing from case resolution workspaces

Data flow: OpenText Extended ECM - Business Workspaces → OpenText TeamSite Authoring Services

Support teams can capture case resolution documents, root cause analysis, and approved responses in Extended ECM case workspaces. High-value resolutions can be converted into knowledge articles and published through TeamSite to the public website or support portal.

• Turns resolved cases into reusable customer self-service content
• Shortens time to publish support information
• Improves deflection of repeat support requests

7. Regional content localization and approval management

Data flow: Bi-directional

Global marketing teams can manage master content in TeamSite while regional business workspaces in Extended ECM track local legal requirements, translations, and market-specific approvals. Local teams review and approve region-specific versions before publication.

• Supports controlled localization across multiple markets
• Ensures regional compliance and brand alignment
• Provides visibility into translation and approval status