Revision containers
The purpose of this feature is to display, in the same Tree User Interface, older revisions of assemblies or structures for which it is available a .TREE file, created at approval time.
Requirements
A field named DBW_EC_TYPE of type varchar(50)
The field must be exposed to both the Generic and Project database views
How it works
When building the Tree structure, MechworksPDM looks for any Generic or Project type document for which the DBW_EC_TYPE field is not empty.
If not empty, DBWorks gets the 1st level children of the document with DBW_EC_TYPE not null.
For each 1st level child, it then looks for the PARENT_CHILD_REVISION field, and, if not null, it looks if any .TREE file is available for the PARENT_CHILD_REVISION of the 1st level child document.
If the .TREE file is available, it will be used for building the sub-tree.
Recommendations
If a Project will be used as Revisions Container, it must be set to a RELEASED state.
Example
In the picture below, the Generic Document with ID="RevisionsContainer" has the DBW_EC_TYPE set to an arbitrary value; the PARENT_CHILD_REVISION value for the PARENT_CHILD relation between the RevisionsContainer Generic Document and the Wilwood Master Cylinder Assembly Document is set to "B".
On the top of the picture, you can see that the Wilwood Master Cylinder Assembly is displayed with its current database relations and values, while in the sub-tree under the RevisionsContainer Generic Document, the same assembly is displayed with its structure at Revision="B". It is interesting to note that the component Reservoir Cover has been deleted from the database, so it is represented in the Tree as an OBSOLETE document.
The markers and on the right side of each ID help to remember that the structure is not available in the database, but it has been loaded from a .TREE revision file.
