OpenText Active Community - Trading Grid - Adobe Experience Manager Sites Integration and Automation

Common Integration Use Cases Between OpenText Active Community - Trading Grid and Adobe Experience Manager Sites

1. Trading Partner Issue Resolution Portal Published in Adobe Experience Manager Sites

Data flow: OpenText Active Community - Trading Grid ? Adobe Experience Manager Sites

Use Trading Grid community discussions, case updates, and shared documents to power a secure partner support portal in AEM Sites. Marketing or partner operations teams can publish approved issue-resolution content, FAQs, and status updates to a branded external website while keeping sensitive collaboration inside Trading Grid.

• Reduces inbound support calls and email traffic
• Improves partner self-service with current issue information
• Ensures only approved content is exposed externally

2. Partner Onboarding and Enablement Content Synchronization

Data flow: Adobe Experience Manager Sites ? OpenText Active Community - Trading Grid

AEM Sites can publish onboarding guides, training pages, policy updates, and launch announcements into Trading Grid communities for trading partners. This gives partner managers a controlled way to distribute enablement content and track partner engagement in the collaboration environment.

• Speeds partner onboarding and readiness
• Creates a single source for approved enablement materials
• Supports consistent communication across large partner networks

3. Shared Document Publishing for B2B Transaction Exceptions

Data flow: Bi-directional

When a transaction exception occurs, Trading Grid can capture supporting documents, dispute notes, and resolution artifacts. Approved summaries or reference documents can then be published in AEM Sites for internal teams or partner-facing knowledge pages, while AEM-hosted policy documents can be linked back into the Trading Grid case workspace.

• Improves visibility into transaction exceptions
• Reduces duplicate document storage and manual re-entry
• Helps operations, support, and content teams work from the same approved materials

4. Partner-Specific Content Delivery Based on Trading Grid Community Membership

Data flow: OpenText Active Community - Trading Grid ? Adobe Experience Manager Sites

Membership, partner tier, or trading relationship data from Trading Grid can be used to personalize AEM Sites content for authenticated partners. For example, a distributor can see region-specific product updates, compliance notices, or order process instructions relevant to their community.

• Delivers more relevant partner experiences
• Reduces confusion caused by generic content
• Supports scalable personalization for large partner ecosystems

5. Launch and Promotion Coordination for New Trading Programs

Data flow: Adobe Experience Manager Sites ? OpenText Active Community - Trading Grid

When marketing launches a new product, promotion, or trading program in AEM Sites, the same content can be pushed into Trading Grid communities for partner notification and coordination. Partners receive launch details, required actions, and supporting assets in the collaboration space where they already manage operational communication.

• Aligns marketing launches with partner operations
• Improves adoption of new programs and offers
• Reduces delays caused by fragmented communication

6. Compliance and Policy Update Distribution to Trading Partners

Data flow: Adobe Experience Manager Sites ? OpenText Active Community - Trading Grid

Compliance teams can maintain policy pages, regulatory notices, and process updates in AEM Sites and automatically distribute them to relevant Trading Grid communities. Partners can review the latest approved content, acknowledge receipt, and ask questions in the same collaboration environment.

• Ensures partners receive current compliance information
• Creates an auditable communication trail
• Reduces risk from outdated or inconsistent policy documents

7. Partner Feedback Loop for Digital Experience Improvements

Data flow: Bi-directional

Feedback collected in Trading Grid from partners about website usability, content gaps, or broken workflows can be routed to AEM Sites teams for content and experience improvements. In return, AEM Sites can publish release notes, updated navigation guidance, or new help content back to the Trading Grid community.

• Connects partner feedback directly to digital experience teams
• Improves website relevance and usability for external users
• Shortens the cycle between issue identification and resolution

8. Centralized Knowledge Base for Partner Operations

Data flow: Bi-directional

AEM Sites can serve as the governed front-end knowledge base for partner-facing operational content, while Trading Grid acts as the collaboration layer for exceptions, clarifications, and case-specific discussions. Content owners publish approved articles in AEM, and partner support teams use Trading Grid to discuss how those articles apply in real scenarios.

• Separates published knowledge from active collaboration
• Improves content governance and reuse
• Supports faster resolution of partner questions and operational issues