OpenText Extended ECM - Business Workspaces - OpenText Core Content - Metadata Integration and Automation

Common Integration Use Cases Between OpenText Extended ECM - Business Workspaces and OpenText Core Content - Metadata

• 1. Synchronize workspace metadata to enforce cloud content classification

  Flow: OpenText Extended ECM - Business Workspaces ? OpenText Core Content - Metadata

  Business workspace attributes such as customer name, project ID, case type, region, and retention category can be pushed into OpenText Core Content to automatically classify related cloud content. This ensures documents stored in Core Content inherit consistent metadata from the business context in Extended ECM.

  Business value: Reduces manual tagging, improves search accuracy, and supports consistent governance across both platforms.

• 2. Enrich business workspaces with governed metadata from Core Content

  Flow: OpenText Core Content - Metadata ? OpenText Extended ECM - Business Workspaces

  Controlled vocabularies, validated metadata values, and classification rules maintained in Core Content can be used to populate or validate fields in Extended ECM workspaces. For example, approved document categories, product codes, or regulatory labels can be reused when users create or update workspace records.

  Business value: Improves data quality, reduces inconsistent entries, and aligns workspace content with enterprise metadata standards.

• 3. Create a unified customer or project record across structured and unstructured content

  Flow: Bi-directional

  When a customer, project, or case is created in Extended ECM, a corresponding metadata profile can be established in Core Content for related files, images, or supporting documents. Updates to key business attributes in either system can be synchronized so both platforms reflect the same operational context.

  Business value: Gives teams a single, reliable view of the business object and its supporting content, improving collaboration and reducing duplicate records.

• 4. Automate document routing based on workspace metadata

  Flow: OpenText Extended ECM - Business Workspaces ? OpenText Core Content - Metadata

  Metadata from a workspace can trigger classification and routing rules in Core Content. For example, a contract workspace marked as high risk or EU regulated can automatically assign the correct metadata set, retention policy, or review queue for documents stored in the cloud repository.

  Business value: Speeds up processing, supports compliance, and reduces the need for manual intervention by content operations teams.

• 5. Improve enterprise search across business context and cloud content

  Flow: Bi-directional

  Workspace metadata from Extended ECM and controlled metadata from Core Content can be shared to support unified search experiences. Users searching for a project, supplier, or claim can retrieve both the workspace and the associated cloud-managed documents using consistent metadata terms.

  Business value: Helps users find the right content faster and reduces time spent searching across disconnected repositories.

• 6. Support records management and retention alignment

  Flow: OpenText Extended ECM - Business Workspaces ? OpenText Core Content - Metadata

  Retention-related metadata such as record type, legal hold status, or disposition category can be passed from business workspaces to Core Content. This allows cloud content to inherit the correct governance rules based on the business process that created or owns the content.

  Business value: Strengthens compliance, reduces retention errors, and ensures content is managed according to business and regulatory requirements.

• 7. Standardize metadata for cross-team reporting and analytics

  Flow: OpenText Core Content - Metadata ? OpenText Extended ECM - Business Workspaces

  Enterprise metadata definitions from Core Content can be used to standardize reporting fields in Extended ECM workspaces. This enables consistent reporting on project status, document types, approval stages, and content volumes across departments such as legal, finance, procurement, and operations.

  Business value: Improves reporting consistency, supports better decision-making, and reduces reconciliation work between teams.