Home | Connectors | OpenText Decision Service | OpenText Decision Service - OpenText Legal Hold Integration and Automation

OpenText Decision Service - OpenText Legal Hold Integration and Automation

Integrate OpenText Decision Service Business Transaction Management and OpenText Legal Hold Document 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 Decision Service and OpenText Legal Hold

1. Automated legal hold trigger based on policy-driven case criteria

When a litigation, investigation, or regulatory matter is opened in OpenText Legal Hold, OpenText Decision Service can evaluate predefined rules to determine whether a legal hold must be issued. For example, the decision engine can assess matter type, jurisdiction, claim value, data sensitivity, and retention obligations before approving the hold workflow.

  • Data flow: OpenText Legal Hold to OpenText Decision Service
  • Business value: Faster, more consistent hold initiation with fewer manual reviews
  • Operational benefit: Legal teams apply the same criteria across matters and reduce risk of missed holds

2. Custodian inclusion rules based on role, location, and matter relevance

OpenText Legal Hold can send custodian details to OpenText Decision Service to determine who should be placed on hold. The rules engine can evaluate employee role, department, geography, reporting line, project assignment, and involvement in the matter to recommend the correct custodian list.

  • Data flow: OpenText Legal Hold to OpenText Decision Service
  • Business value: More accurate custodian selection and reduced over-preservation
  • Operational benefit: Legal and HR or compliance teams can align on repeatable inclusion criteria

3. Content preservation decisions based on document classification and retention status

OpenText Legal Hold can pass content metadata to OpenText Decision Service so the system can decide whether specific records should be preserved, exempted, or escalated. Rules can consider document type, retention schedule, business owner, sensitivity label, and whether the content is already under another hold.

  • Data flow: OpenText Legal Hold to OpenText Decision Service
  • Business value: Better preservation decisions and lower storage and review burden
  • Operational benefit: Prevents unnecessary holds on non-relevant content while protecting critical evidence

4. Escalation of high-risk matters for legal approval

OpenText Decision Service can evaluate matter attributes and automatically route high-risk cases from OpenText Legal Hold to legal leadership for approval before the hold is activated. For example, matters involving multiple jurisdictions, executive custodians, or sensitive investigations can require additional sign-off.

  • Data flow: OpenText Legal Hold to OpenText Decision Service and back to OpenText Legal Hold
  • Business value: Stronger governance for complex or sensitive matters
  • Operational benefit: Ensures exceptions and high-impact decisions are reviewed consistently

5. Dynamic release of holds based on rule-based matter closure criteria

When a matter is nearing closure, OpenText Legal Hold can send status and matter metadata to OpenText Decision Service to determine whether the hold can be released. The decision logic can check for appeal windows, regulatory retention requirements, open sub-matters, or pending discovery requests before authorizing release.

  • Data flow: OpenText Legal Hold to OpenText Decision Service
  • Business value: Reduces the risk of premature hold release
  • Operational benefit: Legal teams can standardize release decisions and improve defensibility

6. Exception handling for conflicting retention and hold obligations

OpenText Decision Service can resolve conflicts when content is subject to both retention policies and legal hold requirements. If OpenText Legal Hold identifies content that would normally be deleted or archived, the decision engine can determine whether the hold overrides the retention action, whether an exception applies, or whether the case should be escalated.

  • Data flow: Bi-directional
  • Business value: Prevents policy conflicts and compliance gaps
  • Operational benefit: Improves coordination between legal, records management, and compliance teams

7. Automated audit and compliance reporting for hold decisions

OpenText Legal Hold can feed decision outcomes, custodian actions, and hold events into OpenText Decision Service to classify cases by risk, jurisdiction, or policy outcome. This supports standardized reporting for audits, internal controls, and regulatory inquiries.

  • Data flow: OpenText Legal Hold to OpenText Decision Service
  • Business value: Stronger auditability and defensible decision records
  • Operational benefit: Compliance teams can produce consistent reports without manual data reconciliation

8. Policy updates without application changes

When legal or compliance policies change, OpenText Decision Service can be updated with new decision rules without modifying OpenText Legal Hold workflows. This is especially useful when hold criteria change due to new regulations, litigation strategy, or corporate policy updates.

  • Data flow: OpenText Decision Service to OpenText Legal Hold
  • Business value: Faster policy implementation and reduced IT dependency
  • Operational benefit: Legal teams can adapt hold logic quickly while maintaining process consistency

How to integrate and automate OpenText Decision Service with OpenText Legal Hold using OneTeg?