Revert to an Older Version
Goal
Use this page when you need to restore an older Configuration version so it becomes the current version for future use.
The shared Revision history screen uses the button label Restore, not "revert." This page uses "revert" in the general sense of returning to an older Configuration version.
When restore is available
Restore is available for most Tool Configurations on the shared Revision history screen when all of these are true:
- the Configuration has a current version
- the selected version is not already current
- the version is available to restore
- your access allows restore
Restore may not be available on the Import Designer history screen. If you do not see restore actions there, treat that history screen as view-only unless your WebHammers administrator or support contact tells you otherwise.
Before you restore
Before restoring, compare the older version with the current version and confirm that you understand what will change.
Check:
- the selected version number
- who saved the selected version, when that information is available
- the Change Summary
- changed Fields, Rules, settings, and output options
- details that exist only in the current version
- details that exist only in the selected older version
- whether a recent edit may have happened since you opened the history screen
- whether the Configuration belongs to your personal area or a Team
For Team Configurations, remember that restoring changes the active Configuration for future use. Users may see different Tool results after restore.
Restore an older version
- Open the Configuration's History screen.
- In Saved revisions, select an older version.
- Select Compare to review the differences.
- Select Continue to restore safely.
- Review Confirm before restoring and Restore summary.
- In Final confirmation, type the required phrase shown on the screen, such as
RESTORE V2. - Select the acknowledgement checkbox: I understand this changes the active configuration for future use.
- Select Restore version v#.
You can use Back to review to return to the comparison, or Cancel to stop the restore flow before confirming.
What changes after restore
Restore behavior for shared Tool Configurations:
- the active Configuration changes to match the selected older version
- the restored version is saved as a new current version
- existing revision history remains available
- the previous current version remains in history so it can be reviewed later
- source data Files are not changed
- only the selected Configuration changes
After a successful restore, WebHammers may show a message such as Restored v2 as new current v6.
Permissions and restrictions
Restore restrictions include:
| Situation | Behavior |
|---|---|
| Current version selected | The current version cannot be restored. |
| No current version exists | Restore is not available. |
| Personal Configuration | Restore is limited to the Configuration owner. |
| Team Configuration | Restore is limited to users with Admin or Editor access. |
| Configuration changed during restore review | WebHammers reloads the latest history and asks you to review again before restoring. |
| User does not have restore access | WebHammers may show Restore not allowed or a permission message. |
What to check after restoring
After restore:
- Confirm the restored version is now marked Current.
- Open the Configuration editor and review the settings.
- Preview results if the Tool supports preview.
- Run the Tool on a small representative File before relying on the output.
- Review the Run result and output File carefully.
Do not assume that a restored Configuration is ready for every current File. If Field names, Rules, or business requirements changed after the older version was saved, the restored Configuration may need additional review.
Common mistakes to avoid
- restoring before comparing the older version with the current version
- assuming an older version includes newer Fields or Rules
- ignoring Current only details that would no longer be active after restore
- reusing a restored Configuration without previewing or testing a Run
- restoring a Team Configuration without considering who uses it