This article describes how to view and manage your product version history.
In this article:
In the sidebar, click Client-Side Versions to view an easy-to-understand display of your version history, including published saves, unpublished saves, and the currently displayed version.
You can filter which versions display by checking one or more of the following filters:
Once a version is published, you quickly perform simple tasks for the selected version.
Click the down arrow next a version title and select one of the following options:
This option only displays if there are change available to merge into the current session. Click to merge a prior version into the current version. Both the incoming and current versions must originate from the same origin or ancestor. To determine which versions you can or cannot merge, select the Show Version Relationship filter in the dashboard. The version list is highlighted to show how each version is related to the others.
There are two methods for saving changes, Save and Save As, and the distinction between the two (explained below) is important. For either option, click the Save/Publish button in the upper right corner of the sreen. Before saving you must add notes and select which environment(s) to publish to. If you do not specify an environment, your version will be an "Unpublished Save".
When you perform a Save, you overwrite the current settings and configurations for the selected version. Previous settings become unrecoverable. Any Save you make is recorded in the Versions interface. Published versions display as a dark gray folder and unpublished versions display as a light gray folder. Iterations of a version are displayed on the same version level.
When you perform a Save As, a new version is created and the the folder icon representing the version displays appears on a new level, separate from the previous version. If you need to rollback to the previous version, it is still available with all of its settings.
You can switch back to a previous version of your account and republish it to any environment. The republished version will contain the configurations or settings of the old version.
Use the following steps to switch back to a previous version:
Use the following steps to access the utag.js file for a version that is currently deployed,
Use the DIff tool to compare any two published versions and review the code changes from their Distro files. Code revisions between versions are highlighted and presented side by side, making it a easy to distinguish the changes.
For additonal details, see the Diff Tool article.
Merging Changes is a built-in feature that makes it easy to bring changes from an older version into the currently-published version. You can only merge two versions if they have branched away from the same origin or ancestor. To learn more, see Merge into current session.