Wrike - OpenText Active Community - Trading Grid Integration and Automation

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

• Partner issue resolution workflow: When a trading partner raises a shipment, invoice, or compliance issue in OpenText Active Community - Trading Grid, a corresponding task or project is automatically created in Wrike for the internal operations, finance, or customer service team. Status updates, owner assignments, and resolution notes are then synced back to the partner community so both sides have a clear view of progress. Direction: OpenText Active Community - Trading Grid to Wrike, with status updates back to OpenText Active Community - Trading Grid.
• Shared document review and approval: Trading documents such as contracts, product specifications, compliance forms, or corrective action plans uploaded in OpenText Active Community - Trading Grid can trigger a Wrike review and approval workflow. Wrike teams can route the document to legal, quality, procurement, or operations reviewers, then publish the approved version or approval status back to the partner community. Direction: Bi-directional.
• Exception management for B2B transactions: If a partner flags an exception such as a missing ASN, damaged goods, pricing discrepancy, or late delivery in OpenText Active Community - Trading Grid, Wrike can generate a structured exception case with due dates, dependencies, and escalation rules. Internal teams can collaborate on remediation while the partner community receives milestone updates and final disposition. Direction: OpenText Active Community - Trading Grid to Wrike, with updates back to OpenText Active Community - Trading Grid.
• Collaborative onboarding of new trading partners: New partner onboarding requests submitted through OpenText Active Community - Trading Grid can create a Wrike onboarding project with tasks for master data setup, EDI testing, compliance checks, account provisioning, and go-live readiness. Once each task is completed in Wrike, the onboarding status is reflected in the partner community to reduce follow-up emails and manual tracking. Direction: OpenText Active Community - Trading Grid to Wrike, with progress updates back to OpenText Active Community - Trading Grid.
• Cross-functional coordination for supply chain changes: When a partner posts a change request for lead times, packaging requirements, routing instructions, or product substitutions in OpenText Active Community - Trading Grid, Wrike can orchestrate the internal impact assessment across procurement, logistics, planning, and customer operations. Approved changes are then communicated back to the partner network with implementation dates and responsible contacts. Direction: Bi-directional.
• Corrective action and compliance tracking: Audit findings, nonconformance reports, or regulatory issues shared in OpenText Active Community - Trading Grid can be converted into Wrike corrective action plans with owners, deadlines, and dependencies. Wrike provides visibility into remediation progress, while the partner community receives evidence of completion, approval status, and closure notes. Direction: OpenText Active Community - Trading Grid to Wrike, with closure updates back to OpenText Active Community - Trading Grid.
• Partner communication dashboard for operational visibility: Wrike project and task status can be summarized and published to OpenText Active Community - Trading Grid as a partner-facing dashboard for key initiatives such as launch readiness, order recovery, or service improvement programs. This gives trading partners a controlled view of milestones, blockers, and expected completion dates without exposing internal task-level detail. Direction: Wrike to OpenText Active Community - Trading Grid.
• Escalation management for time-sensitive commitments: If a partner commitment in OpenText Active Community - Trading Grid is approaching a deadline, the integration can create or escalate a Wrike task to the accountable team with priority, SLA, and notification rules. Once resolved, the outcome and response time can be recorded back in the partner community for transparency and performance tracking. Direction: OpenText Active Community - Trading Grid to Wrike, with resolution updates back to OpenText Active Community - Trading Grid.