Outcome-Based Routing

outcomePortMap Configuration

Define a port name per expected rule outcome. The executor fires the matching port key, and the canvas routes to the edge connected to that port:

{
  "outcomePortMap": {
    "approved": "approved",
    "rejected": "rejected",
    "manual-review": "review",
    "escalated": "escalate"
  }
}

Canvas Layout

RuleEvalNode (checkInvoicePolicy)
    │
    ├── [approved] ──→ UpdateEntity (status=approved) → SendEmail (approved notification)
    │
    ├── [rejected] ──→ UpdateEntity (status=rejected) → SendEmail (rejection + explanation)
    │
    ├── [review]   ──→ ApprovalNode (manual review queue)
    │
    └── [escalate] ──→ SendSlackMessage (#finance-escalation) → ApprovalNode (finance director)
  

Unmatched Outcomes

If the rule engine returns an outcome that is not in outcomePortMap, the executor routes to the main port. Connect the main port to a catch-all handler (e.g., an error notification or a manual review path) to handle unexpected outcomes gracefully.