Route Processing

The current processing model is:

One Stream
  ↓
Many Routes
  ↓
Many Destinations

Each Route is a destination-specific processing unit.

Inheritance

Routes can inherit shared/default processing and override only the concern that differs for a specific destination. This avoids creating multiple Streams solely because two destinations require different field mappings or protection policies.

Persist caveat

The current known-limitations record identifies Intent only cases for incomplete Classification or Protection override payloads. If Deploy shows Intent only where you expected a persisted override, open the Route editor after deploy, save a complete configuration, and verify Effective Status reports Overridden.

Hands-on scenario tutorials (2026-10-18)

One Stream, two Destinations: test global inheritance versus Route override using two independent HTTP sinks.
Mask only the external Route: configure and prove that protected data differs by Destination.
Handle schema changes: validate Union Schema observations and explicit unknown-field policy.

For numbered UI screenshots with action-by-action captions, see Stream Wizard visual walkthrough.

Last modified on October 18, 2026

Getting Started

Step-by-step Use Cases

Administration

Processing & Governance

Operations

Deployment

Security

Reference

Roadmap

Route Processing

Route Processing

Inheritance

Persist caveat

Hands-on scenario tutorials (2026-10-18)

​Route Processing

​Inheritance

​Persist caveat

​Hands-on scenario tutorials (2026-10-18)

Route Processing

Inheritance

Persist caveat

Hands-on scenario tutorials (2026-10-18)