OpenText Content Metadata Service - Dictionary - OpenText Decision Service Integration and Automation

Common Integration Use Cases Between OpenText Content Metadata Service - Dictionary and OpenText Decision Service

OpenText Content Metadata Service - Dictionary provides the governed metadata foundation for content classification, while OpenText Decision Service applies business rules to make consistent, automated decisions. Together, they help organizations standardize content attributes and use those attributes to drive policy-based actions across content, workflow, and case management processes.

• Automated content classification and routing

  When new documents are ingested into OpenText content repositories, OpenText Content Metadata Service - Dictionary supplies the approved metadata fields and controlled values, such as document type, business unit, sensitivity, and retention category. OpenText Decision Service then evaluates those metadata values to route the content to the correct workflow, reviewer, or repository. This reduces manual triage, improves turnaround time, and ensures content is handled according to business policy.

  Data flow: OpenText Content Metadata Service - Dictionary to OpenText Decision Service

• Policy based retention and disposition decisions

  Organizations can use standardized metadata such as record class, jurisdiction, contract type, and expiration date to trigger retention or disposition rules. OpenText Decision Service evaluates these metadata attributes and determines whether content should be retained, archived, placed on legal hold, or scheduled for deletion. This supports compliance teams by making retention decisions consistent and auditable across repositories.

  Data flow: OpenText Content Metadata Service - Dictionary to OpenText Decision Service

• Sensitive content handling and access control decisions

  Metadata definitions can include confidentiality level, privacy category, and regulated data indicators. OpenText Decision Service uses those standardized values to decide whether content requires encryption, restricted access, additional approval, or special handling before distribution. This is especially useful for legal, HR, finance, and customer data workflows where access decisions must be consistent and policy driven.

  Data flow: OpenText Content Metadata Service - Dictionary to OpenText Decision Service

• Metadata driven approval workflows for publishing

  In publishing, marketing, and product documentation processes, content often requires approval based on metadata such as region, brand, language, or content owner. OpenText Content Metadata Service - Dictionary ensures those fields are standardized across teams, while OpenText Decision Service determines the approval path, required reviewers, or whether content can be published automatically. This improves governance without slowing down content delivery.

  Data flow: OpenText Content Metadata Service - Dictionary to OpenText Decision Service

• Exception handling for incomplete or invalid metadata

  OpenText Content Metadata Service - Dictionary defines the required metadata structure and valid values. If incoming content is missing mandatory fields or contains invalid classifications, OpenText Decision Service can trigger exception workflows, reject the submission, or send it back for correction. This prevents poor quality metadata from entering downstream systems and improves search, reporting, and automation accuracy.

  Data flow: OpenText Content Metadata Service - Dictionary to OpenText Decision Service

• Case prioritization based on content attributes

  In case management environments, cases often include supporting documents whose metadata can influence urgency and handling. OpenText Content Metadata Service - Dictionary provides consistent attributes such as case type, customer segment, regulatory impact, and SLA class. OpenText Decision Service uses those attributes to prioritize cases, assign service levels, or escalate high risk items to specialized teams. This helps operations teams focus on the most critical work first.

  Data flow: OpenText Content Metadata Service - Dictionary to OpenText Decision Service

• Cross repository governance and standardized decisioning

  Enterprises with multiple content repositories often struggle with inconsistent metadata and different local rules. OpenText Content Metadata Service - Dictionary establishes a shared metadata model across repositories, and OpenText Decision Service applies the same decision logic regardless of source system. This creates consistent governance for content lifecycle, compliance, and workflow decisions across business units and platforms.

  Data flow: Bi directional, with OpenText Content Metadata Service - Dictionary providing governed metadata definitions and OpenText Decision Service applying decision rules across systems