The Source Integrity Professional Edition User Guide - MKS

Managing Archives
and Revisions
6
While sandboxes and projects allow you to manage and access
project members, the contents of individual member files—and the
history of changes you make to them—are saved in the archives.
Source Integrity lets you save—and recreate—every stage (or
revision) in the development of every file you use.
When you make changes to a project member and then check it back
in, your changes are automatically added to the member’s archive. If
you ever need to see that version of the file again, just check out the
appropriate revision, and Source Integrity rebuilds an exact copy for
you. Not only can every file in a project be archived, the project itself
can be archived (checkpointed), allowing you to rebuild the entire
project configuration at any time.
While the archive commands are as safe and easy to use as their
project-oriented counterparts, they do not communicate their
activities to your projects. For example, if you normally access a file
through a Project window, but another developer uses the archive
commands to check out the file, makes changes to it, and checks it
back into the archive, the project is not automatically updated. MKS
therefore recommends that you usually work through projects and
sandboxes.
User Guide 165