OpenText Lens - Data Visibility - OpenText Developer Admin - IM Developer Administration Integration and Automation

Common Integration Use Cases Between OpenText Lens - Data Visibility and OpenText Developer Admin - IM Developer Administration

1. Sensitive Data Discovery to Integration Environment Segmentation

OpenText Lens - Data Visibility can identify repositories containing regulated, confidential, or business-critical unstructured data, then pass findings to OpenText Developer Admin - IM Developer Administration so integration teams can segment development, test, and production environments accordingly. This helps prevent sensitive content from being exposed in non-production integration artifacts, test payloads, or developer sandboxes.

• Data flow: OpenText Lens - Data Visibility to OpenText Developer Admin - IM Developer Administration
• Business value: Reduces compliance risk and limits accidental exposure of sensitive content during integration development

2. Data Cleanup Prior to API and Messaging Migration

Before migrating integration services, OpenText Lens - Data Visibility can identify obsolete, duplicate, or low-value unstructured content that may be referenced by legacy interfaces. OpenText Developer Admin - IM Developer Administration can then be used to update integration configurations, credentials, and messaging artifacts to align with the cleaned data landscape. This supports smoother migration planning and reduces the chance of moving unnecessary data dependencies.

• Data flow: OpenText Lens - Data Visibility to OpenText Developer Admin - IM Developer Administration
• Business value: Lowers migration complexity and reduces technical debt in integration environments

3. Governance-Driven Control of Developer Access to Sensitive Repositories

OpenText Lens - Data Visibility can classify repositories based on sensitivity and business risk, and those classifications can be used by OpenText Developer Admin - IM Developer Administration to guide which developers, service accounts, or integration projects are allowed to connect to specific sources. This creates a practical control layer for integration teams working with Trading Grid solutions and other messaging platforms.

• Data flow: OpenText Lens - Data Visibility to OpenText Developer Admin - IM Developer Administration
• Business value: Improves access governance and supports least-privilege integration design

4. Automated Identification of Integration Dependencies on Unstructured Content

OpenText Lens - Data Visibility can detect where unstructured content is stored and which repositories are likely to be impacted by integration changes. OpenText Developer Admin - IM Developer Administration can use that information to update integration artifacts, endpoint mappings, and environment configurations when source systems or content locations change. This is especially useful when teams need to maintain stable messaging flows while content repositories are reorganized.

• Data flow: OpenText Lens - Data Visibility to OpenText Developer Admin - IM Developer Administration
• Business value: Reduces integration breakage and shortens change implementation cycles

5. Compliance Evidence for Integration Development and Release Audits

OpenText Lens - Data Visibility can provide evidence of what sensitive data exists, where it resides, and how it is being managed. OpenText Developer Admin - IM Developer Administration can complement this by maintaining records of integration configurations, credentials, and environment separation. Together, they support audit readiness by showing that integration development practices are aligned with data governance requirements.

• Data flow: Bi-directional
• Business value: Strengthens auditability and simplifies compliance reporting

6. Targeted Data Remediation for Integration Test Data Management

OpenText Lens - Data Visibility can identify repositories containing production-like unstructured data that should not be used in test environments. OpenText Developer Admin - IM Developer Administration can then be used to adjust integration setup so test systems point to approved, sanitized, or synthetic data sources. This helps integration teams avoid using live sensitive content in development and QA workflows.

• Data flow: OpenText Lens - Data Visibility to OpenText Developer Admin - IM Developer Administration
• Business value: Improves test data governance and reduces privacy exposure

7. Repository Risk Scoring to Prioritize Integration Hardening

OpenText Lens - Data Visibility can assign risk indicators to repositories based on content type, age, duplication, and sensitivity. OpenText Developer Admin - IM Developer Administration can use those risk indicators to prioritize which integration endpoints, credentials, and messaging routes should be hardened first. This allows integration teams to focus effort on the highest-risk connections instead of treating all interfaces equally.

• Data flow: OpenText Lens - Data Visibility to OpenText Developer Admin - IM Developer Administration
• Business value: Improves security prioritization and operational efficiency

8. Change Impact Analysis for Integration and Content Governance Teams

When OpenText Lens - Data Visibility detects repository changes such as new sensitive content, content sprawl, or obsolete data, OpenText Developer Admin - IM Developer Administration can help integration teams assess whether existing APIs, credentials, or messaging configurations need to be updated. This creates a shared workflow between governance and integration teams to manage change proactively rather than reactively.

• Data flow: Bi-directional
• Business value: Improves cross-team coordination and reduces operational disruption