Home | Connectors | OpenText Core Case | OpenText Core Case - DeSL Integration and Automation

OpenText Core Case - DeSL Integration and Automation

Integrate OpenText Core Case Case Management and DeSL Product Lifecycle Management apps with any of the apps from the library with just a few clicks. Create automated workflows by integrating your apps.

Common Integration Use Cases Between OpenText Core Case and DeSL

1. Product Development Issue Escalation into a Managed Case

Data flow: DeSL to OpenText Core Case

When a product development team identifies a critical issue in DeSL such as a failed sample approval, material compliance concern, or repeated specification mismatch, the issue can be automatically opened as a case in OpenText Core Case. The case can include the product record, affected style, vendor details, comments, and supporting documents from DeSL.

Business value: This creates a controlled escalation path for product risks, improves accountability, and ensures cross functional teams such as sourcing, quality, and compliance can resolve issues faster.

2. Case Driven Review of Product Compliance and Documentation

Data flow: Bi directional

OpenText Core Case can manage compliance or review cases for restricted substances, labeling approvals, or certification gaps, while DeSL provides the product master data and technical documentation needed to complete the review. Case workers can request missing information from DeSL, and once approved, the updated compliance status can be written back to DeSL.

Business value: This supports audit ready product governance, reduces manual follow up, and helps ensure only compliant products move forward in the development cycle.

3. Supplier Collaboration Exception Management

Data flow: DeSL to OpenText Core Case

If a supplier misses a milestone in DeSL such as sample submission, costing confirmation, or material approval, an exception case can be created in OpenText Core Case. The case can route to sourcing, vendor management, and product development teams for investigation and resolution, with all correspondence and evidence stored in the case file.

Business value: This improves supplier accountability, shortens resolution time for delays, and gives management a clear view of recurring supplier performance issues.

4. Product Change Request Governance

Data flow: DeSL to OpenText Core Case and back to DeSL

When a change request is raised in DeSL for a style, BOM, material, or packaging update, OpenText Core Case can be used to manage the approval workflow, impact review, and decision history. Once approved, the final decision and any required actions can be synchronized back to DeSL to update the product record.

Business value: This provides a formal approval trail, reduces unauthorized changes, and ensures product data remains consistent across teams and systems.

5. Customer or Retail Issue Investigation Linked to Product Data

Data flow: OpenText Core Case to DeSL

When a customer complaint, store issue, or retail quality incident is logged in OpenText Core Case, the case can be linked to the relevant product style or season in DeSL. Investigators can then access product specifications, sample history, supplier details, and development notes to determine root cause and corrective action.

Business value: This speeds up issue analysis, improves traceability from complaint to product record, and helps reduce repeat defects in future collections.

6. Launch Readiness and Go Live Exception Handling

Data flow: DeSL to OpenText Core Case

As a product approaches launch, DeSL can flag missing deliverables such as incomplete artwork, unresolved testing results, or pending approvals. These gaps can automatically generate a launch readiness case in OpenText Core Case for coordinated resolution across merchandising, design, quality, and operations.

Business value: This reduces launch delays, improves visibility into blockers, and helps ensure all required tasks are completed before product release.

7. Centralized Audit Trail for Product and Case Decisions

Data flow: Bi directional

OpenText Core Case can store the full decision history for investigations, approvals, and exceptions, while DeSL maintains the authoritative product development record. Key case outcomes such as approval status, corrective actions, and closure notes can be synchronized to DeSL, creating a complete audit trail across both platforms.

Business value: This strengthens governance, supports regulatory and internal audits, and gives business users a single view of both product history and case resolution.

How to integrate and automate OpenText Core Case with DeSL using OneTeg?