Version Control

Every publish captures a snapshot of the report and everything on it.

When you publish a report, PersivX writes a complete snapshot — the report layout plus every visualization's attributes, query config, visual config, and models used — and stamps it with a version number.

Versions Advance Only on Real Changes

Before creating a new version, PersivX compares the current state against the previous snapshot. If nothing has actually changed, no new version is created and the existing one stands.

💡 Why This Matters Publishing repeatedly — because you were unsure whether a change saved, or because publishing is part of a routine — doesn't inflate the version history. The version number tracks meaningful changes, not publish attempts.

Environments

A report always has a working state, referred to as dev, plus a published state per environment. Without a release pipeline, publishing goes straight from dev to prod. With a pipeline, each stage is its own environment and each one holds its own published version.

For each environment PersivX records:

Field	Meaning
version	The version number currently live in that environment.
lastUpdatedAt	When that version was published there.

ℹ️ Promotion Carries the Version, It Doesn't Create One Publishing from dev may create a new version. Promoting an already-published version from one pipeline stage to the next carries the same version forward — so the artifact that was tested is the artifact that reaches production.

Version Comments

A version can be saved with a comment describing what changed. Comments are stored with the snapshot and shown in the version history, which is the difference between a list of numbers and a usable audit trail.

Viewing History

The version history lists the versions recorded for a report along with their comments. Where a report has a release pipeline, you can also see which version each stage currently holds and, if you have rights on that stage, switch between them.

Visualizations Are Versioned Too

Publishing a report versions every visualization on it — including visuals nested inside sections and tabs. A report snapshot is therefore self-contained: it captures the whole composition, not just the page layout.

💡 Related To move a report between PersivX instances rather than between environments, see Export & Import Reports.