Hello,
Some time ago I described problem with Vault "Property Compliant" here.
There is this Configuration (mapping) UDP "Rev Number" and system property"Revision" in Vault:
Provider File Property Type Classification Mapping Create
Inventor Rev Number Text Standard Vault <-> Document Yes
Inventor DWG Rev Number Text Standard Vault <-> Document Yes
AutoCAD Rev Number Text Standard Vault <-> Document Yes
UDP "Rev Number" has declared categories "Document", i.e. only .idw.
System property "Revision":
Provider File Property Type Classification Mapping Create
Inventor Rev Number Text Standard Vault -> Document No
Inventor DWG Rev Number Text Standard Vault -> Document No
Rem: Vault cooperates with Inventor.
There is this problem with "Rew Number" and "Revision" in Vault:
a) Inventor .ipt/.idw template has default "Rev Number" value "A" for example.
When user checks in new .ipt and .idw with this "A" value and system Vault property "Revision"
has value "1" (according to Vault revision and categories declaration) the Vault should display
red exclamation mark and property "Property compliant" should has "Noncompliant" value for .idw.
But there isn't red exclamation nor "Noncompliant".
Red exclamation and "Noncompliant" has only .ipt. But why? .ipt isn't categories with UDP
"Rev Number"! Only .idw has it ....
b) The same situation is after running per lifecycle when Vault changes lifecycle state and
revisions. There are .ipt and .idw with "00" value and system Vault property "Revision"
has value "01" for example, but without red exclamation and without "Noncompliant" again.
c) When we use command "Property synchronisation" the Vault for .idw reports there is nothing
for synchronisation. Why? There is different value "00" and "01" ........
Rem: DBF reindexing doesn't help.
Do you happen to have some better practices with it?
Thank you for any help you can provide.
Peter
"There are a few different reasons that an object in the Vault can be non-compliant.
One of the reasons for non-compliance is equivalence. Equivalence verifies that a mapped
UDP and the source have the same value. If the file has the non-compliance
equivalence status then that means there is a difference between the two values.
This often can be resolved with a property sync or a check out/in."
Autodesk
Adam Luttenbacher
Sr User Experience Designer
Autodesk, Inc.