OpenText Active Community - Trading Grid - Marq Integration and Automation

Common Integration Use Cases Between OpenText Active Community - Trading Grid and Marq

• Partner-facing document distribution for branded communications
  Use Marq to create approved templates for onboarding packets, compliance notices, product updates, and partner announcements, then publish final assets into OpenText Active Community - Trading Grid for secure sharing with trading partners.
  Data flow: Marq - OpenText Active Community - Trading Grid
• Coordinated issue resolution with shared visual assets
  When a trading partner raises a transaction issue in Trading Grid, teams can attach Marq-generated diagrams, one-page instructions, or process guides to clarify the resolution steps. This reduces back-and-forth and helps partners act on the correct information faster.
  Data flow: Bi-directional
• Partner onboarding and enablement content management
  Operations teams can use Marq to produce standardized onboarding kits, training sheets, and process checklists, then distribute them through Trading Grid communities to new suppliers, distributors, or logistics partners. This improves consistency across the partner ecosystem and shortens onboarding cycles.
  Data flow: Marq - OpenText Active Community - Trading Grid
• Compliance and policy update dissemination
  Legal, compliance, or quality teams can update policy documents in Marq and push the latest versions to Trading Grid communities for partner acknowledgment and reference. This supports controlled communication of regulatory changes, packaging requirements, or audit instructions.
  Data flow: Marq - OpenText Active Community - Trading Grid
• Collaborative exception management for supply chain events
  If a shipment delay, invoice discrepancy, or order exception occurs in Trading Grid, the relevant team can generate a Marq-based exception summary or action sheet and share it with affected partners. This creates a clear, branded record of the issue, required actions, and deadlines.
  Data flow: Bi-directional
• Centralized partner communications with approved templates
  Marketing, procurement, or customer operations teams can maintain approved communication templates in Marq and use Trading Grid to distribute them to specific partner groups based on region, program, or transaction type. This ensures message consistency while still allowing targeted outreach.
  Data flow: Marq - OpenText Active Community - Trading Grid
• Shared knowledge base for recurring transaction scenarios
  Teams can convert frequently used troubleshooting steps, transaction FAQs, and process updates into Marq content and store or reference them in Trading Grid communities. Partners can then access the latest guidance without relying on manual email chains.
  Data flow: Marq - OpenText Active Community - Trading Grid
• Partner feedback collection and content refinement
  Trading Grid can be used to collect partner feedback on shared documents, while Marq is used to revise and republish improved versions of those materials. This creates a controlled feedback loop for continuously improving partner-facing communications and operational guides.
  Data flow: Bi-directional