Our approval workflow is getting stuck because the decision table isn’t returning the correct routing pattern. We have a decision table that should route purchase requests based on amount and department, but some combinations are falling through without a match.
Decision table structure:
IF Amount < 5000 AND Dept = IT THEN Route to IT_Manager
IF Amount >= 5000 AND Dept = IT THEN Route to IT_Director
IF Amount < 10000 AND Dept = Finance THEN Route to Finance_Manager
The problem appears when we have amounts between 5000-10000 for Finance department - the workflow just stops. I suspect the decision table completeness is an issue, but I’m not sure how to validate all possible routing paths. Any guidance on conditional routing best practices and rule validation would be helpful.
Don’t forget to document your routing logic in the decision table description field. When audit time comes around, you’ll need to explain why certain approval paths were chosen. Also consider adding date-effective rules if your approval thresholds change over time.
Best practice is to do both - define explicit rules for known scenarios and add a catch-all default rule for unexpected cases. The default rule should route to an exception handler or administrator queue. This way you won’t have workflows getting stuck, and you’ll get visibility into edge cases you didn’t anticipate. I also recommend using a decision table testing tool to validate completeness before deploying to production.
Your decision table has critical gaps that need systematic resolution. Let me address all three focus areas:
Decision Table Completeness:
Your current table only covers 3 scenarios but needs comprehensive coverage. Create a completeness matrix:
# Complete decision matrix for 2 departments, 3 amount ranges:
IT Dept:
Amount < 5000 → IT_Manager
Amount 5000-9999 → IT_Director
Amount >= 10000 → IT_Director + CFO
Finance Dept:
Amount < 5000 → Finance_Manager
Amount 5000-9999 → Finance_Director
Amount >= 10000 → Finance_Director + CFO
Default (other depts or null values):
→ Exception_Queue
Conditional Routing Best Practices:
Implement a three-tier routing structure:
- Primary Rules: Specific department + amount combinations with exact routing targets
- Secondary Rules: Department-only rules with default routing (lower priority)
- Fallback Rule: Catch-all that routes to exception handling (lowest priority)
In Power Platform, set this up by ordering your decision table rows from most specific to most general, and enable the “Stop after first match” option if you want exclusive rule execution.
Rule Validation Strategy:
Before deployment, validate your decision table using this checklist:
-
Completeness Check: Create a test matrix with all possible input combinations. For your case: 2 departments × 3 amount ranges = 6 mandatory rules minimum
-
Overlap Detection: Identify rules that could match the same input. Use priority ordering to resolve conflicts:
Priority 1: Amount >= 10000 (any dept) → Escalation path
Priority 2: Dept-specific amount rules
Priority 3: Default department rules
Priority 4: Global fallback
-
Gap Analysis: Run a simulation with boundary values (4999, 5000, 9999, 10000) for each department to ensure no workflow gets stuck
-
Null Handling: Add explicit rules for null/empty department or amount values
To implement this in Power Platform, edit your decision table and add these additional rows:
- Finance + Amount 5000-9999 → Finance_Director
- Finance + Amount >= 10000 → Finance_Director, CFO (multi-approver)
- IT + Amount >= 10000 → IT_Director, CFO
- Any + Amount >= 50000 → Executive_Committee (override rule)
- Default → Exception_Queue
Enable “Validate decision table” in the properties panel to get automatic completeness warnings. Test thoroughly with your boundary cases before deploying to production. This structured approach ensures your conditional routing handles all scenarios without workflow stalls.
You’ve identified the issue correctly - your decision table has gaps in coverage. For Finance department, you only have a rule for amounts under 10K, but nothing for amounts 10K and above. You need to add rules to cover all possible combinations of Amount and Department values.