Home | Connectors | Threekit | Threekit - OpenText Extended ECM - Records Management Integration and Automation
Threekit and OpenText Extended ECM - Records Management complement each other by connecting rich product visualization and configuration experiences with governed content, retention, and compliance controls. Threekit supports customer-facing product experiences and configuration data, while OpenText Extended ECM - Records Management ensures that business records, approvals, and supporting documentation are formally managed, retained, and disposed of according to policy.
Data flow: Threekit to OpenText Extended ECM - Records Management
When a product model, render, or configuration template is approved for launch, Threekit can publish the final visual assets and supporting metadata into OpenText Extended ECM - Records Management as official records. This gives legal, compliance, and product teams a governed archive of the exact assets used in market-facing campaigns and commerce experiences.
Data flow: Threekit to OpenText Extended ECM - Records Management
For regulated industries such as healthcare, automotive, or financial services, product configuration choices may need to be retained as proof of what a customer selected and what was offered at the time of sale. Threekit can pass finalized configuration snapshots, pricing references, and customer-selected options into OpenText Extended ECM - Records Management for formal recordkeeping.
Data flow: Bi-directional
For complex configurable products, Threekit can provide the final visual configuration and option set, while OpenText Extended ECM - Records Management can store the signed order documents, approvals, and related correspondence. Together, they create a complete evidence package for each custom order.
Data flow: OpenText Extended ECM - Records Management to Threekit
OpenText Extended ECM - Records Management can act as the system of record for launch approvals, policy sign-off, and compliance review. Once a product, campaign, or visual asset set is approved, the release status can be sent to Threekit so only authorized assets and configurations are exposed on the commerce site.
Data flow: Threekit to OpenText Extended ECM - Records Management
When customers configure high-value or custom products, Threekit can generate a visual proof of the final selection and send it to OpenText Extended ECM - Records Management as a retained record. This is especially useful when customers later question color, finish, dimensions, or accessory choices.
Data flow: OpenText Extended ECM - Records Management to Threekit
OpenText Extended ECM - Records Management can manage controlled documents such as product disclosures, warranty terms, safety notices, and technical specifications. Threekit can then reference the approved version of these documents within the visual commerce experience, ensuring customers see the correct supporting information for the configured product.
Data flow: Threekit to OpenText Extended ECM - Records Management
When a product is discontinued, Threekit content such as 3D models, render libraries, and configuration rules can be transferred to OpenText Extended ECM - Records Management for retention or disposition based on policy. This prevents obsolete assets from remaining active in commerce systems while preserving required records for legal and historical purposes.
Data flow: Bi-directional
Threekit and OpenText Extended ECM - Records Management can work together to provide a complete audit trail across product setup, customer configuration, approvals, and published content. Operations, compliance, and customer service teams can quickly retrieve both the visual configuration history and the associated governed records.