OpenText Core Case - FileSpin Integration and Automation

Common Integration Use Cases Between OpenText Core Case and FileSpin

OpenText Core Case is well suited for managing structured, case-based workflows that require collaboration, auditability, and controlled resolution. FileSpin is typically used to manage, transform, and distribute rich media and digital assets such as images, videos, documents, and branded content. Together, they can support workflows where case teams need fast access to approved files, version control, and secure content sharing across departments and external stakeholders.

1. Customer complaint and claims evidence management

Data flow: FileSpin - OpenText Core Case

When a customer complaint or insurance claim is opened in OpenText Core Case, supporting evidence such as photos, videos, scanned documents, or receipts can be pulled from FileSpin and attached to the case record. Case handlers can review all media in one place without searching across shared drives or email threads.

• Improves investigation speed by centralizing evidence
• Reduces manual file handling and duplicate uploads
• Supports consistent review and approval of supporting materials

2. Case-driven content approval and publishing

Data flow: OpenText Core Case - FileSpin

For regulated or brand-sensitive content, OpenText Core Case can manage the approval workflow while FileSpin stores the final approved asset versions. Once a case reaches approval, the finalized file is published to FileSpin for downstream use by marketing, customer service, or partner portals.

• Ensures only approved content is distributed
• Creates a clear audit trail for content sign-off
• Reduces risk of outdated or non-compliant assets being used

3. Secure media collection for investigations

Data flow: Bi-directional

Investigators or field teams can upload photos, videos, and supporting documents into FileSpin, which then syncs metadata and file references into OpenText Core Case. Case managers can request additional evidence from within the case, and contributors can respond by uploading directly to FileSpin without needing access to the full case system.

• Supports external evidence submission with controlled access
• Improves collaboration with field staff, customers, or partners
• Keeps sensitive case data separated from general file access

4. Product defect and quality incident resolution

Data flow: FileSpin - OpenText Core Case

Manufacturing or product support teams can store defect images, inspection videos, and test documentation in FileSpin, then link them to quality or warranty cases in OpenText Core Case. This gives engineering, quality assurance, and support teams a shared view of the issue and the evidence behind it.

• Speeds root-cause analysis with visual evidence
• Improves coordination between support and engineering teams
• Helps standardize defect triage and escalation

5. Compliance case evidence retention and audit support

Data flow: OpenText Core Case - FileSpin

For compliance reviews, OpenText Core Case can orchestrate the case lifecycle while FileSpin stores the supporting documents, screenshots, recordings, or policy artifacts associated with the case. Finalized evidence packages can be retained in FileSpin with version history and controlled access for audits or legal review.

• Strengthens evidence preservation and traceability
• Supports audit readiness with organized case artifacts
• Reduces risk of evidence loss or unauthorized changes

6. Service request resolution with rich media attachments

Data flow: Bi-directional

In customer support scenarios, agents can create a case in OpenText Core Case and request customers to upload screenshots, recordings, or documents through FileSpin. As the issue progresses, updated files and resolution materials can be returned to the case so agents always work with the latest version.

• Improves first-contact resolution by capturing better issue context
• Reduces back-and-forth email exchanges
• Keeps all customer-facing media tied to the case record

7. Controlled distribution of case-related deliverables

Data flow: OpenText Core Case - FileSpin

When a case results in a deliverable such as a settlement letter, investigation summary, training asset, or customer-facing report, OpenText Core Case can trigger the transfer of the approved file to FileSpin for secure sharing. Business users can then distribute the deliverable to internal teams or external recipients from a governed content repository.

• Ensures deliverables are shared only after case closure or approval
• Provides a single source of truth for final documents
• Supports secure access for internal and external stakeholders

8. Cross-functional case collaboration for media-heavy workflows

Data flow: Bi-directional

Organizations handling media-rich cases, such as legal matters, insurance claims, or field service incidents, can use OpenText Core Case for workflow orchestration and FileSpin for asset management. Case owners can assign tasks, request files, and track progress in OpenText Core Case while teams upload, review, and version media in FileSpin.

• Aligns task management with content management
• Improves visibility across legal, operations, and customer service teams
• Reduces delays caused by fragmented file handling