OpenText Core Case - OpenText Legal Hold Integration and Automation

Common Integration Use Cases Between OpenText Core Case and OpenText Legal Hold

• 1. Auto-initiate legal holds from active case events

  When a case in OpenText Core Case is escalated to litigation, regulatory review, or internal investigation, the integration can automatically create a legal hold in OpenText Legal Hold. Case metadata such as matter ID, subject, jurisdiction, and involved parties can be passed to Legal Hold to define the hold scope quickly and consistently. This reduces manual handoffs between legal and operations teams and helps ensure preservation begins without delay.

  Direction: OpenText Core Case to OpenText Legal Hold

• 2. Synchronize case participants with custodian lists

  OpenText Core Case often contains the people involved in a matter, such as employees, managers, customers, or third parties. These participants can be synchronized to OpenText Legal Hold as custodians or notified stakeholders. Legal teams can then issue hold notices to the correct individuals based on case assignments and updates, improving accuracy and reducing the risk of missed custodians.

  Direction: OpenText Core Case to OpenText Legal Hold

• 3. Surface legal hold status inside the case workspace

  Case workers in OpenText Core Case can see whether related information is under legal hold, including hold status, notice date, acknowledgment status, and release date. This gives investigators, claims handlers, or compliance officers immediate visibility into preservation requirements before they request, update, or close a case. It helps prevent accidental actions that could conflict with legal obligations.

  Direction: OpenText Legal Hold to OpenText Core Case

• 4. Block case closure until preservation obligations are cleared

  OpenText Core Case can be configured to check OpenText Legal Hold before allowing a case to close. If a related hold is still active, the case remains open or moves to a restricted status until legal confirms release. This creates a controlled workflow that prevents premature closure of matters that still require retention, review, or evidence preservation.

  Direction: Bi-directional

• 5. Preserve case content and attachments tied to a matter

  Documents, emails, notes, and attachments stored in OpenText Core Case can be flagged for preservation in OpenText Legal Hold when a matter becomes subject to litigation or investigation. The integration ensures that content linked to the case is identified and protected from deletion or alteration. This is especially valuable for claims, HR investigations, and compliance reviews where case records may later become evidence.

  Direction: OpenText Core Case to OpenText Legal Hold

• 6. Trigger legal hold release when a case is resolved

  Once a case in OpenText Core Case is fully resolved and no further legal retention is required, the system can notify OpenText Legal Hold to review and release the associated hold. Legal teams can then confirm whether preservation can end based on policy and matter status. This helps avoid unnecessary retention, lowers storage and review burden, and supports defensible disposition.

  Direction: OpenText Core Case to OpenText Legal Hold

• 7. Provide a unified audit trail for investigations and compliance matters

  By exchanging status updates, notifications, and key timestamps, both systems can maintain a shared audit trail across the case lifecycle and the legal hold lifecycle. OpenText Core Case records operational actions such as assignment, escalation, and resolution, while OpenText Legal Hold records hold creation, notice delivery, acknowledgments, and release. Together, they provide a complete record for audits, eDiscovery, and regulatory inquiries.

  Direction: Bi-directional