OpenText Extended ECM - Business Workspaces - Bluestone PIM Integration and Automation

Common Integration Use Cases Between OpenText Extended ECM - Business Workspaces and Bluestone PIM

1. Product Launch Workspace for Cross-Functional Collaboration

Data flow: Bluestone PIM ? OpenText Extended ECM - Business Workspaces

When a new product is being prepared for launch, Bluestone PIM can publish the approved product record, attributes, and channel-specific content into an OpenText business workspace tied to the launch initiative. Marketing, legal, product management, and operations teams can then collaborate around the same product context, with supporting documents such as packaging artwork, compliance approvals, and launch checklists stored alongside the product data.

• Reduces launch delays caused by scattered files and email-based approvals
• Gives teams a single workspace for product-related decisions and evidence
• Improves governance by linking content to the approved product master

2. Product Compliance and Regulatory Documentation Management

Data flow: Bluestone PIM ? OpenText Extended ECM - Business Workspaces

Bluestone PIM can provide the authoritative product attributes, classifications, and market-specific variants to OpenText workspaces used for compliance management. Regulatory teams can store certificates, safety data sheets, declarations of conformity, and audit evidence in the workspace associated with each product or product family. This ensures that compliance documentation is managed in the same context as the product data it supports.

• Supports faster audits and regulatory reviews
• Improves traceability between product records and compliance artifacts
• Helps ensure market-specific documentation is complete before product release

3. Product Content Approval and Enrichment Workflow

Data flow: Bi-directional

Product managers can create or update product records in Bluestone PIM, while OpenText business workspaces manage the review and approval of supporting content such as descriptions, technical sheets, images, and translations. Once approved in OpenText, the enriched content can be synchronized back to Bluestone PIM for publication across sales channels.

• Separates content creation from final product publishing
• Creates a controlled approval process for product enrichment
• Improves content quality and consistency across channels

4. Supplier and Vendor Content Intake for Product Mastering

Data flow: OpenText Extended ECM - Business Workspaces ? Bluestone PIM

Supplier-submitted documents such as specification sheets, certificates, images, and product declarations can be captured in OpenText workspaces linked to supplier or sourcing cases. After review, validated product attributes and approved assets can be transferred into Bluestone PIM to enrich the product master. This is especially useful when procurement and merchandising teams need to convert supplier content into publishable product data.

• Improves control over supplier-provided product information
• Reduces manual rekeying of specifications into PIM
• Speeds up onboarding of new products and suppliers

5. Product Change Management and Impact Review

Data flow: Bluestone PIM ? OpenText Extended ECM - Business Workspaces

When a product attribute changes in Bluestone PIM, such as dimensions, ingredients, or regulatory classification, the change can trigger an OpenText workspace for impact assessment. Teams can review affected documents, packaging files, contracts, and customer-facing materials before the update is released to downstream channels. This helps ensure that all related content is updated in sync with the product master.

• Prevents inconsistencies between product data and supporting documents
• Supports controlled change review across departments
• Reduces risk of publishing outdated or conflicting product information

6. Channel-Specific Content Governance and Publication Control

Data flow: Bi-directional

Bluestone PIM can manage the structured product data required for each sales channel, while OpenText workspaces store the governance records, approvals, and supporting evidence needed before publication. For example, a retail channel may require additional legal text or localized documentation before a product can go live. Once the required content is approved in OpenText, Bluestone can receive the final channel-ready product package.

• Ensures each channel receives complete and approved product content
• Supports localized and market-specific publication requirements
• Provides an audit trail for content approval and release decisions

7. Product Obsolescence and Archive Management

Data flow: Bluestone PIM ? OpenText Extended ECM - Business Workspaces

When a product is discontinued in Bluestone PIM, the related workspace in OpenText can be used to retain the final approved product data, historical documents, and retirement approvals. This creates a controlled archive for legal, customer service, and product management teams that need access to legacy product information after the item is removed from active catalogs.

• Preserves historical product records for reference and compliance
• Supports customer service inquiries about discontinued products
• Improves retention and governance of retired product content

8. Product Master and Case Management for Exceptions

Data flow: OpenText Extended ECM - Business Workspaces ? Bluestone PIM

When product data issues are identified during a business case, such as missing attributes, conflicting supplier information, or unresolved quality exceptions, OpenText can manage the case in a dedicated workspace. Once the issue is resolved, the corrected product data can be pushed into Bluestone PIM to update the master record. This is useful for master data teams that need a structured process for handling exceptions before product publication.

• Creates a formal process for resolving product data exceptions
• Improves data quality before records are distributed to channels
• Helps align business decisions with product master updates