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

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

1. Metadata-driven document approval routing

When content is uploaded into OpenText Core Content, required metadata such as document type, business unit, region, and sensitivity level can be validated and then passed to OpenText Decision Service to determine the correct approval path. For example, a contract tagged as ?high risk? and ?EMEA? can be routed to legal and regional compliance reviewers automatically. This reduces manual triage, improves turnaround time, and ensures policy-based routing is applied consistently.

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

2. Automated retention and disposition decisions based on content classification

OpenText Core Content can classify records and managed content using controlled metadata values such as record category, retention class, and regulatory jurisdiction. OpenText Decision Service can then apply business rules to determine retention periods, legal hold eligibility, or disposition actions. This is especially useful for records management teams that need consistent enforcement across large content volumes while adapting quickly to changing regulations.

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

3. Compliance exception handling for sensitive content

Content tagged with sensitive metadata, such as personally identifiable information, export-controlled data, or confidential client material, can trigger decision rules in OpenText Decision Service. The service can decide whether the item requires additional review, encryption, restricted access, or escalation to compliance. This creates a controlled workflow for exception handling and helps reduce the risk of unauthorized access or policy violations.

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

4. Metadata quality validation before workflow execution

Before a document enters a downstream business process, OpenText Decision Service can evaluate whether the metadata captured in OpenText Core Content is complete and valid. If mandatory fields are missing or values do not match approved vocabularies, the item can be rejected, returned for correction, or routed to a data stewardship queue. This improves metadata quality at the source and prevents downstream process failures caused by incomplete classification.

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

5. Dynamic case assignment based on content attributes

In case management scenarios, OpenText Core Content can store structured metadata about incoming files, such as customer segment, claim type, product line, or urgency. OpenText Decision Service can use those attributes to assign the case to the right team, prioritize the workload, or determine whether specialist review is required. This is valuable in claims, customer service, and legal operations where routing accuracy directly affects service levels.

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

6. Policy-based publishing and distribution control

For digital asset or enterprise content publishing, metadata in OpenText Core Content can indicate audience, approval status, market, or usage rights. OpenText Decision Service can then decide whether the content is eligible for publication, which channels it can be distributed to, and whether additional approvals are needed. This helps marketing, communications, and brand governance teams enforce publishing policies without manual review of every asset.

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

7. Rule-driven escalation for content lifecycle events

When metadata indicates a lifecycle event such as contract renewal date, review deadline, or expiring certification, OpenText Decision Service can determine the next action. It may trigger reminders, escalate to a manager, create a task in workflow, or initiate a renewal process. This use case supports proactive operations and reduces the risk of missed deadlines across legal, procurement, HR, and compliance functions.

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