Workspaces and workset queries.

Question

I have been trying to make some sense of workspaces and worksets and if they will work with our internal systems. See my earlier thread about this. 
 To check on this I did the following: 
 
 Opened CEU11 and from the back stage opened Create Workspace. 
 I named the new workspace which then populated the folder locations. This used the server location for our No Workspace. 
 Question &ndash; Can I change the &lsquo;Standards&rsquo; location to our server &lsquo; Organisation &rsquo; folder without this being overwritten? 
 Question &ndash; How do I stop the Standards Subfolders being created? Even if I delete, they still appear ! 
 Clicking OK creates the Workspace. 
 With the new Workspace created I am then able to create a Workset . Sounds easy! 
 Naming the Workset populates the Folder locations. 
 Question &ndash; I need the Root Folder to be a new created folder in a different drive, (see previous thread), and not be overwritten. 
 How do I stop Design Files, Standards Files and Standards Subfolders being used. We don&rsquo;t need these as our server &lsquo;Organisation&rsquo; folder has all the standards files & subfolders and the job folder has the design files. 
 
 Basically, if this is to work for us, we just need the workset to point to the server for the standards information and the job folder for everything else. If it can&rsquo;t do this then it&rsquo;s back to No Workspace>No Workset . 
 Any help would be appreciated .

John Frampton · Answer

stuartw said: Question – Can I change the ‘Standards’ location to our server ‘ Organisation ’ folder without this being overwritten? 
 Why do you want to do this? I am not following your logic. The Organization standards are already loaded and don't need to be loaded again by the WorkSpace 
 stuartw said: Question – How do I stop the Standards Subfolders being created? Even if I delete, they still appear ! 
 I think this is WApD. Unfortunatly though it should be like this. If it's not nessary for the application you should be able to set it to null. I know this is something that we desire also as the WorkSpace is just a pass through for us to load the Civil_Org to use (another whole issue!) and the list of WorkSets 
 stuartw said: Question – I need the Root Folder to be a new created folder in a different drive, (see previous thread), and not be overwritten. 
 This location is controlled by the variable _USTN_WORKSETSROOT and it's defined in the WorkSpace as $(_USTN_WORKSPACEROOT)WorkSets/. Just define it in that file to be the location you want them created. Each WorkSpace defines where it's WorkSets are stored 
 stuartw said: How do I stop Design Files, Standards Files and Standards Subfolders being used. We don’t need these as our server ‘Organisation’ folder has all the standards files & subfolders and the job folder has the design files. 
 You can null this information out in the cfg by using the # sign. We have ours set up this way and it seems to work great. 
 Ultimately we hope to be able to have a template workset that creates all the directory structure we need. If you want look into editing the templates for WorkSpaces and WorkSets they will help you get towards what you want. Note the WorkSpace/SET.template files are not intergrated with what the application creates or doesn't. An example would be it doesn't read the WorkSpace.template file to know where to create it's worksets. Also note there are some holes in the WorkSet template approach that Bentley has defects on. These will cause you some headaches as it doesn't work quite right without manual editing. 
 always I hope this helps

Workspaces and workset queries.

Top Replies