Windchill System Administrator's Guide

Modifying and Deleting Rules
Managing Revaulting
When determining the vault to which to direct content files when an upload
operation is requested, the file vault service applies the most specific, valid rule.
For example, consider the following rules:
Rule 1: Vault1
Rule 2: Vault2
Assume that a given document object (WTDocument) is associated with the User
domain and is in the InWork life cycle state. Rule 1 would direct its content to
Vault1, regardless of its life cycle state. However, Rule 2 indicates that content
files should go to Vault2 when the document is in the InWork life cycle state. So,
in that case, the most specific rule would be applied, and any content associated
with the document would be stored in a folder within Vault2.
Note: Currently, content files are moved into a vault only when an object is
checked into the Windchill database and its content files are uploaded. Therefore,
a file does not automatically move to a new vault when the life cycle state of the
object changes. Rather, the file is moved to the appropriate vault the next time it is
uploaded.
When you are satisfied with your selections, click OK to save the rule and exit the
window. Click Cancel to exit the window without saving the rule.
If you return to the Domain window, the list of vaulting rules will includes the
rules you created in this session.
To update a vaulting rule, select it from the list displayed and click Update. When
a rule is updated, only the selected vault may be changed. The class and life cycle
state remain constant.
To delete a rule, select it from the list displayed and click Delete.
When a vaulting rule is created, modified, or deleted, it is necessary to relocate the
files to their new home. This process is called revaulting.
Revaulting is necessary when a vaulting rule is modified to use another file vault
or when a vaulting rule is deleted, which is equivalent to designating the object
storage to be in a BLOB. Revaulting may also be needed when a change occurs in
the domain or life cycle state of an object that holds content files. The revaulting
process for such object changes can be done in the background, which is
administered by a property, wt.fv.revaultOnChange. If you are not setting
properties through a graphical user interface or in a mapping rules file, you add or
edit properties with the xconfmanager utility, which is discussed elsewhere in this
guide.
3-16 Windchill System Administrator’s Guide