OpenText Decision Service - Microsoft Planner Integration and Automation

Common Integration Use Cases Between OpenText Decision Service and Microsoft Planner

OpenText Decision Service is well suited for automating rule-driven decisions in operational processes, while Microsoft Planner is used to organize and track team tasks, assignments, and progress. Together, they can connect automated decision outcomes to human work execution, improving speed, consistency, and accountability across teams.

1. Decision-Based Task Creation for Exception Handling

When OpenText Decision Service identifies an exception in a business process, it can automatically create a Microsoft Planner task for the responsible team to review and resolve it.

• Flow: OpenText Decision Service to Microsoft Planner
• Example: A loan application fails a policy rule and is routed to a credit analyst task in Planner.
• Business value: Reduces manual triage and ensures exceptions are assigned immediately to the right team.

2. Priority Assignment Based on Decision Rules

Decision rules can classify work items by urgency, risk, customer segment, or SLA impact, then create Planner tasks with the appropriate priority and due date.

• Flow: OpenText Decision Service to Microsoft Planner
• Example: High-value customer complaints are automatically assigned as urgent tasks with shorter deadlines.
• Business value: Helps teams focus on the most critical work first and improves SLA compliance.

3. Automated Work Queue Management for Operations Teams

OpenText Decision Service can evaluate incoming requests and determine whether they should be handled automatically or sent to a Planner board for manual processing.

• Flow: OpenText Decision Service to Microsoft Planner
• Example: Insurance claims that exceed a threshold are routed to a claims review Planner bucket.
• Business value: Creates a controlled handoff between automated decisioning and human review, improving operational consistency.

4. Task Updates Triggering Decision Re-Evaluation

When a Planner task is updated, such as status change, completion, or reassignment, the update can trigger OpenText Decision Service to re-evaluate the case or process rules.

• Flow: Microsoft Planner to OpenText Decision Service
• Example: A compliance review task marked complete triggers a final approval decision in the downstream process.
• Business value: Keeps decision logic aligned with real-time operational progress.

5. Policy-Driven Assignment of Tasks to Teams

OpenText Decision Service can determine which team should receive a task based on business rules, then create the task in the correct Planner plan or bucket.

• Flow: OpenText Decision Service to Microsoft Planner
• Example: Vendor onboarding tasks are assigned to legal, procurement, or finance based on supplier type and risk level.
• Business value: Improves routing accuracy and reduces manual reassignment.

6. Escalation Management for Overdue or High-Risk Tasks

Planner task status can be monitored and sent to OpenText Decision Service to determine whether escalation rules should be applied, such as notifying managers or creating follow-up work.

• Flow: Microsoft Planner to OpenText Decision Service
• Example: A task overdue by more than three days triggers an escalation decision and a new task for the supervisor.
• Business value: Strengthens governance and helps prevent delays from affecting business outcomes.

7. Cross-Functional Case Coordination

OpenText Decision Service can evaluate a case and generate multiple Planner tasks for different departments, each based on the same decision outcome.

• Flow: OpenText Decision Service to Microsoft Planner
• Example: A customer dispute triggers tasks for billing, legal, and customer service teams with different instructions.
• Business value: Supports coordinated execution across departments without duplicating decision logic.

8. Closed-Loop Process Improvement and Reporting

Planner task completion data can be fed back into OpenText Decision Service to analyze decision outcomes and refine business rules over time.

• Flow: Microsoft Planner to OpenText Decision Service
• Example: Repeated task delays in a specific approval path indicate a rule threshold may need adjustment.
• Business value: Enables continuous improvement of decision policies based on operational performance.