OpenText Core Case - Ziflow Integration and Automation

Common Integration Use Cases Between OpenText Core Case and Ziflow

1. Creative asset review tied to a formal case record

Data flow: OpenText Core Case ? Ziflow ? OpenText Core Case

When a customer complaint, compliance issue, or service request requires a revised brochure, email template, or public-facing asset, OpenText Core Case can create the case and send the creative file or brief to Ziflow for review. Review comments, approval status, and final sign-off are then written back to the case record. This gives case managers a complete audit trail of what was reviewed, who approved it, and when the asset was released.

Business value: Reduces manual follow-up, improves accountability, and keeps creative approvals aligned with the underlying business case.

2. Compliance review of regulated marketing content

Data flow: OpenText Core Case ? Ziflow ? OpenText Core Case

For regulated industries such as financial services, healthcare, or insurance, OpenText Core Case can manage the compliance case while Ziflow handles the proofing cycle for ads, disclosures, policy documents, or customer communications. Compliance reviewers annotate the proof in Ziflow, and the final approval decision is captured back in OpenText Core Case as evidence of review and control.

Business value: Strengthens governance, supports audit readiness, and shortens approval cycles for regulated content.

3. Customer issue resolution with branded response materials

Data flow: OpenText Core Case ? Ziflow ? OpenText Core Case

When a customer support or escalation case requires a custom response document, apology letter, or service recovery asset, OpenText Core Case can trigger a Ziflow proof for the drafted material. Support, legal, and brand teams can review the response in Ziflow before it is sent to the customer. Once approved, the final version and approval history are attached to the case.

Business value: Ensures consistent customer communications and reduces the risk of sending unapproved or off-brand responses.

4. Campaign exception handling and escalation workflow

Data flow: Ziflow ? OpenText Core Case

If a creative proof in Ziflow is rejected due to legal, brand, or policy concerns, the rejection can automatically create or update a case in OpenText Core Case. The case can route the issue to the appropriate team, such as legal review, brand governance, or product marketing, with the proof comments and version history included as supporting evidence.

Business value: Converts review exceptions into trackable business cases and prevents issues from being lost in email threads.

5. Centralized approval evidence for audit and governance

Data flow: Ziflow ? OpenText Core Case

Ziflow approval metadata, reviewer comments, timestamps, and version history can be synchronized into OpenText Core Case as part of a compliance or governance case. This is useful when organizations need to demonstrate that a specific asset was reviewed by the right stakeholders before publication or distribution.

Business value: Creates a single source of truth for approval evidence and simplifies internal or external audits.

6. Cross-functional review of high-risk communications

Data flow: OpenText Core Case ? Ziflow ? OpenText Core Case

For high-risk communications such as recall notices, policy changes, legal notices, or crisis statements, OpenText Core Case can initiate the case and assign the proof to Ziflow for structured review by legal, compliance, communications, and executive stakeholders. Final approval status and reviewer sign-off are then returned to the case for controlled release.

Business value: Improves coordination across departments and reduces the chance of publishing sensitive content without full approval.

7. Case-driven creative production for service operations

Data flow: OpenText Core Case ? Ziflow

In organizations that produce customer-specific or operational content, OpenText Core Case can trigger Ziflow when a case requires a new visual, form, or document update. For example, a claims case may require a personalized settlement letter or a field service case may require a revised instruction sheet. The creative team receives the case context directly in Ziflow, reducing back-and-forth and helping them review against the correct business requirements.

Business value: Speeds production, reduces rework, and improves alignment between operational teams and creative teams.