I am working through my client configurations commenting out things I don't want/need, and locking variables in my organization CFG so that our standards will be followed when needed.
What is the configuration variable, or variable tree, that determines which workset template is used? Everyone's template is just a little different, and I'd prefer to create my own template and use that wherever possible.
Also, is it possible to create a workset if the directory structure already exists? Our project directories are usually set up by our project managers long before billable work starts on a project. Any new worksets I create do not need to create any directories - I need only the CFG and DGNWS. I'm pretty sure this can be done but I'd like assurance from you guys.
Thank you!MaryB
when creating a workset from the UI, you have the option to use an existing workset as a template. You also have the option to create the workset with just the folders.
Timothy Hickman
CADD Manager | CADD Department
timothy.hickman@colliersengineering.com
Main: 877 627 3772|
1000 Waterview Drive Suite 201 | Hamilton, New Jersey 08691
I'm not actually going to need to create folders at all. The folders will already be there, created when the project managers set up the project directory structure. Is it possible to create a template that doesn't include any folders? I just need the CFG and DGNWS
I'm also trying to track down why my test project is looking for a DGN folder (I don't have one of those, and that's coming from somewhere).
MaryB
Power GeoPak 08.11.09.918Power InRoads 08.11.09.918OpenRoads Designer 2021 R2
MS_DEF ?
The variable that defines where the WorkSet is looking for the dgn files is _USTN_WORKSETDGNS
There is also a _USTN_WORKSETSTANDARDSUBDIRS variable that defines what sub directories get created when creating a WorkSet. You can probably just clear that definition so that no sub folders are defined.
If you create Template with no folders and use that template I think you can modify that as well.
I don't think you can entirely suppress the creation of a WorkSet folder.
Rod WingSenior Systems Analyst
MaryB said:I am working through my client configurations commenting out things I don't want/need, and locking variables in my organization CFG so that our standards will be followed when needed.
I would avoid editing the client configs as much as possible. With every update you receive from the client you will have to remake those changes.
One technique I use is to create a separate config file with all of the modifications to eliminate things from the client config that need adjustment. Then you can edit the client config to do a %include of your custom config at the very end of the client config. It's one simple edit that's not that hard to redo when installing any future updates.