Change Forge - Approval Workflows for rConfig V8

Change Forge: Approval Workflow Control

Change Forge is the upcoming approval and governance layer of Change Manager. After reading this page, I can describe what Change Forge will do, when it’s arriving, and where to find more detail on the full Change Manager roadmap.

What is Change Forge?

Change Forge adds structured approval workflows for network configuration changes, completing rConfig’s closed-loop change management system. By requiring review and approval before changes are implemented, Change Forge prevents unauthorized modifications and creates an audit trail linking planned changes to actual deployments.

Change Forge works alongside Change Pulse: Pulse provides visibility into what changed, Forge provides control over what’s allowed to change.

Planned capabilities

Approval workflows: Multi-stage review chains with role-based routing and stakeholder notifications.
Automated validation: Pre-deployment syntax checks, policy compliance verification, and impact analysis.
Controlled deployment: Scheduled deployment windows, phased rollout, and automated rollback on failure.
Change Pulse integration: Automatic correlation between approved changes and detected modifications, with alerts for unapproved changes.

For the detailed approval flow, integration scenarios, and release roadmap, see the Change Manager Overview.

What can I do until Change Forge ships?

Maintain change governance with existing processes:

Use external ticketing systems for change requests and approvals.
Document approved changes in tickets with device and timeframe details.
Use Change Pulse to verify changes were implemented as approved.
Manually correlate ticket approvals with changes detected by Pulse.

What’s next

Change Manager Overview - full vision, roadmap, and Pulse/Forge integration details
Change Pulse User Guide - historical change visibility and analysis
Configuration Diffs - how diffs enable change detection