Administrator
User Guide
Using Stamps
Using Stamps
If you want to determine the changes that have been made to given elements since a specific date, you must compare the relevant session on the DB to the current session. Although you can manage and compare sessions manually, comparing sessions is simpler if you use Stamps to mark the relevant session of DBs, either by specifying a time and date, or a session number.
Stamps allow you to ‘mark’ a set of databases at significant stages of a project. You can then use the Stamp name instead of the database name and session number when you are working with databases.
Using Stamps with database sessions makes it easier for you to:
•
Make comparisons and identify changes made from session to session ‑ for example, you can issue drawings on which all revisions that have been made since an earlier stamped session are highlighted.
•
Merge database sessions without needing to manually select which sessions to remove. Database sessions included within a Stamp are considered permanent and are not removed when a MERGE CHANGES command is given.
•
Backtrack a standard database to a previous session.
•
Revert an extract database to a previous session.
This chapter gives background information about how Stamps are stored in the System database and explains how to create Stamps, how to stamp DB sessions, and how to modify, copy and delete Stamps. For information on how you can use Stamps to merge changes or backtrack changes, refer to
Project Administration
.
1974 to current year.
AVEVA Solutions Limited and its subsidiaries. All rights reserved.