OpenText Decision Service - OpenText Workflow Service Integration and Automation

Common Integration Use Cases Between OpenText Decision Service and OpenText Workflow Service

1. Policy-Based Case Routing and Approval

Data flow: OpenText Workflow Service to OpenText Decision Service, then back to OpenText Workflow Service

Workflow Service captures a new case or request, such as a loan application, claims intake, or contract review. It sends key attributes like customer segment, amount, risk score, or document type to Decision Service. Decision Service evaluates business rules and returns the required path, such as auto-approval, manager review, legal review, or rejection. Workflow Service then routes the case to the correct team and task queue.

Business value: Faster routing, fewer manual triage errors, and consistent application of approval policies across departments.

2. Dynamic SLA Assignment Based on Case Priority

Data flow: OpenText Workflow Service to OpenText Decision Service

Workflow Service initiates a process for service requests, complaints, or operational incidents and passes case details to Decision Service. The rules engine determines SLA targets, escalation thresholds, and priority levels based on customer tier, issue severity, regulatory impact, or business unit. Workflow Service applies the returned SLA and escalation rules to the case.

Business value: Better service consistency, improved compliance with response commitments, and more effective escalation management.

3. Automated Exception Handling for Process Variants

Data flow: OpenText Workflow Service to OpenText Decision Service, then back to OpenText Workflow Service

When a workflow encounters an exception such as missing documentation, policy mismatch, or threshold breach, it calls Decision Service to determine the correct exception path. The decision logic may instruct the workflow to request additional information, send the case to a specialist queue, or continue with conditional approval. This avoids hard coding exception logic into the workflow model.

Business value: More flexible process design, easier maintenance of exception handling, and reduced rework when policies change.

4. Compliance Validation Before Task Progression

Data flow: OpenText Workflow Service to OpenText Decision Service

Before a workflow advances to the next stage, it submits relevant case data to Decision Service for compliance checks. Examples include verifying required disclosures, validating approval authority, checking segregation of duties, or confirming document completeness. Based on the result, Workflow Service either advances the case, pauses it for remediation, or escalates it for review.

Business value: Stronger control over regulated processes, fewer compliance breaches, and improved audit readiness.

5. Real-Time Eligibility Determination for Customer Requests

Data flow: OpenText Workflow Service to OpenText Decision Service, then back to OpenText Workflow Service

For requests such as benefits enrollment, credit limit increases, warranty claims, or discount approvals, Workflow Service collects the request and sends customer and transaction data to Decision Service. Decision Service evaluates eligibility rules and returns a decision such as eligible, conditionally eligible, or not eligible. Workflow Service then continues the process with the appropriate customer communication and internal task assignment.

Business value: Faster customer response times, standardized eligibility decisions, and reduced manual review workload.

6. Automated Assignment of Work Based on Decision Outcomes

Data flow: Bi-directional

Workflow Service manages the overall process and sends case attributes to Decision Service to determine the best assignment logic. Decision Service returns the assignment criteria, such as skill group, region, product line, or risk category. Workflow Service uses that output to assign the task to the right team or individual and can later send updated case information back to Decision Service if reassignment is needed.

Business value: Better workload distribution, improved first-time resolution, and more accurate task ownership.

7. Policy Updates Without Workflow Redesign

Data flow: OpenText Decision Service to OpenText Workflow Service

Business users update rules in Decision Service when policies change, such as new approval thresholds, revised service entitlements, or updated exception criteria. Workflow Service continues to execute the same process model but consumes the updated decision outcomes automatically. This allows process owners to change business behavior without rebuilding workflow steps.

Business value: Greater agility, lower change management effort, and reduced dependency on application development for policy updates.

8. Closed-Loop Process Monitoring and Decision Tuning

Data flow: Bi-directional

Workflow Service executes cases and records process outcomes such as cycle time, rework, escalations, and approval rates. Decision Service uses this operational data to refine rule thresholds and decision paths. In return, updated decision logic improves future workflow execution. This creates a feedback loop between process performance and business rule optimization.

Business value: Continuous improvement of both workflow efficiency and decision quality, with better visibility into process bottlenecks and rule effectiveness.