OpenText Extended ECM Platform - DeSL Integration and Automation

Common Integration Use Cases Between OpenText Extended ECM Platform and DeSL

• Product development document repository linked to DeSL style and item records

  Use OpenText Extended ECM Platform as the controlled repository for design briefs, technical packs, artwork, lab dip approvals, and specification documents while DeSL manages the product lifecycle record. When a new style or item is created in DeSL, the related documents are automatically created or linked in OpenText Extended ECM Platform. This gives product, design, and sourcing teams a single governed view of all supporting content.

  Data flow: DeSL to OpenText Extended ECM Platform

• Bi-directional approval workflow for product samples and sign-offs

  Connect DeSL sample and approval workflows with OpenText Extended ECM Platform workflow and records management. Sample submissions, fit comments, and approval documents can move from DeSL to OpenText Extended ECM Platform for controlled review, then approval status and decision metadata can be returned to DeSL. This reduces email-based approvals and creates an auditable trail for compliance and product launch readiness.

  Data flow: Bi-directional

• Centralized governance for supplier and compliance documentation

  Store supplier contracts, compliance certificates, testing reports, and regulatory documents in OpenText Extended ECM Platform and link them to supplier or product records in DeSL. Procurement and compliance teams can manage retention, version control, and access permissions in OpenText while DeSL users see the latest approved documents in context. This improves audit readiness and reduces the risk of using outdated certifications.

  Data flow: OpenText Extended ECM Platform to DeSL, with metadata updates from DeSL to OpenText Extended ECM Platform

• Season and collection launch package management

  When DeSL creates a new season or collection, OpenText Extended ECM Platform can automatically assemble the launch package containing line sheets, merchandising documents, pricing approvals, and launch checklists. Teams across design, merchandising, marketing, and operations can collaborate on the same controlled content set. This shortens launch preparation time and ensures every collection is released with complete documentation.

  Data flow: DeSL to OpenText Extended ECM Platform

• Change control for product specifications and revision history

  Use OpenText Extended ECM Platform to manage versioned product specification documents, while DeSL holds the master product record and change request status. When a spec changes in OpenText, the updated version and revision metadata can be synchronized back to DeSL so sourcing, costing, and production teams always work from the latest approved information. This reduces rework caused by outdated specs and improves traceability across the product lifecycle.

  Data flow: Bi-directional

• Supplier collaboration portal for controlled document exchange

  External suppliers can receive approved documents from OpenText Extended ECM Platform through secure access while DeSL tracks the associated product, material, or order context. Suppliers can upload updated certificates, packing instructions, or technical responses back into OpenText for review and approval before the information is reflected in DeSL. This creates a secure and governed collaboration channel without exposing the full PLM environment.

  Data flow: Bi-directional

• Retention and audit management for product development records

  After a product is discontinued or a season closes in DeSL, final records such as approvals, test results, and launch documents can be transferred to OpenText Extended ECM Platform for long-term retention and legal hold management. DeSL retains operational reference data while OpenText manages lifecycle, retention schedules, and audit access. This supports compliance requirements and reduces the burden on the PLM system.

  Data flow: DeSL to OpenText Extended ECM Platform