OpenText Core Content - Metadata - OpenText Exstream Integration and Automation

Common Integration Use Cases Between OpenText Core Content - Metadata and OpenText Exstream

1. Metadata-driven document assembly for customer communications

Flow: OpenText Core Content - Metadata ? OpenText Exstream

Use governed metadata from OpenText Core Content - Metadata to drive document selection, personalization, and assembly in OpenText Exstream. For example, customer segment, product type, jurisdiction, language, and communication preference can be passed into Exstream to generate the correct statement, policy, bill, or notice.

Business value: Reduces manual template selection, improves accuracy, and ensures the right version of a communication is produced for each customer and regulatory context.

2. Controlled vocabulary synchronization for communication categories

Flow: Bi-directional

Synchronize approved metadata values such as document type, channel, region, brand, and compliance category between the two platforms. OpenText Core Content - Metadata can act as the system of record for controlled vocabularies, while OpenText Exstream uses those values to classify and route communication assets.

Business value: Creates consistent naming and classification across content and communications teams, reducing errors in reporting, search, and downstream automation.

3. Compliance-approved content reuse in customer communications

Flow: OpenText Core Content - Metadata ? OpenText Exstream

Store approved legal disclaimers, product descriptions, policy language, and regulatory statements in OpenText Core Content - Metadata with strict metadata tags such as effective date, jurisdiction, and approval status. Exstream can retrieve only the approved content fragments that match the communication context.

Business value: Improves compliance control, supports auditability, and reduces the risk of using outdated or unapproved language in customer-facing output.

4. Communication output archiving with rich metadata

Flow: OpenText Exstream ? OpenText Core Content - Metadata

After Exstream generates a statement, letter, policy packet, or notice, the final output can be archived in OpenText Core Content - Metadata with metadata such as customer ID, communication type, delivery channel, version, and send date.

Business value: Provides a searchable record of what was sent, supports customer service inquiries, and simplifies retention and audit processes.

5. Automated routing of communication exceptions for review

Flow: OpenText Exstream ? OpenText Core Content - Metadata

When Exstream encounters missing data, invalid values, or a template exception, it can send the exception package to OpenText Core Content - Metadata for classification and workflow routing. Metadata can identify the issue type, business owner, and priority for resolution.

Business value: Shortens exception handling cycles, improves operational visibility, and helps business teams resolve communication issues faster.

6. Personalized omnichannel communication governance

Flow: OpenText Core Content - Metadata ? OpenText Exstream

Use metadata to govern which communication channel is allowed for each customer or document type, such as print only, email eligible, or digital preferred. Exstream can use these rules to generate the appropriate output format and channel-specific version.

Business value: Supports customer preference management, reduces channel compliance risk, and improves delivery efficiency across print and digital channels.

7. Reporting and analytics on communication production and content usage

Flow: Bi-directional

Combine Exstream production data with metadata from OpenText Core Content - Metadata to create operational reports on communication volumes, template usage, approval status, regional distribution, and content reuse. This enables business teams to analyze which approved content is used most often and where communication exceptions occur.

Business value: Improves visibility into communication operations, supports governance reporting, and helps optimize templates and content libraries.