OpenText Extended ECM - Content Server - OpenText TeamSite - LiveSite Content Services Integration and Automation

Common Integration Use Cases Between OpenText Extended ECM - Content Server and OpenText TeamSite - LiveSite Content Services

1. Approved document publishing from enterprise content repository to public web experiences

Data flow: OpenText Extended ECM - Content Server ? OpenText TeamSite - LiveSite Content Services

Business teams store final, approved documents in Extended ECM, such as product sheets, policy documents, investor materials, or service brochures. Once content is approved and version-controlled in the repository, it is published to TeamSite for delivery on websites and portals. This ensures only governed, current content is exposed to customers and partners.

• Reduces risk of outdated or unapproved content appearing on digital channels
• Separates content governance from content delivery
• Supports faster web publishing with controlled approval workflows

2. Personalized customer portal content using governed source documents

Data flow: OpenText Extended ECM - Content Server ? OpenText TeamSite - LiveSite Content Services

Organizations can manage source content such as contracts, service guides, onboarding documents, and account notices in Extended ECM, then deliver tailored versions through TeamSite based on customer profile, region, or product ownership. This is useful for customer portals, partner portals, and self-service experiences.

• Improves relevance of digital content for each audience segment
• Enables consistent messaging across web and document channels
• Supports localized and role-based content delivery

3. Web form submissions captured into controlled records and workflows

Data flow: OpenText TeamSite - LiveSite Content Services ? OpenText Extended ECM - Content Server

Forms hosted on TeamSite, such as lead capture, service requests, complaints, or registration forms, can send submitted data and attachments into Extended ECM for retention, classification, and workflow processing. This creates a controlled record of customer interactions and ensures business processes are triggered in the ECM environment.

• Creates a compliant audit trail for submissions and attachments
• Routes requests into internal approval or case management workflows
• Reduces manual re-entry of form data into back-office systems

4. Controlled reuse of marketing and legal-approved assets across digital channels

Data flow: Bi-directional

Marketing, legal, and compliance teams can manage approved assets in Extended ECM, including images, PDFs, disclaimers, and branded templates. TeamSite consumes these assets for web pages and campaign experiences. If a digital team needs a new version or updated asset, the request can flow back to Extended ECM for review and approval before publication.

• Ensures brand and legal consistency across all customer-facing content
• Supports governed reuse of high-value assets
• Reduces duplicate storage and uncontrolled file copies

5. Dynamic publication of policy and regulatory content to public and internal portals

Data flow: OpenText Extended ECM - Content Server ? OpenText TeamSite - LiveSite Content Services

Regulatory notices, privacy statements, terms and conditions, and internal policy updates are authored and approved in Extended ECM. After approval, TeamSite publishes the latest version to public websites or employee portals. This is especially valuable for industries with frequent compliance updates.

• Speeds up publishing of time-sensitive compliance content
• Maintains a single source of truth for regulated documents
• Reduces the chance of inconsistent policy versions across channels

6. Content lifecycle synchronization for expired or superseded web assets

Data flow: OpenText Extended ECM - Content Server ? OpenText TeamSite - LiveSite Content Services

When documents in Extended ECM are marked expired, superseded, or scheduled for disposition, that status can be communicated to TeamSite so the corresponding web content is removed, archived, or replaced. This is useful for product literature, event pages, campaign assets, and time-bound offers.

• Prevents outdated content from remaining live on websites
• Aligns web publishing with records retention policies
• Improves operational control over content expiration

7. Centralized content governance for multi-team digital publishing

Data flow: Bi-directional

Content authors, legal reviewers, records managers, and web publishers can collaborate across both platforms. Extended ECM manages the authoritative content lifecycle, while TeamSite handles presentation and delivery. Status updates, approvals, and publication events can be exchanged so teams have visibility into where content is in the process.

• Improves coordination between content owners and digital teams
• Provides transparency from draft to published state
• Supports enterprise-scale publishing with clear ownership and control

8. Secure delivery of enterprise documents through customer-facing portals

Data flow: OpenText Extended ECM - Content Server ? OpenText TeamSite - LiveSite Content Services

Organizations can store sensitive but shareable documents in Extended ECM, such as statements, reports, onboarding packs, or service documentation, and expose them through TeamSite portals with role-based access and contextual presentation. TeamSite acts as the delivery layer while Extended ECM remains the secure repository.

• Combines strong content governance with modern digital experience delivery
• Supports secure access to documents without duplicating content repositories
• Improves customer and partner self-service