Workset Templates

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. 

Parents
  • Check out the following two variables - these may help
    _USTN_WORKSETSTANDARDSUBDIRS:
    _USTN_WORKSPACESTANDARDSUBDIRS:

    Timothy Hickman

    CADD Manager | CADD Department

    timothy.hickman@colliersengineering.com

    Main: 877 627 3772| 

    1000 Waterview Drive Suite 201 | Hamilton, New Jersey 08691

  • I have seen these variables...What about folders outside of the Standards folder...and what about content? what we need is what V8i has and creates a copy of the workset folders and its content. If this is not available, I have no choice but to manually do this...which is a step backwards going to Connect.

    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 Wing
    Senior 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

    1. If you use ProjectWise, you really can't have a single WorkSet for everything (doesn't sound like an issue for you)

    2. You can only have one Sheet Index per WorkSet. If you're going to use the Sheet Index you'll have to come up with some custom folder structures to separate you different projects. Also, I don't know if there is a maximum number of sheets for the Sheet Index. There could be a practical limit, where once you hit a certain number of sheets the overall MicroStation performance goes down the tubes.

    3. Custom WorkSet properties. This could be a big issue for you. 
      I would like to include a few Custom Properties for use with Title Blocks, etc.

      If that is your goal, the single WorkSet model will not work for you. Changing the properties for one project will change the title blocks for all of your previous projects that are linked to the custom properties.

    Rod Wing
    Senior Systems Analyst

  • 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.

    Rod Wing
    Senior Systems Analyst

  • 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.

Reply Children
No Data