Home | Connectors | OpenText Extended ECM - Business Workspaces | OpenText Extended ECM - Business Workspaces - CELUM Integration and Automation

OpenText Extended ECM - Business Workspaces - CELUM Integration and Automation

Integrate OpenText Extended ECM - Business Workspaces Document Management and CELUM Digital Asset Management (DAM) apps with any of the apps from the library with just a few clicks. Create automated workflows by integrating your apps.

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

1. Campaign Asset Delivery into Project or Product Workspaces

Data flow: CELUM ? OpenText Extended ECM - Business Workspaces

Marketing teams manage approved campaign assets in CELUM, then automatically publish final versions into the relevant OpenText business workspace for a product launch, customer initiative, or project. This gives sales, product, and operations teams direct access to the latest brand-approved materials within the business context they already use.

  • Approved brochures, banners, videos, and presentation decks are synced from CELUM to the workspace
  • Workspace users see only the current, governed version of each asset
  • Launch teams avoid searching across multiple repositories for final content

Business value: Faster campaign execution, fewer version errors, and better alignment between marketing and operational teams.

2. Contract or Proposal Attachments with Brand-Controlled Marketing Content

Data flow: Bi-directional

Sales or account teams working in OpenText business workspaces can attach approved marketing assets from CELUM to proposals, customer presentations, or account packages. In return, usage feedback or document references can be written back to CELUM to support asset governance and reuse tracking.

  • Sales teams pull approved product sheets, case studies, and pitch decks from CELUM
  • OpenText stores the assembled customer-specific package in the relevant account workspace
  • CELUM receives metadata about where and how assets were used

Business value: Improves proposal quality, ensures brand compliance, and reduces time spent assembling customer-facing materials.

3. Customer or Partner Portal Content Governance

Data flow: CELUM ? OpenText Extended ECM - Business Workspaces

Organizations that manage customer or partner-facing content can use CELUM as the source of approved digital assets and OpenText as the governed workspace tied to the customer or partner record. This ensures that only sanctioned content is shared in external-facing business processes.

  • Localized product images, datasheets, and training materials are approved in CELUM
  • OpenText business workspaces store the content linked to the customer, distributor, or partner record
  • Teams can trace which assets were shared with which business entity

Business value: Better control over external content distribution, improved auditability, and reduced compliance risk.

4. Product Launch Workspace with Centralized Asset and Document Management

Data flow: Bi-directional

For product launches, CELUM manages creative assets while OpenText business workspaces manage launch plans, approvals, specifications, and cross-functional documents. Integrating the two creates a single launch context where marketing, product, legal, and operations can collaborate without duplicating content.

  • Creative files, packaging visuals, and campaign media are stored in CELUM
  • Launch checklists, approvals, and business documents remain in OpenText
  • Both systems reference the same launch identifier or product code

Business value: Reduces launch delays, improves cross-team coordination, and creates a complete record of launch-related content.

5. Rights-Managed Asset Access in Business Workspaces

Data flow: CELUM ? OpenText Extended ECM - Business Workspaces

CELUM often contains assets with usage rights, expiration dates, and regional restrictions. By syncing these assets and their rights metadata into OpenText workspaces, business users can access only the content they are allowed to use for a specific customer, region, or campaign.

  • Rights metadata from CELUM is carried into the workspace
  • Expired or restricted assets can be hidden or flagged automatically
  • Teams working on regulated or regional campaigns stay within approved boundaries

Business value: Prevents unauthorized asset use, supports regional governance, and reduces legal exposure.

6. Content Approval Handover from Business Review to Marketing Distribution

Data flow: OpenText Extended ECM - Business Workspaces ? CELUM

Business stakeholders may review and approve content in OpenText as part of a project, case, or customer initiative. Once approved, final assets can be handed over to CELUM for broader distribution, localization, and multichannel publishing.

  • Legal, compliance, or product teams approve content in the workspace
  • Final approved files are transferred to CELUM as publish-ready assets
  • CELUM manages downstream distribution to web, social, and partner channels

Business value: Separates business approval from marketing distribution while maintaining a controlled handoff process.

7. Audit Trail for Asset Usage in Customer and Project Contexts

Data flow: Bi-directional

When assets from CELUM are used in OpenText-managed business workspaces, the integration can capture usage metadata such as asset ID, version, approval status, and associated business object. This creates a traceable record of which approved content was used in which customer, project, or case context.

  • OpenText stores references to the exact CELUM asset version used
  • CELUM receives usage data for reporting and lifecycle management
  • Audit teams can trace content lineage across both platforms

Business value: Stronger governance, easier audits, and better visibility into content reuse across the enterprise.

8. Localization Workflow for Global Campaigns and Regional Workspaces

Data flow: CELUM ? OpenText Extended ECM - Business Workspaces

Global marketing teams can manage master assets in CELUM and distribute localized variants to regional business workspaces in OpenText. Regional teams then work with the correct language, market, or regulatory version tied to their local business process.

  • Master creative assets are maintained centrally in CELUM
  • Localized versions are published to regional workspaces in OpenText
  • Regional teams collaborate on market-specific execution without altering master content

Business value: Speeds localization, improves consistency across markets, and reduces duplication of asset management effort.

How to integrate and automate OpenText Extended ECM - Business Workspaces with CELUM using OneTeg?