With the Connect Edition, how do customize the directory structure that is created when I create a new Workset? I can't find any help on this. With V8i, we have several project template structures setup that we select when creating a new project base on the type of job...Primarily, some complex structures for complex projects and simple structures for simple jobs.
Timothy Hickman
CADD Manager | CADD Department
timothy.hickman@colliersengineering.com
Main: 877 627 3772|
1000 Waterview Drive Suite 201 | Hamilton, New Jersey 08691
Gary Manuel
OBD Update 10.10.00.197
Windows 10 Pro
Using Method #2 as I described above you can accomplish items 1 & 2.
The WorkSet template must reside in the folder where your new WorkSets will be created. You can change the location by modifying the variable _USTN_WORKSETSROOT
Rod WingSenior Systems Analyst
Thank you. I will look into this. But it raises a bigger-picture question:
We use the same exact standards for all of our projects. We are a local government engineering office producing plans for our own use. We don't have different client workspaces, etc. The only benefit of using WorkSets is the use of a dgnws file. Is there a reason I can't just use the same WorkSet for all projects? I have only created a dozen or so WorkSets so far, but as I create more and more over the next few years the drop-down list of WorkSets is going to get annoyingly long - all using the same standards other than maybe a local template library.
In SS2 all users used the same Project and Interface for all projects, but and our own User..
That's a common concern for a lot of companies. We have numerous clients that are just using the one WorkSet for everything model.
There are three drawbacks to going with a single WorkSet
Josh M said: I would like to include a few Custom Properties for use with Title Blocks, etc.
One more thing that I forgot...
If you are using OpenRoads Designer, many companies like to have a project-specific template library (.itl file). You really can't set that up if you're using one WorkSet for everything.
Thanks, Rod.
Since I would like to use custom properties and project-specific template libraries I think I will continue to use separate worksets for now.