Wrike - OpenText Extended ECM - Content Server Integration and Automation

Common Integration Use Cases Between Wrike and OpenText Extended ECM - Content Server

• Project deliverables stored as governed records
  Wrike is used to manage the project plan, tasks, approvals, and deadlines, while final deliverables such as contracts, creative assets, specifications, and client sign-offs are automatically archived in OpenText Extended ECM - Content Server. This creates a controlled record of the approved version, improves audit readiness, and reduces the risk of teams working from outdated files.
• Bi-directional task and document collaboration for regulated projects
  When a document is created or updated in OpenText Extended ECM - Content Server, a corresponding task can be created in Wrike for review, editing, or approval. Once the task is completed in Wrike, the approved version and status can be pushed back to OpenText Extended ECM - Content Server. This is valuable for legal, compliance, engineering, and professional services teams that need both structured work tracking and governed content control.
• Automated intake of content requests into project workflows
  Business users can submit content or document requests through Wrike request forms, and the resulting project or task can be linked to the relevant folder, case, or document set in OpenText Extended ECM - Content Server. This streamlines intake for marketing campaigns, policy updates, proposal development, and client onboarding, ensuring requests are captured consistently and routed to the right content repository from the start.
• Approval workflows for controlled document publishing
  Wrike can manage the review and approval steps for documents stored in OpenText Extended ECM - Content Server, such as policies, procedures, marketing collateral, or customer-facing materials. After approval in Wrike, the document can be released or published in OpenText Extended ECM - Content Server with the approved status and metadata. This shortens approval cycles while preserving governance and version control.
• Centralized project visibility with linked content context
  Wrike project dashboards can display links or metadata from OpenText Extended ECM - Content Server so project managers can see which controlled documents are associated with each initiative. This helps teams quickly access the latest approved content without searching across systems, improving coordination across marketing, operations, and legal stakeholders.
• Retention and records management for completed work
  At project closeout, Wrike task histories, final approvals, and key deliverables can be transferred to OpenText Extended ECM - Content Server as part of the official project record. This supports retention policies, legal hold requirements, and long-term traceability for audits, client engagements, and regulated business processes.
• Enterprise content reference for cross-functional work execution
  Wrike teams can use OpenText Extended ECM - Content Server as the authoritative source for templates, standard operating procedures, brand assets, and reference documents. Wrike tasks can be linked to these controlled documents so teams always work from approved content, reducing rework and ensuring consistency across distributed teams and repeated project types.