Home | Connectors | OpenText Extended ECM - Records Management | OpenText Extended ECM - Records Management - Bluestone PIM Integration and Automation
Data flow: Bluestone PIM ? OpenText Extended ECM - Records Management
When product attributes, pricing references, compliance labels, or regulated content are finalized in Bluestone PIM, the approved version can be declared as a formal record in OpenText Extended ECM - Records Management. This creates an auditable trail for who approved the data, when it was published, and which version was used across channels.
Business value: Supports regulatory evidence, reduces disputes over product data versions, and ensures retention policies are applied to critical product information.
Data flow: Bluestone PIM ? OpenText Extended ECM - Records Management
Final product descriptions, safety statements, technical specifications, and market-specific content can be archived from Bluestone PIM into OpenText as records once they are released. This is especially useful for industries that must prove what product information was published in a specific market at a specific time.
Business value: Enables defensible archiving of published product content, simplifies audits, and helps teams respond to legal or regulatory inquiries faster.
Data flow: Bluestone PIM ? OpenText Extended ECM - Records Management
When a product is discontinued in Bluestone PIM, the associated product record, enriched content, and channel-specific variants can be transferred to OpenText for retention and disposition management. OpenText can then apply retention schedules based on product category, geography, or regulatory requirement.
Business value: Prevents premature deletion of important product history, reduces storage risk, and ensures obsolete product data is retained only as long as required.
Data flow: Bi-directional
Bluestone PIM can store structured product attributes while OpenText manages governed documents such as certificates, declarations of conformity, safety data sheets, and regulatory approvals. Integration can link the product record in Bluestone to the authoritative compliance documents in OpenText, giving product teams a single view of approved content and supporting evidence.
Business value: Improves data governance, reduces manual document chasing, and helps ensure only approved documentation is associated with active products.
Data flow: Bluestone PIM ? OpenText Extended ECM - Records Management
Before product data is published to eCommerce or marketplaces, the final approved dataset can be captured in OpenText as a record after sign-off by product, legal, and compliance teams. This is useful for organizations that need to demonstrate formal approval of product claims, labeling, or regional content variations.
Business value: Creates a clear approval history, reduces compliance risk, and supports internal controls for product publishing.
Data flow: Bluestone PIM ? OpenText Extended ECM - Records Management
For industries such as healthcare, chemicals, food, or financial services, changes to product data may need to be retained for years. Bluestone PIM can pass snapshots of key product changes, including attribute updates and content revisions, into OpenText for long-term retention under defined schedules.
Business value: Preserves historical product evidence, supports investigations and recalls, and reduces the risk of losing critical change history.
Data flow: Bi-directional
During a recall or product investigation, Bluestone PIM can provide the current and historical product data, while OpenText stores the official records of affected product versions, approvals, and supporting documentation. This integration helps compliance, quality, and legal teams quickly assemble a complete evidence package.
Business value: Speeds response to recalls, improves traceability, and strengthens defensibility in legal or regulatory proceedings.
Data flow: Bluestone PIM ? OpenText Extended ECM - Records Management
Different sales channels often require different product descriptions, images, and compliance statements. Once a channel-specific version is approved and published, it can be archived in OpenText with retention rules based on channel, region, or product line. This ensures the organization can prove exactly what content was used in each channel at any point in time.
Business value: Improves channel governance, supports market-specific compliance, and reduces manual effort in tracking published content versions.