OpenText Core Content - Metadata - Ziflow Integration and Automation

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

1. Metadata-driven creative proof routing

Direction: OpenText Core Content - Metadata ? Ziflow

When a creative asset is uploaded or updated in OpenText Core Content, required metadata such as campaign, region, product line, language, and approval type can automatically determine the correct Ziflow proofing workflow. This ensures the asset is routed to the right reviewers based on governed metadata rather than manual assignment.

Business value: Reduces routing errors, shortens review setup time, and improves compliance with approval policies across marketing and brand teams.

2. Approved proof status updates content metadata

Direction: Ziflow ? OpenText Core Content - Metadata

Once a proof is approved in Ziflow, the approval outcome can be written back to OpenText Core Content as metadata such as approval status, approver name, approval date, version number, and release readiness. This creates a reliable record of the content lifecycle inside the governed content repository.

Business value: Provides auditability, supports downstream publishing decisions, and gives content managers a single source of truth for approved assets.

3. Metadata-based reviewer assignment and escalation

Direction: OpenText Core Content - Metadata ? Ziflow

Controlled metadata values can be used to assign reviewers automatically in Ziflow. For example, assets tagged as regulated content can be sent to legal and compliance reviewers, while region-specific content can be routed to local market approvers. Escalation rules can also be driven by metadata such as priority or launch date.

Business value: Improves governance, ensures the right stakeholders review the right content, and reduces delays caused by manual coordination.

4. Proof comments and decision history stored as content metadata

Direction: Ziflow ? OpenText Core Content - Metadata

Key proofing details from Ziflow, including review comments, decision status, number of revision cycles, and final approval notes, can be captured in OpenText Core Content metadata. This preserves the full review history alongside the managed asset for future reference and compliance needs.

Business value: Strengthens traceability, supports audits, and helps teams understand why a specific version was approved.

5. Metadata validation before proof creation

Direction: OpenText Core Content - Metadata ? Ziflow

Before a file is sent to Ziflow for proofing, OpenText Core Content can enforce required metadata fields and controlled vocabularies. Only assets with complete and valid metadata are allowed into the review process, preventing incomplete submissions and reducing rework.

Business value: Improves content quality, avoids review delays, and ensures downstream workflows start with accurate information.

6. Approved asset promotion to downstream content repositories

Direction: Ziflow ? OpenText Core Content - Metadata

After final approval in Ziflow, the approved version can be promoted in OpenText Core Content with updated metadata indicating final status, usage rights, and publication category. This can trigger downstream distribution or publishing workflows only when approval is complete.

Business value: Prevents premature publishing, supports controlled release processes, and reduces the risk of using unapproved content.

7. Campaign reporting across content and approval lifecycle

Direction: Bi-directional

Metadata from OpenText Core Content and proofing data from Ziflow can be combined to create end-to-end reporting on campaign throughput, approval cycle times, revision counts, and bottlenecks by content type or region. This gives marketing operations and content governance teams a complete view of content performance.

Business value: Enables better planning, identifies process inefficiencies, and supports continuous improvement in creative operations.