I develop several types of custom views in Vault Explorer for different purposes.
I would like to develop a hand full that match my setups (example: show all the properties that populate out parts list) and be able to have those pushed out to the users.
Is there a method, in using deployments, that I can do this?
I don't think you can include them with the deployment image of Vault Client, but most if not all the custom views are stored in XML files on your PC.
You can write a batch file which will copy those XMLs onto the other user PCs, that can be manually run or put into a login script. You just need to find the XMLs and where they need to go to. That info is easy to find if you Google around, or ask here and say exactly which views you want to copy and we can locate the paths.
Thanks I pretty much thought that they could not be pushed out with the deploy.
In developing the deploy you can only specify which add-ins to include and service packs.
I will develop some views and do some looking.
Can't do it this morning because I had the new server restore back to raw (just 2014 basic and SQL) to do another upgrade rehearsal.
One more time, writing down all the steps so nothing is missed and I am ready for the upgrade (all software deploys have also been made and tested).
It sounds like the pushing out of the views can be something after the fact anyway.
Also it might be worth checking out "Project Thunderdome". It's a custom app created by Doug Redmond which is designed to do exactly what you want to do, standardise layouts. However I think it might only be supported on Vault Workgroup/Professional, not sure if you're on Basic?
Personally I haven't tried it yet but on face value it talks a good game.
http://justonesandzeros.typepad.com/blog/2013/05/project-thunderdome-2014.html
Worth checking it out I guess, if you have a supported Vault platform.
Ok just looked at the videos he made on this and it looks to be exactly what I need.
And it is free, +++++
OK just pulkled down the install for this and since it is an msi I can include it in my Vault deployment
I've used Thunderdome for a while, and I've been quite happy with the way it works. You load it in all of your client machines, and then run it on your admin system (client) to tell it what you want to push out. Next time your clients log in they get the updates you've made. It's pretty slick. Doug's the man!
Chris Benner
Inventor Tube & Pipe, Vault Professional
Cad Tips Tricks & Workarounds | Twitter | LinkedIn
Autodesk University Classes:
Going With The Flow with Inventor Tube and Pipe | Increasing The Volume with Inventor Tube and Pipe | Power of the Autodesk Community | Getting to Know You | Inventor Styles & Standards |Managing Properties with Vault Professional | Vault Configuration | Vault - What is it & Why Do I Need It? | A Little Less Talk - Tube & Pipe Demo | Change Orders & Revisions - Vault, Inventor & AutoCAD | Authoring & Publishing Custom Content
I do have one caveat to this that I am concerned about.
For the near future I will be running a 2015 Pro Vault with a 2014 Client base.
I will have a 2015 Client on my machine for Vault Admin Stuff (Per a ADSKers direction).
So I am wondering how to go with this add-in. Do I use the 2014 Add-in since that is what my users will be using?