Generic files include a “family table” of file or assembly “instances.”
There are specific behaviors associated with generic files when working through Vault
To generate accurate Where Used and Uses information as well as provide a full Bill of Materials, the Vault add-in for Pro/Engineer and Creo creates instance files on the first check-in. These "dummy files" are generated on disk and are tiny in size (only a few bytes).
Check-in shows Generic files and Instances.
Instance files associated with a generic file cannot be opened directly in Pro E. You must always open them through the generic file.
A view of the instance is opened from the generic file with Vault relationships.
In some cases, you might receive a message that some files are preventing the check-in of an assembly to Vault. This could be due to modified instances of a generic.

The instances should resolve with the latest versions from Vault, enabling you to check in the assembly.

Instance files should no longer incorrectly appear as modified.
Save_Objects Options
|
Option |
Impact on Vault Statuses |
|---|---|
|
all |
All files of assembly are labeled as modified. |
|
change_and_specified |
The set of files is labeled as modified. |
|
changed |
Some last level parts are labeled as modified. |
|
changed_and_updated |
No files are labeled as modified. If you change an assembly or part, it is labeled correctly. |
|
no "save_objects" specified |
Only top level assembly is labeled as modified. |