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 Reply Children
  • I've only started playing with this, but you may be able to use the _USTN_WORKSETSTANDARDSUBDIRS configuration variable. In the WorkSpaceSetup.cfg these come commented out as default:

    #_USTN_WORKSETSTANDARDSUBDIRS                = Cell;Data;Seed;Symb;Macros;Sheet Borders;Superelevation;Template Library
    #_USTN_WORKSETSTANDARDSUBDIRS                > Dgnlib;Dgnlib/GUI;Dgnlib/Render;Dgnlib/DrawComp;Dgnlib/Links;Dgnlib/ClashDetection;Dgnlib/Printing
    #_USTN_WORKSETSTANDARDSUBDIRS                > Dgnlib/Civil Cells;Dgnlib/Feature Definitions;Dgnlib/Sheet Seeds;Dgnlib/Graphical Filters

    That doesn't solve the problem of files, but it should generate your directory structure.

    Files seem to be a bit more...unpredictable. There is the concept of the Workset Template, but I find more posts about how it doesn't seem to work as expected, than how it does. I did a quick search of the Project Administration Forum and didn't find much helpful discussion with easy fixes. 

    MaryB

    Power GeoPak 08.11.09.918
    Power InRoads 08.11.09.918
    OpenRoads Designer 2021 R2

        

  • Thanks, Mary. I will look into these variables and see if we get something close. 

  • I've been looking into this a lot recently. It's been a frustrating exercise to say the least. I've got a few service tickets open for things that aren't working properly.

    There are three basic ways to set up a WorkSet Template. 

    Method #1 - Using configuration variables

    In a configuration file you will need to set the following three variables and also create the corresponding seed .cfg and .dgnws files.

    #-------------------------------------------------------------------- 
    # WorkSet
    #-------------------------------------------------------------------- 
    _USTN_WORKSETTEMPLATE = $(_USTN_ORGANIZATION)seed/WorkSets/$(_USTN_WORKSPACENAME)_WorkSet_Template.cfg
    _USTN_WORKSETDGNWSTEMPLATE = $(_USTN_ORGANIZATION)seed/WorkSets/$(_USTN_WORKSPACENAME)_WorkSet_Template.dgnws
    _USTN_WORKSETSTANDARDSUBDIRS = Cell;Data;Seed;Symb;Macros;Dgnlib;Dgnlib\GUI;Dgnlib\Render;Dgnlib\DrawComp;Dgnlib\Links;Dgnlib\ClashDetection;Dgnlib\Printing;Template Library
    

    When creating a new WorkSet the seed files are copied for the new WorkSet .cfg file and dgnws file, and the Standards subfolders are created. It kind of works, but has problems:

    • As noted by others you cannot have it copy in custom files. For example, in ORD we want to have it copy in a seed .itl file in the Template Library folder so that each WorkSet can have its own.
    • Custom WorkSet properties defined in the seed .dgnws file are not present in the new WorkSet.

    Method #2 - Using a complete template WorkSet.

    For this method you create a complete custom seed WorkSet template where all of your other regular WorkSets are located. When you create a new WorkSet you select your template WorkSet from the drop-down.

    This solves the two main issues with Method #1, but has another big problem. There is no way that I have found to prevent users from accidently picking the template WorkSet as their active WorkSet and adding dgn files and other files to it, thus mucking up your template.

    Method #3 - Creating a custom WorkSet creation tool

    We've been asked by multiple clients to create a custom tool to create WorkSets for each new project. The reason for this is that they want their WorkSet configuration file to reside in the default WorkSets folder, but the dgn files, .dgnws file, project ORD .itl file, etc. to be stored under their company standard Projects folder on a separate network drive in many cases. To complicate matters the project folder names do not directly correspond to the WorkSet name, so the WorkSet configuration file has to have variable modifications when the WorkSet is created to reference the correct folder. One company even wants to pass the job of creating new projects/WorkSets to an Office Manager type person who doesn't need any Bentley products installed.

    It may sound complicated, but it's not a difficult application to develop. 

    This method is a non-starter at present as you cannot move/rename the .dgnws file without corrupting it.

    Rod Wing
    Senior Systems Analyst

  • I, too, am interested in setting up a WorkSet Template.  I would like to include a few Custom Properties for use with Title Blocks, etc.  I would also like to create a standard set of folders.  I would also like to specify the location of the main project (WorkSet) folder.

    I set up a WorkSet with the custom properties that I want, and I manually added a few other folders (besides dgn, out, and Standards and it's subfolders).

    I notice that when I try to use this WorkSet as a template for a new workSet it doesn't allow me to select the folder for the new WorkSet.

    At the very least I would like to standardize the Custom Properties across any new WorkSets.  So far I have just created Worksets with no template. I then manually added in the other necessary folders.

    Can I do any or all of this with a WorkSet template?
    1.  Define Custom Properties
    2.  Create a folder structure that includes folders outside of the Standards folder
    3.  Choose the location of the WorkSet folder?

    Thank you.

  • 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