It would be nice if Vault Basic fully supported *.inest files. I use an iLogic configurator to generate models, drawings and nests of the sheet metal parts that our products contain, and it would be greatly appreciated if I could check-in/delete the whole enchilada from an arbitrary open file in the structure (regardless of how many of the other files that are currently open as well), including everything from the drawing featuring the main assembly the to leaf occurences and back upwards through all parallel paths through INEST-files, drawings that contain views of some, but not all, of the components, etc, etc, and then utilize the copy design function on its entirety. Another immensly powerful improvement I would like to see is the full and complete interopertibility between Vault and iLogic. That would for instance enable me to write a code that checks-in, copies design, renames the files that are copied, AND updates the referrences in the iLogic code with the new file names and so on.
Show More