inriver - OpenText Lens - Data Visibility Integration and Automation

Common Integration Use Cases Between inriver and OpenText Lens - Data Visibility

inriver and OpenText Lens - Data Visibility complement each other by connecting product information management with unstructured content discovery and governance. inriver manages structured product data, enrichment, and syndication, while OpenText Lens helps teams identify, classify, and clean up supporting unstructured content such as product manuals, images, compliance documents, technical sheets, and legacy marketing assets. Together, they improve product data quality, reduce content risk, and streamline cross-functional workflows.

1. Identify and govern unstructured product content before onboarding into inriver

Flow: OpenText Lens - Data Visibility to inriver

Use OpenText Lens to scan shared drives, file repositories, and content archives for product-related documents such as spec sheets, installation guides, safety data sheets, and marketing collateral. The business can then identify which files are current, duplicate, obsolete, or sensitive before they are linked to product records in inriver.

• Reduces the risk of publishing outdated or non-compliant product content
• Speeds up content onboarding by surfacing the best source files
• Supports product marketing, compliance, and legal teams in approving assets

2. Enrich product records with approved supporting documents

Flow: OpenText Lens - Data Visibility to inriver

After OpenText Lens classifies and validates unstructured content, approved documents can be passed to inriver as linked assets for specific products, variants, or product families. This is especially useful for regulated industries where product pages must include manuals, certificates, declarations, or safety information.

• Ensures each product record has the correct supporting documentation
• Improves customer self-service and reduces support inquiries
• Helps maintain consistent documentation across markets and channels

3. Detect obsolete product collateral during catalog refresh cycles

Flow: OpenText Lens - Data Visibility to inriver

When product lines are updated, OpenText Lens can identify outdated brochures, legacy images, superseded technical documents, and duplicate files across repositories. Those findings can be used to trigger cleanup actions in inriver, such as removing obsolete assets from product records or flagging records for review before a new catalog release.

• Prevents outdated collateral from being published to e-commerce or partner portals
• Improves catalog accuracy during seasonal or annual refreshes
• Reduces manual review effort for product content teams

4. Support compliance review for regulated product information

Flow: OpenText Lens - Data Visibility to inriver

OpenText Lens can scan unstructured repositories for sensitive or regulated content such as safety instructions, certifications, restricted-use statements, or region-specific legal documents. The compliance team can then confirm which assets are approved for use in inriver and which must be excluded or replaced before publication.

• Strengthens governance for regulated product categories
• Helps ensure market-specific content is used correctly
• Reduces exposure to legal and compliance issues

5. Improve migration planning for product content modernization

Flow: OpenText Lens - Data Visibility to inriver

During a PIM implementation or content modernization program, OpenText Lens can inventory unstructured repositories to show what product-related content exists, where it is stored, and how much of it is redundant or obsolete. This gives the inriver implementation team a clear migration scope and helps prioritize which assets should be loaded, archived, or retired.

• Reduces migration risk and content sprawl
• Helps define a clean content baseline for inriver
• Supports phased migration by product line, region, or business unit

6. Link product hierarchy changes to content cleanup actions

Flow: Bi-directional

When product hierarchies, variants, or relationships change in inriver, those changes can be used to prompt OpenText Lens scans for related unstructured content. For example, if a product is discontinued or merged into a new family, Lens can locate documents tied to the old product name or code so they can be reviewed and retired.

• Keeps supporting content aligned with current product structures
• Prevents orphaned documents from remaining in circulation
• Improves governance across product lifecycle changes

7. Accelerate localization by finding reusable regional content

Flow: OpenText Lens - Data Visibility to inriver

For global product launches, OpenText Lens can identify existing localized documents, translated manuals, and region-specific marketing assets across repositories. Those assets can then be linked to the correct localized product records in inriver, reducing duplicate translation work and improving time to market.

• Reuses approved local content instead of recreating it
• Supports faster launch readiness in new markets
• Improves consistency across regional product pages and catalogs

Together, inriver and OpenText Lens - Data Visibility create a stronger product content governance process by combining structured product master data with visibility into the unstructured files that support it. This helps organizations publish accurate product information, reduce content risk, and operate more efficiently across marketing, compliance, and product operations teams.