If I'm not wrong, at this time, Vault is able to map and import existing iProperties coming from "User Defined Property" property set only.
If for some reason or particular customization you need to create your own PropertySet with custom iProperties, you will not be able to import them into Vault UDPs.
I think it would be very useful to extend this feature and allow administrators to map iProperties from any Property Set.
Just for an example, with this feature available, you'll be able to import into vault the "IsCustomPart" iProperty that's simplify rules to understand if a ContentCenter part is a "real" CC part or not.
We have a customer using two different revision schemes. One for external rev (A,B,C,D ..) and one for internal revisions (a,b,c,d ..). Today they manually switch between them.
We have a problem with copying files. If i use Copy Design to create a file from a revision A (external rev scheme) file, Vault will create a new file in the same revision scheme as the first one. Not the default start revision wich is a (internal rev scheme).
We then have to change the revision to a (internal rev scheme) and start working with the new file.
If I now try to change the revision to A Vault will give me an error saying that this revision already has been used and i can not get around this problem unless I delete the file from vault and "re-checkin" or create another copy from the rev a file??
on 07-25-201208:00 AM - last edited on 01-14-201301:10 PM by ihayesjr
I'm not sure if it is allowed to request new API features in Idea Exchange.
It should be possible to enable/disable custom commands introduced by a vault extension. E.g. if a command is only available for a special user (Administrator) the command should be disabled for all other users.