Consonance - OpenText Workflow Service Integration and Automation

Common Integration Use Cases Between Consonance and OpenText Workflow Service

1. Manuscript Intake and Editorial Approval Routing

Data flow: Consonance → OpenText Workflow Service → Consonance

When a manuscript is submitted or reaches a key editorial milestone in Consonance, the record can be sent to OpenText Workflow Service to route approvals, assign reviewers, and manage editorial sign-off tasks. OpenText can orchestrate human review steps across acquisitions, editorial, legal, and production teams, then return approval status to Consonance to advance the title to the next stage.

• Reduces manual follow-up on manuscript approvals
• Creates a clear audit trail for editorial decisions
• Ensures titles only move forward when required stakeholders approve

2. Rights and Permissions Review Workflow

Data flow: Consonance → OpenText Workflow Service → Consonance

Consonance manages rights metadata for titles, while OpenText Workflow Service can automate the review and approval process for subsidiary rights, permissions, and contract exceptions. When a rights-related record is updated in Consonance, OpenText can trigger tasks for legal, rights, and business affairs teams to validate terms, approve usage, or escalate exceptions before publication or licensing.

• Improves control over rights-sensitive content
• Speeds up approvals for permissions and licensing requests
• Reduces compliance risk by enforcing review checkpoints

3. Production Readiness and Release Gatekeeping

Data flow: Consonance → OpenText Workflow Service → Consonance

As a title approaches production, Consonance can send milestone data to OpenText Workflow Service to coordinate readiness checks across editorial, design, production, and metadata teams. OpenText can manage a release gate workflow that confirms all required assets, metadata, ISBNs, and format deliverables are complete before the title is marked ready for print, digital, or audio release in Consonance.

• Prevents premature release of incomplete titles
• Improves cross-functional accountability
• Helps standardize go-live criteria across imprints and formats

4. Exception Management for Missing or Incomplete Metadata

Data flow: Consonance → OpenText Workflow Service → Consonance

If Consonance detects missing metadata such as contributor details, BISAC codes, pricing, or format-specific information, OpenText Workflow Service can create an exception case and route it to the appropriate owner. The workflow can track resolution, reminders, escalation, and closure, then update Consonance once the missing data is supplied.

• Improves metadata quality before distribution
• Reduces delays caused by incomplete title records
• Provides accountability for data owners across departments

5. Contract and Royalty Exception Handling

Data flow: Consonance → OpenText Workflow Service → Consonance

Consonance can flag royalty anomalies, contract exceptions, or unusual payment conditions and pass them to OpenText Workflow Service for review and approval. OpenText can orchestrate finance, legal, and rights team reviews, capture supporting documents, and record the final decision before Consonance updates the title or rights record.

• Supports controlled handling of financial and contractual exceptions
• Improves transparency for royalty-related decisions
• Creates a documented approval history for audits

6. Content and Asset Approval Across Publishing Teams

Data flow: Consonance → OpenText Workflow Service

Consonance can initiate workflows for cover art, jacket copy, sample chapters, and marketing materials stored in connected systems, while OpenText Workflow Service manages the review and approval cycle. Once approved, status updates can be returned to Consonance so title records reflect the latest approved assets and publication readiness.

• Coordinates approvals across editorial, design, and marketing
• Ensures only approved assets are linked to title records
• Improves consistency between content, metadata, and production status

7. Publishing Issue Escalation and Case Management

Data flow: Consonance → OpenText Workflow Service

When a title encounters a critical issue such as a missed deadline, production blocker, vendor delay, or distribution discrepancy, Consonance can create a case in OpenText Workflow Service. OpenText can then manage escalation, assign owners, track resolution steps, and notify stakeholders until the issue is closed.

• Provides structured handling of publishing exceptions
• Improves visibility into blockers affecting launch dates
• Helps leadership monitor high-risk titles and intervene early

8. Periodic Workflow Reporting and Operational Review

Data flow: Consonance → OpenText Workflow Service → reporting systems

Consonance can provide title milestone and workflow status data to OpenText Workflow Service to support operational review processes such as weekly publishing meetings, launch readiness checks, and backlog triage. OpenText can route review tasks, collect approvals or comments, and feed completion status back into Consonance for a unified view of publishing progress.

• Supports disciplined operating rhythms across publishing teams
• Improves visibility into bottlenecks and overdue tasks
• Helps standardize workflow governance across multiple imprints