Diagram Version History and Snapshots
Track diagram evolution with snapshot versioning. Stamp meaningful checkpoints, navigate history, and anchor downstream references to specific versions.
Architecture diagrams evolve. Systems change, designs are refined, and stakeholders need to understand how things have changed over time. NeoArc Studio's Snapshot Versioning creates a permanent record of your diagram at key milestones, allowing you to navigate back through its history.
When to Stamp a Version
Stamping a Version
Open your diagram and follow these steps to create a version snapshot.
Navigating Version History
Click any version in the history list to view the diagram as it looked at that point in time.
Lifecycle Tagging on Diagram Elements
In addition to version snapshots, individual shapes and connections can carry lifecycle status: active, planned, or deprecated. This provides a visual overlay showing which parts of the architecture are current, which are coming, and which are being retired.
| Status | Visual Treatment | Purpose |
|---|---|---|
| Active | Default styling | Elements live in production |
| Planned | Dashed border or muted styling | Approved elements not yet implemented |
| Deprecated | Faded or strikethrough styling | Elements being retired |
Lineage Anchoring
Downstream systems like schemas and published content can reference a specific version. This "lineage anchor" means consumers see a consistent, blessed state rather than work-in-progress.
Version Metadata
Each version captures full metadata for traceability.
| Field | Description |
|---|---|
| Version Name | User-provided label (e.g., "Phase 1 Complete") |
| Description | Optional explanation of the diagram's state |
| Timestamp | When the version was stamped |
| Change Summary | Auto-generated list of modifications since the previous version |
| Shape Count | Number of shapes at this version |
| Connection Count | Number of connections at this version |
Track changes to graph diagrams with snapshot versioning and lifecycle tagging. Create named snapshots, compare versions, and manage entity lifecycles with active, planned, and deprecated states.