We are evaluating the PTC Integrity tool, and we have a databased system for tracking files for projects and a very flat means of tracking files in a repository by individual files/branches/versions. Thus we clash heavily when because Integrity's Projects are doing much the same. In the PTC Integrity training I've done so far, mentioned but not expounded upon is the Archive. I suppose an archive is just a container for (or simply a database object to track) versions of a file, any labels or special attributes that may be associated with the file, and the content of the file.
Are there any commands that would allow users to extract files by version, check-in files, check-out files, and build sandboxes from specific versions of files or by label with respect to the Archive rather than via the Project?
We have a very complex system where the Project level might apply easily at a subsystem level, but it gets overwhelming "fast, quick and in a hurry" when we combine that complexity with the next level complexity one level above that. Our software reuse and maintenance requirements would create millions(!) of links just on import.
Any thoughts?
