OpenText Lens - Data Visibility - OpenText Decision Service Integration and Automation

Common Integration Use Cases Between OpenText Lens - Data Visibility and OpenText Decision Service

OpenText Lens - Data Visibility and OpenText Decision Service complement each other well in governance, compliance, and operational decisioning. Lens identifies and classifies unstructured content across repositories, while Decision Service applies consistent business rules to determine what action should be taken based on that information. Together, they help organizations move from data discovery to automated, policy-driven action.

1. Automated Sensitive Content Triage and Remediation

Data flow: OpenText Lens - Data Visibility to OpenText Decision Service

Lens scans file shares, content repositories, and collaboration platforms to identify sensitive content such as PII, financial records, or confidential contracts. The findings are passed to Decision Service, which applies business rules to determine the correct remediation path, such as quarantine, encryption, legal review, or deletion.

• Reduces manual review effort for large content inventories
• Ensures consistent handling of sensitive data across repositories
• Supports privacy and records management programs

2. Policy-Based Data Retention and Disposition Decisions

Data flow: OpenText Lens - Data Visibility to OpenText Decision Service

Lens identifies obsolete, duplicate, or inactive content and provides metadata to Decision Service. Decision rules then determine whether content should be retained, archived, reviewed, or disposed of based on content type, age, ownership, and regulatory requirements.

• Improves retention compliance
• Reduces storage costs by eliminating unnecessary content
• Creates a repeatable disposition process for governance teams

3. Migration Readiness and Content Routing

Data flow: OpenText Lens - Data Visibility to OpenText Decision Service

Before a migration to a new platform, Lens analyzes source repositories to identify content categories, risk levels, and business relevance. Decision Service uses this information to route content into migration paths such as migrate, archive, exclude, or escalate for review.

• Improves migration quality and reduces unnecessary data movement
• Helps project teams prioritize high-value content
• Minimizes risk during cloud or platform modernization programs

4. Legal Hold and eDiscovery Escalation

Data flow: OpenText Lens - Data Visibility to OpenText Decision Service

When Lens detects content that matches legal hold criteria, such as case-related terms, custodians, or sensitive document types, it sends the metadata to Decision Service. Decision rules determine whether the content should be preserved, flagged for legal review, or excluded from automated cleanup.

• Reduces the risk of accidental deletion
• Supports defensible legal hold processes
• Improves coordination between legal, compliance, and IT teams

5. Risk-Based Access Review Prioritization

Data flow: OpenText Lens - Data Visibility to OpenText Decision Service

Lens identifies repositories containing highly sensitive or broadly exposed content. Decision Service applies rules to prioritize access reviews based on sensitivity, business unit, geography, and content age, helping security teams focus on the highest-risk areas first.

• Improves the efficiency of access certification campaigns
• Helps security teams focus on the most critical repositories
• Supports least-privilege and data minimization initiatives

6. Automated Records Classification and Review Routing

Data flow: OpenText Lens - Data Visibility to OpenText Decision Service

Lens detects document types and content patterns that indicate records, contracts, HR files, or regulated correspondence. Decision Service then applies rules to classify the item, assign a retention category, or route it to the appropriate records manager or business owner for approval.

• Improves consistency in records classification
• Reduces dependence on manual tagging
• Speeds up governance workflows across departments

7. Exception Management for High-Risk Content

Data flow: Bi-directional

Lens identifies content that falls outside standard policy, such as unusually large files, unowned content, or documents with conflicting classifications. Decision Service evaluates the exception against business rules and can trigger workflow actions such as manager approval, compliance review, or temporary restriction.

• Creates a controlled process for policy exceptions
• Improves auditability of governance decisions
• Helps organizations manage edge cases without slowing operations

These integration patterns are especially valuable in information governance, privacy compliance, migration programs, and risk management initiatives where organizations need both visibility into unstructured data and automated, policy-driven decisions about what to do next.