Validate

• To be validated, an object has to be in the vault (blue padlock before the object in the project tree).

• A validated object becomes a major revision.

• Modifying a validated object moves it to the next minor revision. For example, part A.1 (minor revision) becomes part A (major revision) when it is validated. If it is modified, the new revision should be the same then the previous one. When it is saved, TopSolid analyzes if it corresponds to a true modification. If it is the case, the text of the major is incremented and changed to B. If not, it satys with A.

In the case of a hardly in place assembly, it is synchronized with n parts. If the assembly is validta A and one of the part is modified, there are new major for the assembly and parts. When saving, the part really modified will have a revision B when all other parts will have A.

- In some cases, A(1) is displayed because several majors have the same letter and TopSolid has to different them. (redirection, tree,...)

- The analyze of the part is only be done when saving for performance reasons. The major is called A(i) by waiting the save. If the user has a doubt, he can save to see if A(i) becomes B or will stay with A(i).

• Previous minor and major revisions can be viewed by clicking on the "+" sign before the object in the project tree and scrolling through the Revisions folder.

• When a document should no more be used, you have to make it obsolete.

• In the context of exchanging data with import package by replication, validation must be done by one person only. This in order to avoid conflict / import failure if the same document is validated on two different PDM.

• Once a document is validated, it is no more possible to go back in a Design state for the same revision.

Document in the vault, but not validated

validated document

Obsolete document