OpenText TeamSite - LiveSite Content Services - NetX Integration and Automation

Common Integration Use Cases Between OpenText TeamSite - LiveSite Content Services and NetX

1. Digital Asset Delivery from NetX to OpenText TeamSite - LiveSite Content Services

Use NetX as the central digital asset repository and publish approved images, videos, and documents into OpenText TeamSite - LiveSite Content Services for use on websites and portals.

• Data flow: NetX to OpenText TeamSite - LiveSite Content Services
• Business value: Ensures web teams always use approved, brand-compliant assets while reducing duplicate storage and manual file handling.
• Typical workflow: Marketing uploads and approves assets in NetX, then selected assets are synchronized to TeamSite for page rendering and campaign delivery.

2. Metadata Synchronization for Personalized Content Experiences

Synchronize asset metadata from NetX into OpenText TeamSite - LiveSite Content Services so content authors can filter and personalize experiences based on campaign, region, product line, or usage rights.

• Data flow: NetX to OpenText TeamSite - LiveSite Content Services
• Business value: Improves content relevance and reduces the risk of using expired or restricted assets.
• Typical workflow: NetX provides asset tags, expiration dates, audience segments, and usage permissions that TeamSite uses to drive dynamic content rules.

3. Asset Usage Tracking from OpenText TeamSite - LiveSite Content Services Back to NetX

Send content usage information from OpenText TeamSite - LiveSite Content Services back into NetX to track where assets are published and how they are used across digital properties.

• Data flow: OpenText TeamSite - LiveSite Content Services to NetX
• Business value: Gives marketing and compliance teams visibility into asset distribution, reuse, and governance.
• Typical workflow: When an asset is embedded in a page or campaign, TeamSite records the page URL, publish date, and channel, then updates the asset record in NetX.

4. Approval and Publishing Workflow for Campaign Assets

Integrate NetX approval states with OpenText TeamSite - LiveSite Content Services publishing workflows so only approved assets can be used in live digital experiences.

• Data flow: Bi-directional
• Business value: Reduces compliance risk and prevents premature publication of unfinished content.
• Typical workflow: Creative teams approve assets in NetX, TeamSite checks approval status before publishing, and any rejected asset is automatically blocked from deployment.

5. Regional Content Syndication for Multi-Site Operations

Use NetX to manage master assets centrally and distribute them to multiple OpenText TeamSite - LiveSite Content Services instances for regional or brand-specific websites.

• Data flow: NetX to OpenText TeamSite - LiveSite Content Services
• Business value: Supports global content consistency while allowing local teams to publish faster with fewer manual steps.
• Typical workflow: Corporate marketing publishes a master campaign asset in NetX, and regional TeamSite environments receive the approved version with localized metadata.

6. Expiration and Rights Management Enforcement

Use NetX as the system of record for asset rights, expiration dates, and licensing terms, and have OpenText TeamSite - LiveSite Content Services enforce those rules at render time.

• Data flow: NetX to OpenText TeamSite - LiveSite Content Services
• Business value: Prevents legal exposure from expired or unauthorized content appearing on public sites.
• Typical workflow: TeamSite checks NetX rights metadata before rendering an asset and automatically suppresses content that is no longer valid.

7. Campaign Performance and Asset Reuse Reporting

Combine publishing data from OpenText TeamSite - LiveSite Content Services with asset master data from NetX to create reporting on campaign asset performance and reuse across channels.

• Data flow: Bi-directional
• Business value: Helps teams identify which assets drive engagement and which approved assets are underused.
• Typical workflow: TeamSite provides page and campaign performance data, while NetX contributes asset category, owner, and version details for consolidated reporting.

8. Content and Asset Lifecycle Automation

Automate the full lifecycle from asset creation in NetX to content publication in OpenText TeamSite - LiveSite Content Services, including review, update, and retirement.

• Data flow: Bi-directional
• Business value: Reduces manual coordination between content, creative, and web operations teams.
• Typical workflow: New asset versions in NetX trigger content review in TeamSite, and when an asset is retired in NetX, TeamSite removes or replaces it across affected pages.