About Vaulting Rules
You can establish file vaulting rules that identify the vault and folder to which content files are to be uploaded based on the domain, location, and life cycle state of the object with which they are associated. Main vaults can be created at File Server sites and main sites.
Windchill domains can be created in a hierarchical fashion, with some domains being children of other domains. It is important to note that a domain does not inherit the vaulting rules of its parent domain. You must explicitly define vaulting rules at each level of a domain hierarchy.
When determining the vault should receive a content file upload, the file vault service applies the most specific, valid rule.
Content files are moved into a vault only when an object is checked into the Windchill database and its content file is uploaded. Therefore, a file does not automatically move to a new vault when the life cycle state of the object changes (unless the wt.fv.revaultOnChange property is set to true). Instead, the file is moved to the appropriate vault the next time it is uploaded.
* 
The content may not always be immediately uploaded to the vault where it will be stored. To make the system more efficient, the file is sometimes initially uploaded to the defaultuploadvault and then later moved to the appropriate location during scheduled revaulting (through CacheVaultSynchronization).
Was this helpful?