FTP - OpenText Core Case Integration and Automation

Common Integration Use Cases Between FTP and OpenText Core Case

1. Automated intake of case-related documents from external parties

Direction: FTP to OpenText Core Case

Organizations often receive large batches of supporting files from vendors, customers, brokers, or field teams through FTP or SFTP. These may include claim photos, signed forms, inspection reports, shipment evidence, or compliance documents. An integration can monitor FTP folders, ingest new files into the appropriate case, and attach them to the correct record based on file naming rules, metadata, or accompanying index files.

Business value: Reduces manual downloading and uploading, speeds up case creation, and ensures all evidence is centrally available for review and resolution.

2. Bulk document submission for high-volume case processing

Direction: FTP to OpenText Core Case

In high-volume operations such as insurance claims, loan exceptions, or regulatory reviews, external systems may export large daily batches of documents to FTP. OpenText Core Case can consume these batches and create or update cases in bulk, associating each document set with the right workflow stage. This is useful when source systems cannot connect through APIs but can reliably produce structured file drops.

Business value: Supports scalable intake for legacy and partner systems while maintaining case consistency and traceability.

3. Case document export for external review or archival

Direction: OpenText Core Case to FTP

When a case reaches a review milestone, OpenText Core Case can export selected documents, case summaries, or evidence packages to an FTP location for downstream consumers such as legal teams, auditors, print vendors, or external adjusters. This is especially useful when recipients require file-based delivery rather than direct access to the case management platform.

Business value: Simplifies controlled sharing of case materials with external stakeholders and supports formal review or archival processes.

4. Scheduled exchange of case evidence with legacy back-office systems

Direction: Bi-directional

Some organizations maintain legacy back-office platforms that exchange files through FTP, while OpenText Core Case manages the operational case workflow. A bi-directional integration can send case documents from OpenText Core Case to a legacy system for processing and receive returned outputs such as approvals, status files, or generated correspondence back into the case. This is common in claims, finance operations, and regulated service environments.

Business value: Bridges modern case management with older operational systems without requiring a full replacement of existing infrastructure.

5. Evidence collection for investigations and compliance cases

Direction: FTP to OpenText Core Case

Compliance teams often collect large evidence sets from multiple sources, including logs, spreadsheets, scanned forms, and exported reports delivered via FTP. OpenText Core Case can automatically ingest these files into an investigation or audit case, classify them by source or date, and route tasks to reviewers. This creates a complete case file for internal audit, regulatory response, or dispute resolution.

Business value: Improves audit readiness, reduces evidence handling errors, and gives investigators a single view of all case materials.

6. Customer support escalation package transfer

Direction: OpenText Core Case to FTP

When a support case requires escalation to a third-party service provider or engineering partner, OpenText Core Case can package relevant attachments, logs, screenshots, and case notes into a structured export and place it on FTP for retrieval. The partner can then process the package using their own systems and return findings or resolution files through the same channel.

Business value: Accelerates escalations, standardizes handoffs, and reduces back-and-forth email exchanges.

7. Media or large-file case attachment management

Direction: FTP to OpenText Core Case

Some case types involve very large files such as video evidence, high-resolution images, or engineering drawings. These files are often staged on FTP because of size or partner constraints. OpenText Core Case can ingest the files, link them to the correct case, and preserve them as part of the official case record for review, approval, or dispute handling.

Business value: Enables reliable handling of large evidence files while keeping the case record complete and accessible to authorized teams.

8. Batch status updates and case closure notifications

Direction: OpenText Core Case to FTP

After case processing, OpenText Core Case can generate batch output files containing case status, resolution codes, SLA outcomes, or closure summaries and place them on FTP for downstream reporting systems or partner consumption. This is useful when operational teams need nightly or hourly file-based updates rather than real-time API calls.

Business value: Keeps external systems synchronized with case outcomes and supports reporting, reconciliation, and partner notifications.