Skip to main content

Version History

What this page covers

Version History helps you review saved versions of a Configuration, understand what changed, compare an older version with the current version, and restore an older version when that action is available.

In the WebHammers interface, the shared history screen uses the label Revision history. The version number is shown as v1, v2, and so on. In this guide, "version" and "revision" refer to the saved Configuration versions you can review from that screen.

What Version History is

Version History is a review area for saved Configurations. It lets you look back at earlier versions of the same Configuration without changing your File or dataset.

For most Tool Configurations, the shared Revision history screen supports three main tasks:

  • view a plain-language summary of a saved version
  • compare a saved version with the current version
  • restore an older version after review, when your access allows it

Import Designer has a separate history screen for Import Designer Configurations. That screen lists versions and shows which version is current. Compare or restore actions may not be available there.

When to use Version History

Use Version History when you need to answer practical questions such as:

  • What changed in this Configuration since an earlier version?
  • Who saved a version, when that information is available?
  • Did a Field, Rule, setting, or output option change before a recent Run?
  • Should we restore a prior Configuration after a mistaken change?
  • Is the current Configuration still the right one to reuse or share with a Team?

For example, if a Filterer Configuration no longer keeps the expected Records, you can compare the older version with the current version and check whether a Rule, default action, Field, or comparison value changed.

Before you begin

Before using Version History, make sure:

  • you are signed in
  • the Configuration has saved versions
  • you are opening history from the correct Tool and Configuration
  • the correct Team context is selected if the Configuration belongs to a Team
  • you have access to view the Configuration

For restoring, WebHammers applies additional restrictions:

  • a current version must exist
  • the selected version must not already be the current version
  • personal Configuration restore is limited to the owner
  • Team Configuration restore is limited to users with Admin or Editor access

If your access does not allow an action, the action may not appear or WebHammers may show a message such as Restore not allowed.

Screen overview

The shared Revision history screen includes these main areas.

AreaWhat you do there
HeaderReview the Configuration name, Tool type, current version, saved version count, and use Refresh or Back to Editor.
Progress stepsFollow the restore review flow: Choose revision, Review changes, and Restore safely.
Saved revisionsSearch, filter, and choose a saved version.
Details panelView a Plain-language summary or Change details for the selected version.
Side panelReview what you can do next, including Review changes or Continue to restore safely when available.

What appears in the saved version list

For most Tool Configurations, the Saved revisions table shows:

ColumnWhat it means
VersionThe saved version number, such as v3.
When savedThe date and time the version was saved, shown in UTC.
Saved byThe user who saved the version, when available.
SummaryThe change summary, or No summary provided.
StatusWhether the version is Current, Previous, or Original.
ActionsAvailable actions such as View, Compare, or Restore.

The screen also includes a search box with the prompt Search by version, date, or person and a status filter with All versions, Current only, Previous only, and Original only.

Data handling note

WebHammers jobs run on your machine. Your data stays on your machine during Tool processing. WebHammers servers store Configurations so they can be reused, shared, and managed. A Configuration may include information such as the Field names from your data files.

Version History applies to saved Configuration information. Restoring a Configuration version does not change your source data Files.