OpenText Decision Service - Ziflow Integration and Automation

Common Integration Use Cases Between OpenText Decision Service and Ziflow

OpenText Decision Service and Ziflow complement each other well in organizations that need controlled, repeatable approval processes for creative and marketing content. OpenText Decision Service provides rule-based decisioning for business policies, while Ziflow manages proofing, review, and approval workflows for creative assets. Together, they can automate routing, enforce governance, and reduce approval delays.

1. Policy-Based Creative Approval Routing

Data flow: OpenText Decision Service to Ziflow

When a new creative asset is submitted for review, OpenText Decision Service evaluates business rules such as brand, region, product line, campaign type, or content sensitivity. Based on the outcome, Ziflow automatically routes the proof to the correct reviewers and approvers.

• Example: A financial services ad is routed to legal, compliance, and brand teams, while a standard social post goes only to marketing approval.
• Business value: Reduces manual triage and ensures the right stakeholders review the right content every time.

2. Compliance Escalation for Regulated Content

Data flow: Ziflow to OpenText Decision Service

When reviewers in Ziflow flag content as regulated, high risk, or requiring special approval, Ziflow sends the proof metadata to OpenText Decision Service. The decision engine applies compliance rules and determines whether additional approvals, legal review, or escalation are required.

• Example: A healthcare campaign mentioning product claims is automatically escalated for regulatory review before final approval.
• Business value: Improves governance and reduces the risk of publishing non-compliant content.

3. Dynamic Reviewer Assignment Based on Content Attributes

Data flow: Bi-directional

Ziflow captures proof details such as asset type, language, market, and campaign owner. OpenText Decision Service uses these attributes to determine reviewer groups, approval thresholds, and required sign-offs, then sends the assignment rules back to Ziflow.

• Example: A multilingual campaign is automatically assigned to local market reviewers and language specialists.
• Business value: Ensures accurate review coverage without relying on manual coordination.

4. Approval Thresholds for High-Impact Campaigns

Data flow: OpenText Decision Service to Ziflow

OpenText Decision Service can classify content by business impact, such as budget size, audience reach, or strategic importance. Ziflow then applies different approval paths based on the decision outcome, including executive approval for high-impact assets.

• Example: A national product launch requires VP marketing approval, while a local event flyer follows a standard review path.
• Business value: Aligns approval rigor with business risk and campaign importance.

5. Automated Rework Routing After Review Feedback

Data flow: Ziflow to OpenText Decision Service

When reviewers request changes in Ziflow, the feedback can be sent to OpenText Decision Service to determine the next workflow step. The decision engine can route the asset back to the original creator, a specialist team, or a secondary reviewer based on the type of revision needed.

• Example: Copy changes go back to the content team, while legal wording changes are routed to compliance for revalidation.
• Business value: Shortens revision cycles and prevents unnecessary back-and-forth.

6. SLA-Based Escalation for Stalled Approvals

Data flow: Bi-directional

Ziflow tracks review status and elapsed time, while OpenText Decision Service applies escalation rules when approvals exceed defined thresholds. If a proof remains pending too long, the system can trigger reminders, reassign reviewers, or escalate to a manager.

• Example: If a campaign proof is untouched for 48 hours, it is escalated to the reviewer?s backup approver.
• Business value: Improves turnaround time and keeps launch schedules on track.

7. Final Approval Gating for Downstream Publishing

Data flow: Ziflow to OpenText Decision Service

Once a proof reaches final approval in Ziflow, the approval event can be sent to OpenText Decision Service to validate whether downstream publishing or asset release is permitted. The decision engine checks business conditions such as required approvals, campaign dates, or market restrictions before authorizing release.

• Example: A retail promotion is only released to the content management system after all required approvals are complete and the launch date is valid.
• Business value: Prevents premature publication and enforces release controls.

8. Exception Handling for Non-Standard Creative Requests

Data flow: Ziflow to OpenText Decision Service

For unusual requests such as urgent launches, off-brand content, or exception-based approvals, Ziflow can send the request details to OpenText Decision Service. The engine evaluates exception rules and determines whether the request can proceed, needs additional approvals, or must be rejected.

• Example: An urgent same-day campaign bypass request is approved only if the request meets predefined business criteria.
• Business value: Provides controlled flexibility while maintaining policy compliance.

These integrations help organizations combine structured decision automation with collaborative creative review, resulting in faster approvals, stronger governance, and more consistent cross-team workflows.