Version History

Audit rule set changes to investigate issues, validate updates, and maintain accountability

Version History provides a chronological record of changes to a rule set, including what changed, who made the change, and when it occurred. It gives administrators the visibility needed to investigate issues, validate updates, and maintain accountability across teams.

View Version History

Each rule set includes a Version History tab that shows all versions associated with that rule set.

The tab includes a table that shows:

  • Timestamp of the change
  • Version type (Active or Test)
  • Version number
  • User (email address)
  • Role
  • Comment (optional note added when the change was made)

Versions are sorted by most recent first, making it easy to track the latest updates.

There are two version types:

  • Active versions are created whenever changes are saved directly to the active version, or when a test is promoted to active.

    • ⚠️ Updates to the Rule Set Name and Description do not create a new active version.
  • Test versions are created each time a test is created or updated and are scoped to that test.

    • Test versions appear in Version History only while a test is running.
    • When a test is deleted or promoted to Active, its version history is removed.

This ensures Version History reflects only relevant and current changes.

Example Version History tab in a rule set

View Version Details

Click any row in the table to see a detailed view of that version and a comparison to the previous version.

The details view shows:

  • Current Version
  • Previous Version
  • Version Comparison

Version History highlights what changed between versions so you can quickly understand impact.

Examples of changes include:

  • Rule added
  • Rule removed
  • Rule condition modified
  • Outcome modified
  • Default outcome modified

Comparison rules:

  • Active versions are compared to the previous Active version
  • Test versions are compared to the previous Test version
⚠️

Important Notes

  • Version History is scoped to a single rule set (not a global audit log yet)
  • Versions are immutable once created