OpenText Lens - Data Visibility - Phrase Strings Integration and Automation

Common Integration Use Cases Between OpenText Lens - Data Visibility and Phrase Strings

• Translation content inventory and cleanup before localization
  OpenText Lens - Data Visibility scans shared drives, repositories, and collaboration platforms to identify all source content that may feed Phrase Strings projects, including outdated drafts, duplicate files, and obsolete documentation. Localization teams use the findings to remove non-current assets before importing content into Phrase Strings, reducing translation waste and improving source quality.
• Sensitive content detection before sending text to external translators
  OpenText Lens - Data Visibility flags documents containing personal data, confidential product information, or regulated content. Only approved and sanitized text is then routed into Phrase Strings for translation, helping legal, security, and localization teams enforce data handling policies and reduce compliance risk.
• Migration readiness for content moving into Phrase Strings workflows
  When organizations centralize translation assets into Phrase Strings, OpenText Lens - Data Visibility identifies where source strings, style guides, and reference materials currently reside across file shares and content repositories. This supports migration planning by revealing redundant sources, missing owners, and content that should be archived instead of migrated.
• Governance of translation source files and reference assets
  OpenText Lens - Data Visibility continuously monitors repositories for source documents, terminology lists, and reference materials used by Phrase Strings. If outdated or conflicting versions are detected, governance teams can trigger review and replacement so translators work from approved content only, improving consistency and reducing rework.
• Retention and deletion coordination for localized content
  OpenText Lens - Data Visibility helps identify obsolete source materials and related translation inputs that no longer need to be retained. Those records can then be removed or archived in line with policy, while Phrase Strings retains only active localization assets, lowering storage costs and simplifying records management.
• Audit support for regulated localization programs
  For industries such as healthcare, financial services, and public sector, OpenText Lens - Data Visibility provides evidence of where regulated content exists and how it is classified before it enters Phrase Strings. This creates a defensible audit trail for compliance teams and helps localization managers prove that only approved content was translated.
• Cross-team content triage for product launches and updates
  Before a product release, OpenText Lens - Data Visibility scans engineering, marketing, and support repositories to locate all content that must be localized. The prioritized inventory is then handed to Phrase Strings so product, localization, and regional teams can coordinate translation work based on business impact and release timing.